Made for translators
UEExtractor turns .pak and .utoc containers into a locres CSV, and back again. Built for translators, not for engine veterans.
Detected automatically from the folder or executable name
Strings are collected from every asset in the archive, and from the .locres when the game ships one, into the same three column file. Games with no .locres at all, or with a stale one, are the normal case rather than the exception.
The archive is walked asset by asset and the localization is pulled out of whatever holds it. A compiled .locres is one place it can live, and by no means the only one.
DataTablerows and rich textStringTablenamespaced keysTextPropertyblueprint strings.locreswhen the game ships oneEngine version and game type are read from the main executable. Nine titles have their own pak layout, index offset and encryption already wired in.
Run the extraction again after a patch. New rows are added, the Translation column you filled in is written back, and rows the game dropped stay put.
Hand the CSV to OpenRouter, or to any local server that speaks the OpenAI chat API. Batched, resumable, and parallelisable when the model can keep up.
Four moves, and the last one hands you back a file the game will actually load.
Drag the game directory onto UEExtractor.exe, or pass the path as the first argument. A folder in, a CSV out.
aes.txt and the .usmap are picked up from the game folder. The engine version comes from the executable.
Translate in whatever editor you like, or let the built-in pass do it through OpenRouter or a model on your own machine.
Point the tool at the CSV and it writes the .locres. Patch mode keeps the original key order, so every lookup still lands.
Four ways you normally drive the tool. Everything else is a flag sitting on top of one of them.
Most games need nothing at all. These are the two cases where you do, and both are a file drop.
aes.txt--aes=0x...aes.txt goes in the main game folder holding one line: a 32 character hex key.0x when you pass it as an argument instead.--aes:auto looks through the game resources and writes aes.txt for you.*.usmap--mapping..pak and .utoc on its own, so if the text is missing from the CSV, it either sits somewhere the asset scan does not reach, or it was dropped on purpose.Detection matches on the folder name and the main .exe, ignoring spaces, hyphens and underscores, so the version flag is not needed.
Three columns. The middle one is the game text, the last one is yours. The first one is a hash the game looks the string up by.
| key | source | Translation |
|---|---|---|
| 4A6FDB1549E45F6C5D8D739129686E2F | Default | По умолчанию |
| B1C74E0A93D6428FA5C1E07D2B98F3A6 | Press any button to continue | Нажмите любую кнопку, чтобы продолжить |
| E7D05C38F1BA4E6290C3D745B8A26F1 | Inventory full | Инвентарь заполнен |
| 3F92A6D5C0844B1E97AD6205FB3C84E | Quest_Ch03_Retrieve |
The previous source becomes the Translation. This is the path you hit when you export straight from UE4LocalizationsTool.
The Translation column already in the file is written back untouched, so repeated runs change nothing.
It stays in the file. If the game ever rolls back, the string and your translation are both still there.
key,hash,string.url,key,string. Useful when a line has several possible sources.Thirty two of them. Filter by flag name, or by what you are trying to get done.
--version=<ver>-vEngine version or game name, detected automatically when omitted. Use -v=UE5_6 to force one, or -v=GAME_NevernessToEverness to enable NTE encrypted locres output.
--aes=<key>-aA 32 character hex AES key. It must start with 0x.
--aes:auto-a:autoFinds the AES key in the game resources and writes aes.txt to the root of the folder. Directories only.
--mapping-mapLoads the .usmap from a path you give directly, instead of hunting for it in the game folder.
--updateChecks GitHub for a newer build and updates in place when there is one.
--path=<virtual_path>-pRestricts processing to assets under one internal path, for example --path=HT/Content/Localization. Case insensitive substring match. Far faster than a full scan when you already know where the strings live.
--all-allProcesses every folder in the archive, including effects, meshes and sounds. Slower, and it finds strings you would otherwise miss.
--read-locres-rlAlso reads the .locres binaries themselves, for games that keep their localization in pre-compiled .locres files instead of inside assets, NTE among them. Keys and hashes come from the game, so a v3 round trip stays valid.
--skip-uexp-s:xpSkips .uexp files during processing.
--skip-uasset-s:etSkips .uasset files during processing.
--pickyStrict mode. More detail per file, useful when a game will not cooperate.
--verbose-vbPer file processing detail and diagnostics, in place of the progress bar.
--locres=<1|2|3>-lWrites a .locres of that version after processing. Version 1 is Compact and works from UE4.0, version 2 carries the DataTables inside the file and needs UE4.20, version 3 needs UE5.8. Default is 1. Hand an engine older than 4.20 a version 2 file and it reads that file at offsets that mean nothing to it: the game loads invisibly in the background and keeps allocating until the machine runs out of memory, taking the whole system with it. The only way out is force-killing the process, or rebooting. Newer engines just refuse the file, which is what makes the mistake easy to miss.
--extract-locresDumps the raw .locres binaries from the archive into the output directory. Handy for inspection, and required as a template for patch mode.
--table-format-tfSwaps the standard comma separator for a pipe.
--headmark-mWrites a header row and a footer into the .csv.
--hash-hAdds the combined source hash to the output: key,hash,string.
--url-urlAdds the path of the file each string came from: url,key,string.
--qmarks-qForces quotation marks around text strings no matter what the source looks like.
--table:only:key=<name>-t:o:kKeeps only the entries whose key or name matches the given value.
--search-sAt the end of the run, reports every occurrence of the string you searched for.
--no-underscore-n:unDrops lines built out of identifiers, such as ex_string.
--no-uppercase-n:upDrops lines that are entirely uppercase, such as EXAMPLE. It clears the constants and debug leftovers out of the table.
--lang:from=[code]-l:fSource language for the translation pass, for example en.
--lang:to=[code]-l:tTarget language for the translation pass, for example ru.
--api:key=<key>-a:keyAPI key for OpenRouter, or for any server that requires authentication. Not needed for local models.
--api:url=<url>-a:urlCustom OpenAI compatible base URL for a local model, for example http://localhost:11434/v1/ for Ollama. Leave it out to go through OpenRouter.
--api:model=<model>-a:modelModel to translate with. An OpenRouter slug such as tngtech/deepseek-r1t2-chimera:free, or llama3 on Ollama.
--batch-size=<n>-bsSegments per translation request, 150 by default. Lower it for models with a small context window.
--parallel=<n>-parConcurrent translation requests, one by default. Raise it for a local model on decent hardware.
--translate-only-t:oSkips extraction entirely and translates the CSV files from a previous run, picking up where the last pass stopped.
--helpPrints the built in reference.
Nothing matches that. Clear the field to see all of them again.
The idea was to get text out of an Unreal Engine game so somebody could translate it. Everything running today was written from scratch in C#, mostly by the maintainer, with the rest coming from people who had a localisation to finish.
Download a release, drop a game folder on the executable, and the CSV is yours to fill in.