Unreal Localization Dashboard ready
Follows standard Unreal PO syntax so re-importing never triggers missing key warnings or parse failures.
Supported formats:.po.locres.json
Translate Unreal Engine 4 & 5 localization files cleanly
Upload gettext PO files generated by the Unreal Localization Dashboard. AI Glot preserves namespaces, context strings, and plural rules for error-free builds.
Sleep je PO-bestand hierheen
Tot 2 MB, vijf bestanden per dag. Niets te installeren, geen account nodig.
Built for Unreal Engine 4 and 5 game developers
Unreal Engine uses msgctxt for string namespaces and arguments like {ItemName} or {0}. AI Glot protects these identifiers byte for byte.
Dialogue context preservation
Comments and context metadata in the PO file are passed to the AI to ensure accurate voice acting tone.
FText placeholder integrity
Positional arguments ({0}) and named parameters ({PlayerName}) stay untouched.
Zero build pipeline disruption
The translated PO compiles directly into binary LocRes files inside Unreal.
Localize Unreal Engine games in 3 steps
Native workflow for Unreal Localization Dashboard.
Export PO from Unreal Localization Dashboard
Export your culture targets as portable object (.po) files from the Unreal Editor.
Upload PO file →product-catalog.csvwebsite-content.xlsxmobile-app.xliffcourse-subtitles.zip
Review translation plan
Ensure msgctxt keys, dialogue namespaces, and FText arguments remain uncorrupted.
Review translation →How to translate this file?
Translate into German and Spanish. Keep product names in English, use our glossary, and make the copy sound natural for e-commerce.
Glossary applied
Translation planReadyUpdated
LanguagesEN → DE, ES
Scope742 cells
Volume8,490 words
Existing translationsKeep unchanged
Start translation
Refine your instructions
Import and compile text in Unreal
Import the translated PO file back into the Localization Dashboard and compile text.
Download PO file →fr-FR
de-DE
es-ES
ja-JP
website-content_localized.xlsx
Unreal Engine localization FAQ
How does AI Glot fit into the Unreal Engine Localization Dashboard workflow?
In the Unreal Localization Dashboard, run "Gather Text", export your culture target as a .po file, translate it in AI Glot, then re-import the .po and click "Compile Text".
Are msgctxt string namespaces and context metadata preserved?
Yes. AI Glot's gettext engine strictly protects msgctxt, msgid, and line comments (#.), translating only the target msgstr strings.
How are Unreal Engine plural forms (msgid_plural) handled?
Target language plural formulas (e.g. 3 plural forms in Polish, 2 in French) are respected according to gettext standards, ensuring correct runtime plural resolution.
Can I translate Unreal Engine 5 String Table CSV files?
Yes. You can upload Unreal String Table CSV files containing Key, SourceString, and MetaData columns. Only the SourceString column is localized.
Are FText format arguments like {Arg} and rich text tags safe?
Yes. All bracketed arguments ({0}, {ItemName}) and Unreal rich text XML tags are recognized as immutable tokens.
Why do standard translation tools corrupt Unreal PO files?
Generic tools often strip gettext header metadata, break multiline string wrapping, or encode invalid UTF-8 bytes that cause Unreal Engine text compiler errors.
Is this compatible with Unreal Engine 4 and Unreal Engine 5?
Yes. Fully compatible with UE 4.27 through UE 5.4+ localization pipelines.
Can I test translating an Unreal PO file for free?
Yes. Drop your .po or .csv file into the free tool above to translate sample strings immediately without sign-up.