Skip to tool
Developer tools / Localization checker
FILES STAY IN YOUR BROWSER
EVERY KEY. EVERY LANGUAGE.

Localization checker.

Catch missing translations and broken placeholders before a build.

CSV CHECKUse one source-language CSV and one or more translation CSVs. Select the key and text columns for each file.

01 · Source language

The reference keys and placeholders.

No source selected.

02 · Translations

Add a CSV for each language to check.

No translations selected.

Translation report

Load files to generate a report.

File / CSV rowIssueKeySource textTranslationDetails
Supported CSVs and placeholder rules

UTF-8, comma-separated CSVs with a header row. Quoted commas and multiline text are supported. Files may contain extra columns; choose the key and text columns to use. Limits: 2 MB, 10,000 entries, and 80 columns per file; up to 20 translation files.

Keys are case-sensitive and trimmed at their edges. Blank keys, duplicate keys, empty source text, missing target keys, empty translations, and extra target keys are reported. Duplicate keys are treated as ambiguous and excluded from text comparisons.

Checks compare placeholder identities and occurrence counts, allowing reordering: {0}, {playerName}, {0:N2}, and {0,10:N2}. Alignment and format suffixes must match. Escaped double braces such as {{0}} are treated as literal text. Nested ICU message syntax, printf tokens, and HTML tags are not validated. This checker does not judge translation accuracy.

Files remain in this tab and are not saved after a reload. Export the report to keep the findings.