i18n Coverage Checker
Compare two locale JSON files to find missing keys, extra keys, and empty translations with per-namespace coverage percentages. Private and fully in-browser.
Loading tool...
What is i18n Coverage Checker?
The i18n Coverage Checker compares two locale JSON files key by key using dot-notation flattening, reporting missing keys in each direction, empty translations, and per-namespace coverage percentages - all computed locally without uploading your files.
Key Benefits
- Instant locale parity check without running a build
- Per-namespace coverage table shows exactly where gaps live
- Empty-translation detection catches unfinished work
- Missing keys displayed as copyable chips for fix commits
Common Use Cases
- •Auditing translation files before a release
- •Onboarding a new language and finding what must be translated
- •Reviewing i18n pull requests for parity regressions
- •Cleaning up legacy locale files with orphaned keys
- •Tracking translation progress across sprints
Check i18n Coverage
- Paste locale A: Paste the full JSON of your first locale file, such as en.json, into the left editor.
- Paste locale B: Paste the second locale, such as th.json, into the right editor. Both files are parsed locally.
- Read the coverage table: Each top-level namespace shows key counts for both sides and a coverage percentage based on keys present in both files.
- Fix the gaps: Missing-key chips show exactly which dotted paths to add where - copy them into your fix commit.
Key Features
- Compares two locale JSON files key by key with dot-notation flattening
- Missing and extra keys reported per direction
- Empty string and null values surfaced as their own counters
- Per-namespace coverage percentages in a sorted table
- Key chips for quick copy into a fix commit
- Instant client-side diff - no repo access needed