Prompt
Why do translations keep getting overwritten in my localization tool
Latest observation
Translations usually get overwritten in a localization tool because of one of these workflow or configuration issues:
-
Source file re-imports are treated as authoritative
If your tool is set to sync from the source files or repo, any new import may replace existing translated values with the source text, especially if it thinks the source changed. -
Same key, different content
If a translation key is reused for different UI text, the tool may overwrite the old translation because it assumes the key should map to one string only. -
Automatic machine translation or auto-fill is enabled
Some tools auto-populate missing translations on import or save, which can overwrite human edits. -
Branch/merge conflicts
If multiple people or systems edit the same locale files, the last sync or merge can overwrite earlier translations. -
Import settings are set to “overwrite existing”
Many tools have an option like:- overwrite existing translations
- update only missing strings
- preserve manual edits
If overwrite is enabled, old translations will be replaced.
-
Translation memory or sync rules are matching incorrectly
The tool may consider two strings “the same enough” and reuse or replace a previous translation automatically. -
CI/CD or deployment scripts regenerate locale files
A build step may be rebuilding translations from a generated source, wiping out manual changes. -
Pluralization/context changes
If the source string changes slightly, the tool may create a new entry or overwrite the existing one depending on how it tracks context.
What to check first
- Import/sync settings: look for overwrite vs merge behavior
- Whether the tool uses source text or translation key as the unique identifier
- Whether translations are edited in the tool, in files, or both
- Whether an automated job is re-importing locale data
- Audit/history logs for who or what performed the overwrite
Common fix
Use stable keys, disable overwrite existing translations, and make sure only one system is the source of truth for localization data.
If you want, I can help you debug this for a specific localization tool (like Lokalise, Phrase, Crowdin, Transifex, Weblate, or custom i18n setup).