Branch, edit, and merge translations the way your team already works — built for developers and translators working together. Real-time collaboration, role-based reviews, webhooks, and a clean API.
Free plan forever · No credit card required
Built for product teams that treat translations as part of the release process — not an afterthought.
Create a branch per feature, translate in isolation, and merge back to main with permission-guarded merges.
Live WebSocket updates notify every project member the moment a label is added, edited, or merged.
REST API with personal access tokens, multi-format import/export (JSON, Android XML, iOS .strings, CSV), and webhooks for label and branch events.
Organize projects into workspaces and assign owner, admin, developer, or translator roles per project.
Fill missing values automatically with AI-powered suggestions, then let your translators review and refine.
Two-factor authentication, token-based access, rate limiting, and input sanitization on every request.
Stop coordinating spreadsheets across feature freezes. Each feature gets its own translation branch — work lands on main only when it's reviewed and ready.
A CLI, CI/CD integrations, a REST API, and an official MCP server — so your pipeline and your AI agents can work on translations directly.
Sync locale files from any repo with init, pull, push, and status. One config file ties a project to its branch, so translations move with your code.
A GitHub Action and a GitLab CI component wrap the same sync commands. Gate pull requests on missing translations, then push new keys automatically when a branch merges.
Branch-bound API tokens scope access to a single branch and the ones it creates. Labels, exports, branches, and AI translation are all scriptable over plain HTTP.
Our official server speaks the Model Context Protocol (MCP), so agents like Claude, Cursor, and other MCP clients work on translations like a teammate. They create a branch, add keys, fill in missing languages, ask you to review, and merge — with a token that can only touch its own branches.
$npx -y @translatize/mcpUpload existing files in JSON, Android XML, iOS .strings, or CSV — or start from scratch. Your structure is preserved.
Add teammates to workspaces with the right role: admin, developer, or translator.
Work in branches with live collaboration, AI suggestions, and review before merge.
Pull translations via the API or export to JSON, Android XML, iOS .strings, or CSV — webhooks keep your pipeline in sync.
Start free and upgrade as your team grows. Cancel anytime.
For trying things out
For small teams
For growing products
For agencies & enterprises
Prices exclude VAT. Applicable taxes are calculated at checkout.
All prices in USD, billed monthly via Stripe. Upgrade, downgrade, or cancel anytime from your account.
Need white-labeling or a custom integration? Contact us at support@translatize.com
A source key is a unique translation key in a project (for example checkout.pay_button). Its translated values across languages count as one key — only Free and Starter plans have key limits.
Just like Git: create a branch from main, add or edit labels there without touching production copy, and merge back when the work is reviewed. Merging to main requires admin or owner permissions.
Yes — import files in JSON, Android XML, iOS .strings, or CSV and your key structure is preserved. You can export back to any of those formats at any time, or fetch translations through the REST API with a personal access token.
Yes. Billing runs through Stripe and you can upgrade, downgrade, or cancel from your account's subscription page at any time. The Free plan is free forever.
Projects live in workspaces. Each member has a role — owner, admin, developer, or translator — that controls what they can do, from editing labels to creating branches and merging to main.
Create your first project in minutes. Branch, translate, and merge — with your whole team, in real time.
Start for freeFree plan forever · No credit card required · Cancel anytime