Software teams rarely translate neat documents. They translate files full of keys, placeholders and nested objects. One careless edit can break a screen or print a raw variable name to users. A clear workflow keeps those files safe while still giving translators the context they need.
Why app files are different
A JSON file mixes text meant for people with code meant for machines. Translators must change the first and never touch the second.
A good process separates the two before anyone starts work. That single step prevents most production bugs.
Keys stay, values change
Each entry has a key, which the code reads, and a value, which users see. Only the value is translated. If a key changes, the app can no longer find its text.
Lock keys in your tooling so translators cannot edit them, even by accident.
Protect the placeholders
Strings often contain markers such as names, counts and dates inserted at runtime. These must appear in the translation exactly as written, though their position in the sentence may change.
Quality checks that flag missing or altered placeholders save a lot of testing time later.
Give translators context
A short string like Save can mean very different things in other languages. Add notes, screenshots or character limits so translators know where the text appears.
Context reduces questions, speeds up delivery and improves quality at the same time.
Plural and gender rules
Many languages have more plural forms than English. Your files need a format that supports them, and translators need a way to supply each form.
Check how your framework handles plurals before translation starts, not after the first bug report.
Choose the right platform
Games push this workflow harder than most software. A single title can hold tens of thousands of strings, from dialogue and quest text to store descriptions, and every one of them has to survive the same key, placeholder and plural rules described above. That is why video game localization treats the file pipeline as part of the translation itself, with locked keys, protected variables and in-context review built in from the start. Studios that set this up early ship each language version on release day instead of patching broken text afterward.
Passing files by email does not scale. translation workflow management software keeps files, glossaries, memories and reviews in one place, so developers and translators work from the same source.
Look for tools that read your file formats natively and return files ready to commit.
Connect to your repository
Manual uploads cause delays. Integrations that pull new strings from your repository and push finished translations back keep releases on schedule.
Automated sync also reduces the risk that someone uses an outdated file.
Use translation memory
Interface text repeats a lot. Buttons, errors and menu labels appear across many screens, and memory ensures each one is translated once and reused everywhere.
Over time this lowers cost and keeps wording consistent across the product.
Add machine translation carefully
Machine translation can create a first draft for low risk strings. Reviewers then check the results, especially short texts where context is thin.
Avoid sending legal, safety or brand critical messages straight from an engine to production.
Review in context
Translators work best when they can see the text in the interface. Preview links or screenshots let reviewers check length, tone and layout before release.
Long German or Finnish words often overflow buttons, so test those early.
Handle updates smoothly
Products change weekly. Your workflow should detect new and changed strings automatically and send only those for translation.
Sending the full file every time creates noise and raises the chance of errors.
Version control for languages
Treat translation files like code. Use branches, reviews and clear commit messages so everyone can see what changed and why.
This makes it easy to roll back a faulty translation without touching other languages.
Test before release
Run a pseudo translation first. It replaces text with longer accented characters and reveals layout problems and hard coded strings before real translation begins.
After translation, run a short test in each language to confirm that nothing is cut off or missing.
Set up quality checks
Automated checks can find missing tags, duplicate spaces, number mismatches and glossary violations. Run them on every delivery.
A short checklist for human reviewers adds the final layer of safety.
Keep a glossary
Product names, feature names and key terms should be defined once and used everywhere. Store them in a shared glossary linked to your project.
It also helps new translators get up to speed in hours instead of days.
Measure and improve
Track turnaround time, number of review comments and bugs linked to text. These numbers show where the workflow is strong and where it needs attention.
Review them every quarter and adjust the process with your team.
Roles and responsibilities
Decide who owns each step. Developers export strings, a localization manager assigns work, translators deliver, and a reviewer approves. Clear owners prevent files from sitting unseen for days.
Write the process on one page and share it with everyone involved, including new hires.
Where to start
If you want a practical walkthrough, this guide to using a translation tool for JSON files explains the steps in more detail. Start with one project, one repository and two languages.
Once the process works, add more languages and automate the remaining steps. Open communities such as Mozilla localization resources share practical guidance on app localization.