FREE
10,000 words offered on sign up

Translate game text without losing your variables

String tables, dialogue exports, quest text and subtitles. Upload the file your engine or tool already produces, tell AI Glot how the world should sound in each language, and get it back ready to load.

Translate game text
AI Glot game localization background

From string table to shipped language in 3 steps

Thousands of lines of dialogue, one job, one set of rules applied to all of it.

1. Upload your string table or dialogue export

CSV and Excel tables, XLIFF, JSON, PO, or a ZIP of subtitle files for cutscenes. Whatever your engine exports is what you send.

Upload a file →

2. Describe the world, not just the language

Register, character voice, invented nouns that must never be translated, length limits for UI. Written as a sentence, applied to every line.

Write your instructions →

3. Load the translated file back in

Same format, same keys, same ordering. Variables, colour tags and formatting codes come back exactly as they went in.

Export result →

Variables and tags are structure, not words

Player names, item counts, colour codes and rich-text tags are recognised and preserved. The sentence is rewritten around them so grammar still works in the target language.

Built for the volume game text actually reaches

Dialogue at scale

Tens of thousands of lines in one job, under one glossary, instead of a spreadsheet split across five translators.

A glossary for your world

Place names, factions, items and abilities keep the same translation in every quest, every patch and every language.

Length rules that hold

Tell it what fits on a button or in a subtitle line and it works within that instead of handing you a layout bug.

Subtitles with their timing intact

SRT files and ZIP bundles of them keep every timestamp and filename, so cutscene audio and text still line up.

Game localization FAQ

Which files can I send from my engine or localization tool?

CSV and Excel string tables, XLIFF, JSON and ARB, PO and POT, Android XML and iOS .strings for mobile titles, and SRT subtitles. A homogeneous ZIP works when you have one file per language.

Will my variables and formatting tags survive?

Yes. Placeholders such as {playerName} or %d, colour and style tags, and engine-specific markup are treated as structure. They are read for context and written back unchanged.

Can I stop invented names from being translated?

Yes, and this is what the glossary is for. Add your proper nouns once and they are held to the same form, or left in the source language, across every file you ever run.

How do I keep UI text inside its box?

State the limit in your instructions. AI Glot works to it while translating rather than handing you strings you have to shorten by hand afterwards.

Can I translate one file into several languages in one go?

Yes. Add every target language to the same job and each one is produced under the same instructions and the same glossary, which is what keeps the terminology aligned between them.

What about a patch that only adds new lines?

Tell AI Glot to keep existing translations and only fill what is empty. Your reviewed text stays exactly as your team approved it.

Is a general AI assistant not enough?

For a handful of lines, yes. For a shipped title it drops rows, renames variables and loses the thread on terminology across a long file. AI Glot applies one set of rules to the whole table and validates the structure before returning it.

10,000 words offered on sign up

Ready to translate your game text?

Create a free account →