JSON Localization Validator
A JSON localization validator checks whether translated JSON still matches the source structure your application expects.
Examples
{
"profile.greeting": "Hello {name}",
"profile.edit": "Edit profile"
}{
"profile.greeting": "Bonjour {username}",
"profile.save": "Enregistrer"
}Missing key: profile.edit
Extra key: profile.save
Placeholder mismatch: {name} is missing; {username} is extraThe file is valid JSON, but the app may still render the wrong button set or fail runtime interpolation.
What a validator should verify
A syntax validator only answers one question: can this file be parsed? A localization validator answers the next release question: does this target file still match the source file the app was built around?
Developers care about paths and runtime tokens. PMs and vendors care about delivery completeness. QA cares about whether the delivered file will create avoidable build or UI defects.
Manual checks versus scan checks
Manual spot checks work for a few keys but do not scale well across nested JSON, repeated placeholders, inline tags, or strings that look intentionally unchanged. Reviewers also tend to focus on wording, not file drift.
LocaleQA parses both JSON files, flattens string paths, and applies the same checks every time. It checks JSON files; it is not translation review or translation generation.
When to run it
Run validation when a vendor returns translated JSON, before developers merge resource files, and before QA starts a localized build. If the report is clean, the remaining review can focus on product behavior and language rather than file integrity.