This walks through one full cycle: preparing your localization target, sending strings to LocHub, running an AI translation job, reviewing the result, and writing it back into your project. It assumes LocHub is already installed (see Installation) and you have picked an AI provider and set its API key, or, for Anthropic, signed in to Claude Code instead (see AI Providers and API Keys).

The example project below is called MyGame; substitute your own project's name.

1. Choose your foreign cultures (optional)

LocHub sets up a Game localization target with a default set of foreign cultures (de, fr, es, ja). If you want different languages, set them first in Project Settings > Plugins > LocHub, under Localization Target > Setup Foreign Cultures, before the next step. Every run of Set Up adds whichever listed cultures the target does not already have, and never removes one — so if you remove a culture in the Localization Dashboard but leave it listed here, the next Set Up brings it back. To drop a culture for good, remove it from Setup Foreign Cultures too. Unknown culture names are skipped and listed in the Set Up summary.

2. Set Up Localization Target

Go to Tools > LocHub > Set Up Localization Target.

This creates the Game localization target if it does not exist yet, or completes an existing one: it adds the foreign cultures from the previous step, points the target's text and asset gathering at your project's Source and Content folders (and those of your enabled plugins), turns on format-pattern and rich-text validation, and makes LocHub the active Localization Service Provider. It only adds what is missing — running it again on an already-configured target is a no-op.

3. Gather text

Use Unreal's own Window > Localization Dashboard, or your project's usual Gather Text step, to gather the Game target's manifest. LocHub Push always sends what the manifest already has — it does not gather text itself.

<aside> ℹ️

if the last Gather Text you ran only covered part of the project, Push warns you before retiring any strings that the manifest no longer has, so a partial gather cannot silently delete strings from LocHub.

</aside>

4. Push

Go to Tools > LocHub > Push (Dry Run) first to see what would be added, changed or retired without changing anything. When it looks right, run Tools > LocHub > Push to actually send the gathered strings to the LocHub service.

Tools > LocHub menu

5. Run a translation job

Open Tools > LocHub > Open LocHub — this opens the LocHub tab inside the editor. Switch to the Jobs tab, pick the culture you want to translate, and optionally narrow the scope to one group or a folder.

1. Click Estimate to see how many strings and requests the job would use, and (for a paid provider) the estimated cost.
2. Enter a Max USD budget if one is shown, then click Run.
3. The job runs in the background — translating, then a deterministic consistency check, then a second AI pass that judges each translation — and the tab shows live progress.

Jobs tab with an estimate

<aside> 💡

to skip estimating altogether, click Run without estimate next to Estimate — the job starts right away with no Max USD limit, and its report shows the real cost.

</aside>