Supported engine · Unity

Full — rebuilt & played

Unity game translator — translate Unity games end-to-end

A large share of modern indie games — RPGs, visual novels, and simulation titles — ship on Unity. RuneTranslate translates the text those games externalize: TextAsset payloads (JSON / CSV / TSV / plain-text scenario blobs) and MonoBehaviour string fields packed inside .assets, level files, and AssetBundles (including single-bundle data.unity3d games), plus loose script files under StreamingAssets. RuneTranslate reads and writes the binary assets itself, all in a per-project workspace so the original game stays untouched. MonoBehaviour text is handled on both Mono and IL2CPP builds — on Mono the type trees come from the game's Managed/*.dll, and on IL2CPP RuneTranslate reconstructs them from GameAssembly.dll + global-metadata.dat (needs parseable metadata). It also reads packed Addressable bundles and injects a non-Latin fallback font for CJK and other scripts. On Mono builds it also reads string literals compiled into Assembly-CSharp.dll and leaves out the ones the code uses as names or keys; text compiled into an IL2CPP build's native code is out of scope. Check a few screens of the exported game before you share it.

Glossary tip for this engine

Unity VN/RPG scripts are usually externalized as JSON or CSV tables, so character names and recurring terms appear hundreds of times across many TextAssets. Providers will rephrase them inconsistently batch to batch. Glossary the protagonist, party, recurring NPCs, place names, and any signature skill or system term up front so every TextAsset and StreamingAssets file renders them identically.

Glossary 101

How to translate Unity

  1. STEP 1

    Open the Unity game folder

    Point RuneTranslate at the game directory (the one containing the <Name>_Data folder). Engine detection looks for globalgamemanagers / data.unity3d / resources.assets. The asset reader is built into RuneTranslate, so there is nothing else to install.

  2. STEP 2

    Extract externalized text

    RuneTranslate scans the serialized files for TextAsset and MonoBehaviour strings in the source language (Japanese by default; set any supported source language per project), plus loose script files under StreamingAssets. Structured payloads (JSON / KAG / HTML) are sliced into individual translatable lines so the file structure round-trips intact.

  3. STEP 3

    Translate via your preferred provider

    DeepL is a strong default for narrative dialogue; OpenAI GPT-4o or Anthropic Claude handle stylized speech and onomatopoeia better. Free Google Translate or a local model (Ollama / LM Studio) covers menu strings and item names. Provider routing can split short strings to a cheap lane.

  4. STEP 4

    Export a translated build

    On export, RuneTranslate copies the game and writes the translated strings back into the asset files and StreamingAssets scripts in place. The translated build runs like the original — no manual asset juggling.

Supports

  • TextAsset payloads (JSON / CSV / TSV / .txt / .ks scenario blobs)
  • MonoBehaviour string fields on Mono AND IL2CPP builds — type trees come from Managed/*.dll (Mono) or are reconstructed from GameAssembly.dll + global-metadata.dat (IL2CPP)
  • Loose StreamingAssets script files (.json / .txt / .csv / .ks / .js / .html / …)
  • .assets, level files, and AssetBundles incl. single-bundle data.unity3d + packed Addressable bundles
  • Per-project workspace in the app's game cache (by default userData/unity-workspace/<projectId>/, movable in Settings > App > Game cache)

Limitations

  • String literals compiled into an IL2CPP build's native code (GameAssembly.dll) are not translated. On Mono builds, literals in Assembly-CSharp.dll are, except the ones the code uses as names or keys
  • IL2CPP MonoBehaviour support needs a parseable global-metadata.dat; heavily obfuscated metadata may not reconstruct
  • AssetBundles in a packed format RuneTranslate does not recognise are skipped

Related reading

Related reading

Related reading

Documentation

Other supported engines