Frequently asked questions
Everything about Translatize — what it is, how branching works, pricing, integrations, AI agents, and your data. Straight answers to the questions people actually ask.
What is Translatize?
Translatize is a translation-management platform with git-like branching. You branch, edit, and merge your app's translations the same way your team ships code — with real-time collaboration, role-based permissions, webhooks, a REST API, and multi-format import/export. It is built for developers and translators working together.
How is Translatize different from Lokalise or Crowdin?
The core difference is git-like branching: every feature gets its own translation branch that you compare against main and merge with a chosen strategy, so unfinished copy never leaks into production. Pricing is simple and predictable — Free, Starter at $19/mo, Professional at $49/mo, and Agency at $199/mo, all in USD. Translatize is a young, independent EU product rather than a large incumbent, so it concentrates on the developer workflow — CLI, CI/CD, and an MCP server for AI agents — instead of trying to cover every enterprise feature.
How much does Translatize cost?
There are four plans, billed monthly via Stripe. Free is $0 with 1 project, 1 workspace, 1,000 source keys, 2 branches per project, and 2 team members. Starter is $19/month with 5 projects, 3 workspaces, 10,000 source keys, 5 branches per project, and 5 team members. Professional is $49/month with unlimited projects, workspaces, source keys, and branches, 10 team members, and AI auto-translation. Agency is $199/month, adding unlimited team members and custom integration requests. Prices exclude VAT, which is calculated at checkout.
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, and 2 team members — enough to run a small project from start to finish. You can upgrade, downgrade, or cancel at any time from your account.
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 one of four strategies: overwrite (a non-destructive union where the source wins conflicts), replace (destructive — 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 has three commands — pull, push, and status — so you can download translations, upload new source keys, and gate a build on translation completeness (status --fail-on-missing exits with a non-zero code). 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.
Can AI agents use Translatize?
Yes. The @translatize/mcp server exposes 18 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 auto-translation fills in missing values as a background job and is metered in characters against a monthly quota — 2,000,000 characters on Professional and 10,000,000 on Agency. On any plan, an AI agent connected over MCP can also translate the missing values itself and write them back.
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, CSV, 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 JSON (nested or flat), CSV, Android XML, and iOS .strings. The CLI reads and writes per-language JSON files, and the API export endpoint additionally serves single-language iOS and Android 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.