Paste both locale files
Use the complete source-language file and one translation file.
Localization gap finder
Use a source locale and a translated locale to find missing translation keys, obsolete extra keys, empty values, and value-type mismatches before release.
Data tool
Use the complete source-language file and one translation file.
Nested objects are converted into matching key paths.
Review missing, extra, empty, and type-mismatched translation entries.
Catch missing interface strings before deployment.
Identify obsolete keys that can be removed.
Compare locale files after restructuring translation namespaces.
Yes. i18n JSON Compare is free to use without an account or usage meter.
No. The processing for this tool runs locally in your browser. Entered content is not sent to our server.
No. It focuses on deterministic structural QA so teams can send an accurate missing-key list to translators.
Keep working
Check source and translated text for missing variables, HTML tags, numbers, URLs, and line mismatches before localization release.
Flatten nested JSON objects and arrays into dot-notation paths. Inspect configuration, translation, and API data online.
Compare two JSON documents by keys and values instead of line order. Find added, removed, and changed paths in your browser.
Validate JSON online and locate syntax errors with line and column details. Format valid JSON without uploading your data.