The most expensive localization mistakes happen before a single string is translated. They happen in the design phase, in the writing process, in the technical decisions about how text is stored and displayed. By the time files reach a localization team, the damage is often already done.
We’ve seen it countless times: hardcoded strings that can’t be extracted without engineering work, UI elements with fixed widths that can’t accommodate German compound words, jokes built on English puns that have no equivalent in any of the target languages, date and number formats baked into the code, character limits that work in English but truncate every Asian language.
Each of these issues creates delays, additional costs, and compromises in the final quality of the localized product. The good news is that all of them are preventable — if you bring localization thinking into your production pipeline early enough.
Here’s what that looks like in practice. Write with localization in mind from the start: avoid idioms that don’t travel, flag culturally specific references, leave room for text expansion (German and French typically run 30% longer than English). Build your UI with flexible containers. Store all player-facing strings in extractable files. Establish a glossary of key terms — character names, item names, game-specific vocabulary — before translation begins.
Equally important: involve your localization team early. At Moonlit, we offer pre-production consulting precisely because the conversations we have at the design stage save our clients significant time and money downstream. We help you identify the landmines before you step on them.
Localization done right starts on day one. And the studios that understand this ship better games, faster, and at lower total cost.