Translation management for developers and AI coding agents

Ship every language
like you ship code

Translatize treats localization like code: a translation branch for every feature and pull request, quality checks that gate your CI, an MCP server your AI coding agents work through, and over-the-air delivery to your apps. Built for developers and translators working together.

Free plan forever · No credit card required

checkout-app/feature/checkout-v2
checkout.titleReview your order
checkout.pay_buttonPay securely
checkout.promo_hintHave a promo code?
checkout.delivery_etaArrives in {{days}} days
2 keys changed on this branchMerge to main
Branch & merge
A branch per feature and PR
CI/CD quality gates
Catch missing and broken strings
AI coding agents
An MCP server with 28 tools
Over-the-air delivery
Fix text without an app release
Features

Everything your localization workflow needs

Built for product teams that ship translations with every release – from the first key in a pull request to the text on your users' screens.

Git-Like Branching

A translation branch per feature, compared against main and merged with the strategy you choose. Merges to main are permission-guarded, so unfinished copy never reaches production.

GitHub App

Every pull request that changes your source strings gets its own translation branch and a "Translatize" check with translation status and quality results. Translations are committed back to the pull request and merged when it merges.

Quality Checks & Merge Gate

Ten checks catch broken placeholders, ICU syntax, HTML tags, glossary terms and length limits on every change. The merge gate warns about or blocks a merge, and AI review flags meaning and style issues.

AI Translation with Context

AI translation sees key names, descriptions, character limits, your glossary and style guide, so a button reads like a button. Placeholders are never lost, and "do not translate" labels stay as they are.

Translation Memory

Approved translations and your team's edits become suggestions in the editor, and exact matches fill in before AI translation at no extra cost. AI drafts never teach the memory.

Screenshots

Show translators the screen behind every string: upload or paste a screenshot and mark the text, or capture screenshots automatically during your Playwright tests.

Over-the-Air Delivery

Publish translations to our CDN and let your web and mobile apps load them at runtime, with release history and rollback. Text fixes ship without an app-store release.

Developer Friendly

A CLI, GitHub Action, GitLab component, REST API and webhooks, with import and export in nine formats: JSON, YAML, CSV, XLIFF, gettext PO, Flutter ARB, .NET RESX, Android XML and iOS .strings.

Teams, Roles & Audit Log

Workspaces, owner, admin, developer and translator roles, live collaboration, and an audit log of who changed what. Two-factor authentication and branch-scoped API tokens keep access tight.

Why branching

Translations that move at the speed of your releases

Stop coordinating spreadsheets across feature freezes. Each feature gets its own translation branch – work lands on main only when it's reviewed and ready.

  • Branch per feature
    Developers create branches; translation work never blocks or breaks production copy.
  • Permission-guarded merges
    Only admins and owners merge to main. Branch creators and admins control deletion.
  • Conflict-free teamwork
    Translators see live changes from teammates, so nobody overwrites anyone's work.
main42 keys · 3 languages
feature/checkout-v2+8 keys · in review
feature/onboarding+14 keys · translating
merge → mainapproved by admin
roles: owner · admin · developer · translator✓ merged
Automation & AI agents

Translations your tools can drive

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.

CLI

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.

CI/CD

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.

REST API

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.

AI agents

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/mcp
How it works

From zero to localized in four steps

01

Import your keys

Upload existing files in JSON, YAML, CSV, XLIFF, PO, ARB, RESX, Android XML, or iOS .strings – or start from scratch. Your structure is preserved.

02

Invite your team

Add teammates to workspaces with the right role: admin, developer, or translator.

03

Branch & translate

Work in branches with live collaboration, AI suggestions, and review before merge.

04

Export & automate

Pull translations via the API or export to any of nine formats – JSON, YAML, CSV, XLIFF, PO, ARB, RESX, Android XML, iOS .strings – webhooks keep your pipeline in sync.

Pricing

Simple, transparent pricing

Start free and upgrade as your team grows. Cancel anytime.

Free

For trying things out

$0/month
  • 1 project · 1 workspace
  • 1,000 source keys
  • 2 branches per project
  • 2 team members
  • QA checks & translation memory
  • 20 MB screenshots (manual upload)
  • 30-day audit log
  • Community support
Get started
Most popular

Starter

For small teams

$19/month
  • 5 projects · 3 workspaces
  • 10,000 source keys
  • 5 branches per project
  • 5 team members
  • QA checks & translation memory
  • 1 GB screenshots with automated capture
  • 90-day audit log
  • Over-the-air delivery – $5/month per million requests
  • Email support
  • Basic analytics
Choose Starter

Professional

For growing products

$49/month
  • Unlimited projects & workspaces*
  • Unlimited source keys*
  • Unlimited branches*
  • 10 team members
  • Extra members at $5/month each
  • QA checks & translation memory
  • AI auto-translation – 2,000,000 characters/month
  • AI review – 1,000,000 characters/month
  • GitHub App – a translation branch per pull request
  • 5 GB screenshots with automated capture
  • 180-day audit log with CSV export
  • Over-the-air delivery – $4/month per million requests
  • Priority support
Choose Professional

Agency

For agencies & enterprises

$199/month
  • Everything in Professional
  • 100 team members
  • Extra members at $3/month each
  • AI auto-translation – 10,000,000 characters/month
  • AI review – 5,000,000 characters/month
  • 25 GB screenshot storage
  • 365-day audit log
  • Over-the-air delivery – $3/month per million requests
  • Custom integration requests
  • Dedicated support
Choose Agency

Need more people? Professional and Agency can add extra team members at any time – up to 20 on Professional and 150 on Agency. Added seats are charged pro rata for the current billing period, and removed seats are credited to your next invoice. Over-the-air delivery is an add-on on Starter, Professional and Agency, sold in blocks of 1,000,000 requests per calendar month – $5, $4 or $3 per block, up to 10, 50 or 200 blocks.

Prices exclude VAT. Applicable taxes are calculated at checkout.

* Subject to fair use, as set out in our Terms of Service.

All prices in USD, billed monthly. Upgrade, downgrade, or cancel anytime from your account.

Need white-labeling or a custom integration? Contact us at support@translatize.com

FAQ

Frequently asked questions

Can AI coding agents and CI pipelines use Translatize?

Yes – that is what it is built for. The official MCP server gives agents like Claude Code and Cursor 28 tools to create keys, translate and manage branches, with a token you scope to one branch and the branches it creates. The CLI, the GitHub Action and the GitLab component fail a build on missing translations or quality-check errors.

What counts as a source key?

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.

How does branching work for translations?

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.

Can I import my existing translation files?

Yes – import files in JSON, YAML, CSV, XLIFF, gettext PO, Flutter ARB, .NET RESX, Android XML, or iOS .strings 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.

Can I change or cancel my plan later?

Yes. You can upgrade, downgrade, or cancel from your account's subscription page at any time. The Free plan is free forever.

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 do teams and permissions work?

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.

Ready to go global?

Create your first project in minutes. Branch, translate, and merge – with your whole team, in real time.

Start for free

Free plan forever · No credit card required · Cancel anytime