In almost every game localization project, there is always a constant — translators will ask questions due to the lack of context and testers will complain about issues that will require a rewriting of the game code due to some language-specific issues. As a result, developers need to spend a good deal of time fixing localization bugs, and depending on the number of the affected languages, this can delay localized builds and increase localization costs. However, many localization issues can be avoided if the internationalization phase meets a minimum level of quality standards. This is especially important now that many indie developers have arisen, as they often are not aware of the impact that internationalization can have on the translation and quality assurance stages. Thus, the aim of this presentation is to give some internationalization best practices for beginner and experienced game developers from a translator’s point of view that will help them to better focus on the game functionality by reducing potential localization issues at a later stage.