How to check a translation file
Most translation bugs are not bad writing. They are mechanical: a key that exists in English but never made it into German, a placeholder a translator renamed without knowing the app passes values by name, a plural form a language needs that nobody wrote. Each one is invisible in the translation file itself and only shows up when a real user opens that screen in that language — usually after release. Checking the files against each other before shipping catches all of them in seconds.
To use it:
- Paste the base file. Usually en.json — the file the developers wrote first. Paste the JSON, drop the file onto the box, or pick it with the file button. Nested objects are flattened to dotted keys (app.welcome), so any nesting style works.
- Paste the translation. One or two target locales, each with its locale code (de, fr, ar, ja…). The code matters: it is what the plural check uses to know which forms that language needs.
- Press “Check translations”. Every key is compared: same keys, same placeholders, right plural forms, same HTML tags. Errors are the ones that break the app (missing keys, renamed or dropped placeholders, missing plural forms, empty values); warnings are the ones to look at (untranslated strings, extra keys, duplicated text).
- Work through the table. Each row names the key, the severity and the exact problem — “Placeholder {name} became {username}” rather than a vague “mismatch”. Fix the file, paste it again, and re-check until the verdict is PASS.
- Export the report. Copy it into a pull-request comment, or download the Markdown, CSV or JSON version and attach it to the translation ticket, so the translator sees exactly which keys to fix.
What makes this checker different
A key coverage checker answers one question: do both files have the same keys? That is necessary and not enough. The failures that actually break apps live one level deeper: a placeholder renamed from {name} to {username}, a %d that became %s, a plural missing the “one” form that German needs, a string left in English because nobody noticed. The tools that do check placeholders either handle one format at a time — you have to tell them whether your project uses {name} or {{name}} — or they do not parse ICU plurals at all, so the plural check never happens. This page does all of it in one run: seven placeholder styles auto-detected, ICU plurals and selects parsed, plural completeness checked against the real CLDR categories for the target language, and two locales checked together. The nearest comparable web tool checks one pair of files, one placeholder format, and states plainly that it does not parse ICU plural or select syntax. If all you need is a key list, that is enough; if you need to know whether the translation will actually run, this is the check.
When is this the right check?
Before every release that touches a locale file; when a translation comes back from a translator or a machine-translation pass; when a developer adds a new string and wants to know which languages are now behind; and when a user reports a blank, a raw {name} on screen, or a sentence that reads wrong only in one language. It is also the check to run after merging a translation pull request — the diff may look clean while a placeholder quietly changed inside a string.
Honest limitations
It cannot judge translation quality
A string can pass every check here and still read badly, use the wrong tone, or mistranslate a term. Structure is checkable; quality needs a human reader of that language. Use this tool to catch breakages, not to approve wording.
Plural rules come from the browser
The plural categories are read from the browser's own Intl.PluralRules, which follows the CLDR data shipped with that browser. If a locale code is unknown, the plural check is skipped and the report says so, rather than guessing.
ICU parsing is a subset
Plurals, selects, numbers and dates are parsed, including placeholders nested inside plural options. Exotic ICU features — custom formats, nested selects inside selects, and rich-text tags inside ICU options — are read as plain text, which can produce a warning where a full ICU parser would not.
Renamed placeholders are a best guess
When the same number of placeholders is missing as is added, the checker reports them as renames paired in order. If a translator renamed two placeholders at once, the pairing may be wrong — the error itself (something changed) is real either way.
HTML tags are compared, not rendered
A tag mismatch is a warning, not an error: some frameworks strip tags, others render them, and a dropped <b> may be harmless in one app and visible in another. Read the warning against how your app renders the string.
Keys are matched by name, not meaning
A key that was renamed in the base file looks like a missing key plus an extra key. That is correct behaviour — the translation really does not have the new key — but the fix is to rename it in the translation, not to add a duplicate.