Knowledge Base

Documentation to help you use the POEditor localization platform effectively

Unreal Engine localization

Owner

To localize an Unreal Engine game with POEditor, export the gathered text from Unreal's Localization Dashboard as .po files, import the source file into a POEditor project, translate it, then import the translated .po files back into Unreal. Here's how to set it up.

1. Export your text from Unreal Engine

In Unreal Engine, open the Localization Dashboard from the Tools menu. In the toolbar of the Cultures section, click Gather to collect the text for your localization target, then Export to save it as .po files. Unreal creates one .po file for each culture; the file for your native culture holds the source texts you'll translate.

The Unreal Engine steps in this article match Epic's Localization Dashboard documentation as of November 2026. If your editor looks different, check the latest version there.

2. Set up your localization project

Log in to your POEditor account (if you don't have one, you can create one for free), create a project and add the source and target languages to it.

Then, import the source PO file exported from Unreal Engine to your project, using Import in the project page. The msgids from your .po file will be imported as the project's terms.

Import Terms page - POEditor translation management system

If your msgids are keys and not the strings in the source language, use the option Also import translations to a language to add the source strings from msgstr to the source language in your POEditor project (they will be imported as translations). Then set this language as Default Reference Language in the project's settings.

Other import options are available, such as integrations with Git hosting services or API import, which allow you to automate the import.

After importing the source strings to the project, you can start assigning people to your project.

After importing the source strings, you can assign people to your project. Users who should be able to manage the project terms should be added as admins, while those whose access should be limited to specific languages can be added as contributors.

3. Translate your game text

Choose how to translate each language:

Translation memory (available from the Start plan) suggests earlier translations of identical strings, and QA checks and QE feature catch issues before export.

4. Export the translated .po files

Whenever you want, export the localized .po files using Export in the translation pages.

If you want to include a validation step, use the proofreading option. The proofread flag can be used as a filter for all export options.

Export proofread strings for Unreal Engine- POEditor Localization Platform

5. Import the translations back into Unreal

Put each translated .po file back in place of the one Unreal exported for that culture. Then, in the Cultures toolbar of the Localization Dashboard, click Import and then Compile, so your game uses the new translations.

Unreal only imports translations for text it has already gathered. If you've added new text since the last export, run Gather again before importing.

If you want to automate the import/export, use the POEditor API, one of the integrations with code hosting platforms or Workflows.

All the export options are described here, and best practices for syncing your translations with the localization files in your repositories can be found here.

Additional help

Related articles