The quality of a localization depends a lot on what the translator receives. A spreadsheet of 8,000 strings with no context forces guesswork; the same strings with screenshots, notes and a glossary produce a translation that feels written for the game. This checklist covers what we ask for when we start a project, and what makes the biggest difference.
1. String files in an editable format
- Export text as CSV, XLSX, JSON, XML, .po or your engine’s native localization format.
- Keep one column (or field) for the source text and one for the translation.
- Include a unique string ID for each line, so updates and fixes are easy to track.
- Do not send text inside code files or scenes if you can avoid it.
2. Context for every tricky string
A short note saves a lot of questions: who is speaking, to whom, where the text appears (button, tooltip, dialogue, item name) and what it refers to. A column with the speaker name or the scene is especially useful for dialogue.
3. Screenshots and gameplay video
Even a 10-minute gameplay video or a folder of UI screenshots helps the translator understand tone, space and how text is used. For menus and HUD, screenshots are often more useful than any written description.
4. Character limits
If a string must fit in a fixed space, write the limit in the file. Polish text is frequently longer than English, so knowing the limit in advance lets the translator choose a shorter phrasing instead of having it cut off in the build.
5. Variables, tags and plurals
- Mark placeholders clearly (
{player_name},%d,<color>) and explain what they will contain. - Tell the translator if the word order can change around variables.
- Use your engine’s plural support instead of “1 item(s)”: Polish needs several plural forms.
- Avoid building sentences from fragments; give translators the whole sentence.
6. Gender and form of address
Can the player choose a male or female character, or a non-binary option? Does the game address the player directly? In Polish this affects verb and adjective endings, so it needs to be decided before translation starts. We wrote about this challenge in detail in Why translating “you” into Polish is harder than it looks.
7. Glossary and names
List key terms: character names, places, factions, items, skills and game mechanics. Mark which names must stay in English (trademarks, proper names) and which can be translated. A glossary keeps the terminology consistent across thousands of strings and future updates.
8. Style guide and references
Describe the tone in a few sentences: is the game serious, sarcastic, cosy, dark, full of puns? Are there characters with a distinctive way of speaking? Mention games, books or films with a similar feel. If you already have other language versions, say which ones the community liked.
9. Build access for testing
A Steam key or test branch lets the translator check text in context and, later, run LQA. Debug options or save files that unlock later chapters save a lot of time.
10. A contact person and update plan
Name one person who can answer questions, and agree how new and changed strings will be marked in future updates (for example a “status” or “changed” column). This keeps patches fast and cheap.
Quick checklist
- Editable string files with unique IDs
- Context notes and speaker names
- Screenshots or a gameplay video
- Character limits
- Clearly marked variables and plural support
- Decisions on gender and form of address
- Glossary of names and terms
- Short style guide
- Build access for review and LQA
- Contact person and update process
For the technical side of preparing your game (font support, text expansion, concatenation), see our developer’s guide to Polish localization.
Planning a Polish release? Send us your string count, a few screenshots and your target date, and we will reply with a fixed quote and timeline. Get a free quote or see the games we have worked on.



