Working with freelance translators well

Most studios that localize do it through freelance translators rather than an in-house team — a handful of people, sometimes one per language, working from files you send them. The relationship is simple on paper: you send text, they send translation back. In practice, the quality of that exchange depends entirely on things that have nothing to do with the translator's skill — the clarity of your scope, the context you give them, and how you treat the relationship over time.

Scope and files, stated plainly

A translator working from an ambiguous file will guess, and guesses are where inconsistent terminology comes from. Before sending anything, be explicit about what is and is not in scope for this batch, what format you need back, and what must not change — string IDs, placeholder tokens, formatting markers.

• Which file or section is being translated, and which parts (if any) are already translated and should be left alone
• The exact format expected back — same file structure, same keys, same encoding
• What must survive untouched: placeholders, line-break characters, HTML-like tags, character limits per field if any
• Where to leave questions or notes rather than guessing

Real context, not just strings

A spreadsheet of isolated strings is one of the hardest things to translate well, because tone, register, and word choice all depend on context the translator cannot see in a single cell. A line of dialogue reads differently depending on who is speaking, to whom, and how urgent the moment is.

Where you can, attach what actually helps: screenshots of the UI the text appears in, a short character or tone note (this character is formal and clipped; this one is playful), and any glossary of names or terms that must stay consistent. None of this needs to be elaborate — a one-page note per character or system is often enough to remove most of the guesswork.

Deadlines and payment are part of the relationship

A deadline set without asking is a deadline the translator either rushes to meet or quietly slips. Both cost you: rushed work has more errors, and slipped deadlines compress your own review time. Ask what is realistic for the volume before you commit a date internally.

Prompt, predictable payment is not a courtesy — it is what keeps a good translator taking your next job first instead of someone else's. Translators who work with many studios prioritize the ones who pay on time and do not haggle after the fact.

A channel for questions, and feedback on the work

Good translators ask questions when something is ambiguous — that is a sign of care, not a problem to route around. Give them a real channel (a shared doc, a chat thread, whatever your team already uses) rather than making them wait for your next email. Answer promptly; a question that sits unanswered for a week either gets guessed at or blocks their whole batch.

Feedback should run both ways. When you find an issue during review — a mistranslation, a broken placeholder, a tone mismatch — tell them specifically, ideally with the exact string and what you'd expect instead. Silence teaches nothing; a translator who never hears back has no way to calibrate to your game.

Why the relationship compounds

A translator who has worked on your game for several updates knows your characters, your recurring terms, and the quirks of your file format. That knowledge is not written down anywhere — it lives in their head, and it makes every subsequent batch faster and more consistent, with fewer questions and fewer round-trip corrections.

Switching translators to chase the lowest price per job resets that knowledge every time. The new translator starts from the same blank context the first one did, and you pay for that ramp-up again — in review time if nothing else, even if the invoice looks smaller. A slightly higher rate with someone who already knows your game is often the cheaper choice once you count the whole cost, not just the line item.

Keep your files clean enough to survive round-trips

Every hand-off and re-import is a chance to lose something — a placeholder gets typed over, a line break disappears, a formula in a spreadsheet overwrites a cell. The translator can only preserve what the file makes preservable. Consistent keys, protected or clearly marked placeholders, and a format that survives being opened in whatever tool the translator actually uses are the foundation everything else in this article depends on. Context and good process cannot compensate for a file that quietly breaks on every round-trip.