Frequently asked questions
Everything about Translatize – what it is, how branching and pull requests work, quality checks, AI translation, delivery, pricing and your data. Straight answers to the questions people actually ask.
What is Translatize?
Translatize is a translation-management platform built for developer teams and the AI coding agents they work with. It treats localization like code: every feature and pull request gets its own translation branch, quality checks gate your CI before anything merges, AI coding agents work on translations through an MCP server, and over-the-air delivery puts text fixes in front of users without an app release. Translation memory, AI translation with your context and screenshots help translators get it right the first time.
How is Translatize different from Lokalise or Crowdin?
Translatize is built around the developer workflow instead of added on to it. Translations live in branches that follow your Git branches and pull requests, they are checked in CI like the rest of your code, and AI coding agents can manage them end to end through the official MCP server. On top of that it covers what a modern localization platform needs: translation memory, AI translation with context, quality checks with a merge gate, screenshots for translators and over-the-air delivery. Pricing is flat and predictable – Free, Starter at $19, Professional at $49 and Agency at $199 a month.
How much does Translatize cost?
There are four plans, billed monthly. Free is $0 with 1 project, 1 workspace, 1,000 source keys, 2 branches per project, 2 team members, 20 MB of screenshot storage, and a 30-day audit log. Starter is $19/month with 5 projects, 3 workspaces, 10,000 source keys, 5 branches per project, 5 team members, 1 GB of screenshots with automated capture, and a 90-day audit log. Professional is $49/month with unlimited projects, workspaces, source keys, and branches, 10 team members, AI auto-translation (2,000,000 characters a month), AI review (1,000,000 characters a month), the GitHub App, 5 GB of screenshots, and a 180-day audit log with CSV export. Agency is $199/month with 100 team members, 10,000,000 AI translation and 5,000,000 AI review characters a month, 25 GB of screenshots, a 365-day audit log, and custom integration requests. QA checks and translation memory are included on every plan. On Professional and Agency you can add extra team members at any time – $5 and $3 per member a month respectively – and Starter, Professional, and Agency can add over-the-air delivery at $5, $4, and $3 respectively per block of 1,000,000 requests a month. Prices exclude VAT, which is calculated at checkout. “Unlimited” allowances are subject to fair use under our Terms of Service.
Is there a free plan?
Yes. The Free plan is free forever and needs no credit card. It includes 1 project, 1 workspace, 1,000 source keys, 2 branches, 2 team members, QA checks, translation memory, 20 MB for manually uploaded screenshots, and a 30-day audit log – enough to run a small project from start to finish. You can upgrade, downgrade, or cancel at any time from your account.
Can I add more team members without changing plan?
Yes, on Professional and Agency. Professional includes 10 team members and Agency 100. Beyond that, add extra seats from your subscription page – $5 per member a month on Professional (up to 20 extra) and $3 on Agency (up to 150 extra). Added seats are charged pro rata for the rest of the billing period, and seats you remove are credited to your next invoice.
What is over-the-air delivery and how is it billed?
Over-the-air delivery publishes your translations to a global content delivery network, so your web or mobile app picks up new strings without a redeploy or an app-store release. It is an add-on on Starter, Professional and Agency, sold in blocks of 1,000,000 requests per calendar month (UTC) – $5, $4 or $3 per block a month respectively, up to 10, 50 or 200 blocks. We email you at 80 % and 100 % of your volume and keep serving up to 120 %; beyond that, requests pause until you add blocks or the next month begins, and the SDK falls back to cached or bundled strings. Anything you publish is public, so never put secrets in translations.
How does translation branching work?
You create a branch from main, add or edit labels there without touching production copy, then compare the branch against main to see exactly which keys were changed, added or deleted. When you merge, you pick a strategy: branch-changes (only what the branch itself changed, per language – what the GitHub App uses), overwrite (a non-destructive union where the source wins conflicts), replace (main becomes a copy of the branch), keep-newer, or manual (you resolve each conflict yourself). Merging to main requires admin or owner permissions, while developers and above can create branches.
Can I use Translatize in CI/CD?
Yes. The @translatize/cli tool downloads translations, uploads new source keys, and gates a build on translation completeness (status --fail-on-missing) or quality (qa, which fails on QA errors) – a failed gate exits with a non-zero code. It also uploads screenshots captured in your end-to-end tests and publishes over-the-air releases. There is a ready-made GitHub Action (translatize/sync-action) and a GitLab CI/CD Catalog component, both wrapping the same CLI. Every tool authenticates with a branch-bound API token you store as a CI secret. On Professional and Agency, the Translatize GitHub App goes further and gives every pull request its own translation branch and check automatically.
Does Translatize work with GitHub pull requests?
Yes. The Translatize GitHub App, on Professional and Agency, gives every pull request that changes your source strings its own translation branch and a "Translatize" check with translation status and quality results. New strings can be translated by AI right away, translations are committed back to the pull request on request or automatically, and when the pull request merges, only its strings are merged into your base branch.
Can AI agents use Translatize?
Yes. The @translatize/mcp server exposes 28 tools over the Model Context Protocol, so agents like Claude Code, Cursor, and Claude Desktop can read and write keys, translate, and manage branches directly. You can mint a create-own API token that works only on its own base branch and the branches it creates – it can never touch any other branch – which makes it safe to hand an agent a token of its own.
Does Translatize do AI translation?
Yes, on the Professional and Agency plans. AI translation works from more than the source text: key names, descriptions, character limits, your glossary and style guide, translation memory and related translations go along with it. A translation that loses a placeholder is never saved, and labels marked "do not translate" keep their text. It runs as a background job metered in characters – 2,000,000 a month on Professional and 10,000,000 on Agency. AI review then flags accuracy, fluency, terminology and style issues on a quota of its own – 1,000,000 characters a month on Professional and 5,000,000 on Agency – and its findings never block a merge.
Does Translatize have translation memory and quality checks?
Yes, on every plan. Translation memory learns from translations your team approved or edited and suggests them in the editor; on Professional and Agency, exact matches fill in before AI translation without using your AI characters. Ten quality checks – placeholders, HTML tags, ICU syntax and plural forms, glossary terms, character limits and more – run on every change, and a per-project merge gate can warn about or block a merge into main.
Can translators see where a string appears?
Yes. Attach screenshots to any key in the editor – upload or paste one and mark where the text is. From the Starter plan, @translatize/playwright captures screenshots during your existing end-to-end tests and links each visible string to its key automatically. Screenshots are visible only to your project members and are never sent to AI.
Where is my data stored?
Translatize is operated from the European Union by SIA "MICRON", a company registered in Liepāja, Latvia (registration number 42103081578). It is built to be GDPR-compliant, and the Privacy and Cookie policies document exactly what is collected and why.
Can I export my data, or is there lock-in?
There is no lock-in. You can export your translations at any time to JSON, YAML, CSV, XLIFF, gettext PO, Flutter ARB, .NET RESX, Android XML, or iOS .strings, import from those same formats, and pull everything through the REST API with a personal or integration token. Your key structure is preserved on both import and export.
What file formats does Translatize support?
Import and export both cover nine formats: JSON (nested or flat), YAML, CSV, XLIFF 1.2, gettext PO, Flutter ARB, .NET RESX, Android XML, and iOS .strings. JSON, YAML and CSV carry every language in one file; the rest are single-language. XLIFF is bilingual – it pairs each translation with its source text, which is what CAT tools and translation agencies expect. The CLI reads and writes per-language JSON files.
Who is behind Translatize?
Translatize is built and operated by SIA "MICRON", a software company based in Liepāja, Latvia, in the European Union (registration number 42103081578). You can reach the team at support@translatize.com.