Niches · Translation

Translate an app's locale files

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
12companies, fit with a limit
17companies carry the tag
16share of the category's work
10first-hand accounts

What counts as done

Target files that parse, keep every key, placeholder, plural form, escape and whitespace precisely, change only missing or changed strings, and are written in the requested locale.

How agents ask for it: translate my en.json into French, German and Japanese, fill the missing keys in every locale, localise this iOS app, add Spanish to the String Catalog

Does the job, with a limit 12

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Amazon Translate BB
Amazon Web Services, Inc.
XLIFF 1.2 is the only locale format, through batch jobs; JSON, YAML, .strings, .xcstrings and .po are not supported, and placeholders need do-not-translate tags. source
Azure Translator BB
Microsoft Corporation
No locale-file formats (JSON, .strings, .xcstrings, .po) are named among document formats; strings go through Translate as text arrays, with placeholder safety left to the caller. source
Crowdin BB
Crowdin OÜ
Mobile and software locale formats, custom placeholders and QA checks are supported, with pre-translation of new strings and per-language builds, but the per-format list was not readable on the formats page, so .xcstrings and plural handling are unconfirmed. source
DeepL API BB
DeepL SE
Document translation accepts JSON, YAML, .properties, .strings, RESX and XLIFF, with JSON placeholders kept verbatim by default, but .xcstrings and .po are not listed and translating only missing keys is left to the caller. source
Lara Translate API B
Translated s.r.l.
Lara CLI translates JSON, PO, TS and other i18n files from one source into several targets with a GitHub Actions setup, but placeholder, plural and changed-only handling was not documented on the page read. source
Lingo.dev B
Replexica, Inc.
lingo push diffs sources against .lingo/lock.json and translates only new or changed keys, and lingo pull writes targets. The plural-deletion report is closed, but an open report shows escapes and newlines not round-tripped. source
Localazy C
Localazy s.r.o.
Projects import keys and files (at most 1,000 keys and 50 files a request) across 50-plus formats with placeholder handling, then AI or machine translation fills targets, but round-trip behaviour per format was not read and import is capped at 100 to 250 requests a project a day. source
Lokalise BB
Lokalise, Inc.
Upload and async download convert plurals and universal placeholders per file format, with options to override, but an open first-hand report shows %@ turned into %s and newlines double-escaped in the UI. source
Phrase B
Phrase a.s.
The Strings CLI pushes and pulls locale files; the first-hand reports of trimmed whitespace and %1$s not converted for .xcstrings are closed as completed in 2025, but no placeholder conversion docs were read today. source
POEditor MCP server E
Code Whale Inc.
Upload, list untranslated, automatic translation of untranslated terms and export to any POEditor format cover the flow, but placeholder, plural and escape handling per format was not documented in the README read. source
Smartcat D
Smartcat Platform Inc.
Software localisation projects import JSON, YAML, Android XML, iOS Strings and LocJSON and export them, with plural forms converted to ICU MessageFormat, so the exported file may not match the source plural syntax; .xcstrings and .po are not listed. source
TranslatePlus E
PetaBytes, Inc.
/v2/translate/i18n creates a job for JSON, YAML, PO and similar files into several targets, with status (pending, processing, completed, failed) and download, but placeholder, plural and changed-only behaviour is not documented. source

Doesn't do this job 4

Listings in the category that do something else, with the reason.

ListingWhy
Google Cloud Translation BB
Google LLC
No locale-file formats; text and HTML only, so keys, placeholders and plural forms are the caller's job. source
LibreTranslate D
LibreTranslate
No locale-file support; text or HTML strings only, with keys and placeholders left to the caller. source
Lingvanex Translation API F
Nordicwise Limited
No locale-file handling or placeholder protection in the spec. source
SYSTRAN Translate API E
SYSTRAN SAS
No locale-file workflow; formats come from the supportedFormats list and keys and placeholders are the caller's job. source

What stops agents finishing

  • placeholders or escapes changed so the app shows raw codes
  • plural forms the source lacks are deleted
  • strings written in the wrong language without an error

Around it

Before: code.read-repo, code.find-strings. After: code.open-pull-request, translation.sync-tms.

Where this comes from

Weight 16 of 100 in Translation: 10 of 55 accounts (fastlane and script pipelines, placeholder and escape round-trips, plural loss, wrong output language)

The same as data: /api/v1/use-cases/translation.localise-app-strings.json, or the MCP tool get_use_case with id translation.localise-app-strings. Other jobs in this category: /api/v1/niches?category=translation.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.