Free Tools
Localization Coverage Checker
Paste your base (source) localization file and a translation, and instantly see what's missing: untranslated keys, empty values, and keys that exist in one file but not the other. Works with legacy .strings files and modern .xcstrings catalogs. Runs entirely in your browser.
Why coverage matters
When you add or rename a key in your base language, the corresponding entry in every other language can silently fall behind — the build still compiles, but users see English (or a raw key) where a translation should be. This checker diffs the two key sets so you catch missing, empty, and copy-pasted-but-untranslated strings before you ship, instead of waiting for a bug report or an App Store reviewer to spot the gap.
What it checks
- Missing keys — defined in the base file but absent from the translation.
- Untranslated keys — the translated value is identical to the source string.
- Empty translations — the key exists but its value is blank.
- Extra keys — present in the translation but no longer in the base file.
Want a full pre-submission review?
AcceptMyApp analyzes your metadata, permissions, and privacy setup against Apple's guidelines and surfaces rejection risks before you hit submit.