Tolgee

Capabilities

• In-context editing in the live app Hold ALT and click any string in the running application to translate or edit it in place, with the change saved straight to the platform. Developers integrate an SDK once and never shuttle translation files around again.[1][2]

• One-click screenshots per key One click captures a screenshot of the current view with the translated phrases highlighted, so every key carries the visual context translators need to pick the right wording and length.[1][2]

• Translate in production via browser plugin The Chrome plugin Tolgee Tools plus an API key opens translation mode on the deployed production app, so translators and content editors can fix copy in the real product without a developer build.[1][2]

• SDKs across web and mobile stacks Dedicated SDKs cover React, Vue, Angular, Svelte, Next.js, and vanilla JavaScript, with Apple, Android, and Flutter support for native and cross-platform mobile apps.[1][2]

• AI translator with visible context The built-in AI translator reads screenshots, key and project descriptions, translation memory matches, and layout context, then explains how it arrived at each suggestion so reviewers can judge it quickly.[1]

• Multi-provider machine translation Machine translation from DeepL, Google, AWS, and Azure plus automatic translation of new keys through translation memory or machine translation keeps new strings from sitting untranslated.[1]

• Memory, history, and team workflow Translation memory suggests past translations with similarity scores, while per-key history, an activity log, and comments preserve who changed what and why across the whole project.[1]

• CLI, API, Figma, and AI-assistant access A CLI and REST API automate imports, exports, and content delivery, the Figma plugin links design copy to translation keys, and an MCP server lets AI assistants manage translations through the same API.[1]

Who it fits

• We would evaluate Tolgee first if the bottleneck is the handoff between developers and translators: in-context editing and production translation mode remove the file-passing loop that slows multi-language releases.[1][2]

• Teams with data-control or procurement requirements will get the most out of it, since the Docker self-hosted option keeps all translation content on infrastructure they operate.[1][2]

• Products with layout-sensitive copy across many languages fit well, because screenshots, AI context, and translation memory all target the classic problem of strings that fit in English but break elsewhere.[1]

Boundaries to check

• The free self-hosted core does not include everything: advanced self-hosted features require a paid Tolgee Platform license, so capability planning needs the pricing page alongside the repository.[1]

• The Cloud Free plan caps at 3 seats and 30,000 hosted words with finite machine translation and AI credits, so growing projects graduate to metered tiers where both translation volume and MT characters are billed.[1]

• Machine and AI translation remain suggestions that need human judgment on ambiguous or brand-sensitive strings; the platform keeps an optional review step for exactly this reason, which adds reviewer workload on large projects.[1][2]

• Self-hosting trades subscription cost for operational work: running, updating, and backing up the Docker deployment is yours, whereas the cloud plans hand that over to Tolgee.[1][2]

Fit and compatibility