Game Localization · All Services
Unreal Engine Game Localization — Pipeline, Tools, and Common Issues
Native translators. Engine-specific expertise. LocQA in your build. Get a free quote →
Unreal Engine has one of the most capable native localization pipelines in any game engine — FText, the Localization Dashboard, StringTable assets, and built-in culture code support. The challenge for teams shipping multilingual games is not the tooling: it’s knowing which features to use, in which order, and where the edge cases are. SandVox handles Unreal Engine localization projects for PC, console, and mobile — from string export to LocQA in a working build.
Common Localization Challenges
- FText vs FString vs plain literals — only FText strings are tracked by the Localization Dashboard; strings using FString or raw C++ literals require manual audit before localization begins
- Culture code configuration — Unreal uses IETF BCP 47 culture codes but the culture-to-asset mapping requires explicit project configuration, especially for zh-CN vs zh-TW and pt-BR vs pt-PT
- CJK font rendering — Unreal requires per-font glyph range configuration for Chinese, Japanese, and Korean; missing glyph ranges cause characters to fall back to default glyphs or render as boxes
- RTL language support — Arabic and Hebrew require specific text layout configuration in UMG; standard left-to-right widget layouts need mirroring for RTL locales
- Voice-over subtitle synchronization — lip sync and subtitle timing must be managed separately per language when replacing or dubbing audio
- Localization Dashboard batch export — large projects with many string tables benefit from command-line export automation rather than manual Dashboard operations
What We Deliver
- String audit — identifying all FText, FString, and hardcoded literals requiring localization
- PO file export, translation, and import via Unreal’s Localization Dashboard
- CJK font configuration and glyph range audit for Chinese, Japanese, and Korean builds
- RTL layout configuration and LocQA for Arabic and Hebrew UMG widgets
- LocQA — in-engine testing across all target language builds including layout, truncation, and font rendering
- Voice-over direction and subtitle timing for dubbed language builds
- Post-patch localization for Engine and project content updates
How a Project Works
- Project scoping: string count audit, culture code configuration review, engine version and platform targets confirmed
- String export via Localization Dashboard or command-line to PO/XLIFF format
- Translation by native-language translators with Unreal-specific context metadata
- Import and culture asset packaging via Localization Dashboard
- LocQA across all target language builds — layout, truncation, font rendering, and functional testing
Languages Available
Japanese · Korean · Simplified Chinese · Traditional Chinese · German · French · Spanish (ES) · Spanish (LATAM) · Brazilian Portuguese · Italian · Russian · Polish · Arabic · Dutch
Frequently Asked Questions
How does Unreal Engine’s localization system handle Chinese and Japanese?
Unreal supports CJK natively but requires per-font glyph range configuration to ensure all characters render correctly. Static glyph ranges must cover every character in your translated content — or dynamic font loading must be enabled. SandVox audits glyph coverage before translation begins to ensure no missing character regressions at LocQA.
Can SandVox work directly with our Unreal project files?
Yes. We can work from PO file exports (engine-standard format), XLIFF, or directly with your Localization Dashboard project structure. We return translated files ready for import, alongside Translation Memory and a terminology glossary.
Does SandVox handle Unreal voice-over localization alongside text?
Yes. We coordinate text and voice-over localization in parallel, including subtitle timing adjustment for dubbed builds where audio length differs from the English original. Lip sync is handled with your animation team — we provide guidance on length constraints per line.
What Unreal Engine versions do you support?
UE4 and UE5 — both use the same Localization Dashboard pipeline with minor configuration differences. We note engine version during scoping and flag any version-specific LocQA requirements.
Start Your Unreal Engine Game Localization Project
Tell us your word count, target languages, and timeline. We’ll send a fixed-price quote within one business day.
Frequently Asked Questions
Unreal Engine has a built-in Localization Dashboard (accessible via Tools > Localization Dashboard) that manages string collection, translation, and compilation into .locres binary resource files. Strings are stored in .po (Portable Object) files for editing — the industry-standard format for localization tools. The localization pipeline involves: gathering all source strings (GatherText commandlet), exporting to .po files, translating, importing translated .po files, and compiling to .locres. SandVox works natively with Unreal’s .po export format and can configure the full Unreal localization pipeline for new projects.
Unreal Engine 5 has improved BiDi (bidirectional text) support, but RTL languages (Arabic, Hebrew, Urdu) still require attention: UMG (Unreal Motion Graphics) text widgets must have their text wrapping and alignment configured for RTL, RichText blocks may need RTL-specific adjustments, and 3D text in the world must be tested in-engine. The default Slate text widget in UE5 supports basic RTL, but complex UI layouts (forms, settings menus, HUDs) may require explicit RTL handling. SandVox provides RTL technical QA for Unreal Engine games as part of Arabic or Hebrew localization projects.
Blueprint variables that display text to players must use the FText type (not FString) to be included in the localization pipeline. Strings hardcoded as FString in Blueprints are invisible to the localization gathering process. Best practice is to use NSLOCTEXT or LOCTEXT macros in C++, or the FText literal in Blueprints, for all player-visible text. SandVox’s pre-localization audit reviews your project’s string usage and flags all non-localizable FString usage before translation begins, preventing gaps in the localized build.
Unreal Engine game localization cost is driven by word count, not the engine. Unreal projects often have larger word counts than equivalent Unity games due to the genre of games built in UE (shooters, open-world, AAA narrative games). A mid-size UE5 game (50,000–200,000 words) into German costs $6,000–$44,000 for text-only. Voice-over re-recording for a full UE5 narrative game adds $30,000–$500,000 per language. SandVox handles complete Unreal localization pipelines including .po workflow, .locres compilation, and platform QA.