Ship wording updates
Publish approved translations to connected apps without compiling a new build.
Live translation updates for app developers
Bring translations from your AI agent, review them, and publish updates to your customers. Built for solo developers and teams.
Add delivery to your app once. Compatible wording updates need no rebuild.

AI quick start
Keep translating with your own agent. The TransLocale skill helps it choose your app’s integration and check what’s needed for delivery.
Create a free project Read the setup guideRun this in your app directory. You'll need Node.js 22.16 or later.
npm exec --package=@translocale/cli@latest -- translocale skills install --agent codexAdd this URL in your assistant's MCP settings, sign in, and choose a project. Local file checks work without this connection.
https://translocale.io/mcp/authorizedReload your assistant if the skill isn't listed, then send:
Use $translocale to check whether this app can receive translation updates without a new build. Show the setup and catalog gaps. Do not start a translation job or publish changes.This prompt checks readiness without changing or publishing wording. TransLocale’s paid AI translation is optional.
Use your existing stack. OTA support varies by integration.
Why TransLocale
Use translations from your AI agent, translator, or agency. In TransLocale, you can review and publish them to your app yourself.
| After translation | A manual file handoff | With TransLocale |
|---|---|---|
| Check and approve | Review the changed files and keep track of what is ready to ship. | Check for missing keys and placeholder errors. Approve wording yourself or invite a reviewer. |
| Deliver a correction | Replace bundled language files, then build and distribute an app update. | Publish compatible wording to connected apps. Your customers see it when their app next checks for updates. |
| Undo a wording change | Restore the previous files and ship another app update. | Roll back to a previous compatible release. Apps use cached or bundled translations when they cannot fetch an update. |
Set up delivery in your app once. OTA support depends on your framework. New keys, languages, or message parameters may still need a new app build.
From your agent to your customers
Publish approved translations to connected apps without compiling a new build.
Import wording from your AI agent or existing language files.
Review wording yourself, or invite someone to help before you publish.
Find missing keys, changed source text, and broken placeholders.
Connected apps keep bundled or cached wording when delivery is unavailable. Roll back a release when needed.
Need help generating wording? Use TransLocale’s translation service with a character cap.
For AI coding assistants
Keep using your AI assistant to translate. Connect it to TransLocale through MCP to import the wording, check it, and prepare an approved release for your app.
Your agent can write the language files using your glossary. TransLocale’s translation service is optional.
Ask your assistant to find missing keys and broken placeholders.
Publish approved wording through MCP. Compatible apps get the update without a new build.
Use your own model to translate our onboarding strings into French. Follow our project’s glossary, validate the files, and show me an import preview in TransLocale.
Use the AI agent you already work with.
Take a closer look
Check the context and edit wording together.
Update wording and switch languages.
For the way you build
Work in the dashboard, your terminal, or your AI assistant.
Read the docsnpx translocale check \
--source en.json \
--target fr.json \
--format jsonCheck the files before you import and publish.
Bring your language files and connect a compatible delivery integration.