How to merge multiple json i18n translation files
- Step 1Identify the translation files to merge — Gather the partial translation JSON files: a base file with common strings, a feature-specific file, and any namespace overrides. The base file is your first (lowest priority) input.
- Step 2Paste each file in priority order — Paste the base translations first, then the feature-specific or more specific translations as subsequent inputs. Later files override conflicting keys in earlier files.
- Step 3Review the merged output — Verify the merged translation file has all expected keys. Check that namespace objects are merged (not replaced): the auth.login.title key should exist even if auth.login.title was only in one input file.
- Step 4Save as the combined locale file — Download the merged output as en.json, de.json, or the locale filename for your project. Replace the old combined locale file with the merged version.
Frequently asked questions
How do I detect missing translations after merging?+
After merging, use the JSON Diff tool to compare the merged translation file against a reference locale (usually English). Keys present in the reference but absent in the merged target file are missing translations that need to be added.
What happens when two input files have the same translation key with different values?+
The later input wins — its value replaces the earlier value for the conflicting key. This implements the override behavior: a feature-specific translation file can override a base translation file's generic value for a specific key.
Is the translation content transmitted to JAD Apps?+
No. Merging runs entirely in your browser. Translation strings, locale-specific content, and product terminology are never transmitted to JAD Apps servers.
Privacy first
Conversion runs locally in your browser. No file is uploaded — only metadata counters are saved for signed-in dashboard stats.