Translate Unity JSON, CSV and XLIFF files with human-level AI. Keep your game's voice, and get 100% protection for Smart Strings, variables, rich text tags and table structures.
Same format in and out. Keep your existing import workflow.
One renamed token is enough. A plain chat prompt is not a schema validator. Without syntax protection, a translated key, a missing CSV quote or a stripped rich text tag turns a routine import into an afternoon of file repairs.
The damage shows up in the Editor and in play: parsing exceptions, String Table entries that no longer match their shared keys, or reward text that breaks when the game passes a runtime argument. Your team ends up diffing files instead of testing the next build.
Qopywriter.ai protects Unity Smart Strings, formatting variables, rich text markup and table structures throughout translation. Player-facing language changes. The contract your game depends on does not.
{0}, {PlayerName} and named selectors unchanged.
Use CSV or XLIFF from the Unity Localization package, or JSON from your project's export pipeline. This Unity localization tool translates the text without rewriting the structure around it.
Keep object keys, nesting and escape sequences fixed. Translate the player-facing string values, then send the file back through your JSON loader or conversion script.
{
"ui.play": "Jouer",
"quest.reward":
"Vous recevez {0} pièces."
}A comma belongs inside dialogue, not in a new column. Translate target-locale cells while preserving headers, shared key IDs, quoting and row boundaries.
Key,Id,French(fr)
ui.play,104,Jouer
quest.reward,105,
ui.confirm,106,"Oui, continuer"Translate target segments without rewriting unit IDs, XML namespaces or inline codes. Keep source text and contextual metadata available for review.
<trans-unit id="104">
<source>Play</source>
<target>Jouer</target>
</trans-unit>.po
Use AI PO translation for gettext-based tools and custom importers. Message IDs, context and format variables stay protected while msgstr content is translated.
GUIDs, Addressable references and asset paths stay outside the translation pass. Translate labels and descriptions, not the links to your audio, textures or prefabs.
A clean import is only half the job. Your veteran ranger should not sound like a help desk, and the “Loadout” button should not change names halfway through a mission. Our game localization AI delivers human-level linguistic accuracy, with the gaming terminology and context your strings depend on.
“Charge” means something different in a combat tooltip and a checkout screen. Context drives the translation.
Keep the captain terse, the merchant charming and the villain cold. Dialogue retains its intent, register and personality.
Abilities, item names and UI labels stay consistent across menus, quest text and dialogue. No random switch from “stamina” to “energy.”
“Eyes up, rookie. We're not done yet.”
« Ouvre l'œil, le bleu. On n'a pas fini. »
The same terminology follows the player from the menu to the mission.
Unity string table translation should fit your production workflow, not replace it. Work at the file level, keep your existing package setup and leave engine code alone.
Export your String Table Collection as CSV or XLIFF. For JSON, use your project's exporter. Keep stable keys and the dialogue context carried in your source metadata.
Upload your file and select the locale. AI translates player-facing text while protection keeps variables, rich text and table structure out of the translation pass.
Download the same format and use the matching Unity importer or JSON adapter. Run a variable-driven line, a plural and a rich text label in Play Mode before your next build.
Every plan includes JSON, CSV and XLIFF translation, Smart String protection and 100+ languages. Test your import workflow with a free trial first.
For a focused localization pass.
For new locales and regular updates.
For shared production workloads.
One annual plan for ongoing releases.
Working with a custom exporter or a larger studio pipeline?
Talk to our teamPractical answers for developers, technical artists and narrative teams using Unity localization files.
Ask about your file structure ↗{PlayerName} and {CoinAmount}, indexed arguments such as {0}, and Smart String control syntax are protected. The language changes; selector names, formatter names and runtime arguments do not. Linguistic content inside formatting branches is translated separately from the control syntax.Key and Id columns and the correct target-locale column. Keep those mappings, delimiters and quoted fields fixed while translating locale text. Qopywriter.ai protects that structure, so dialogue containing commas or quotation marks does not spill into another column during import.msgstr content is translated. CSV and XLIFF remain the String Table interchange paths in the Unity Localization package.<b>, <color=#FFD700> and <sprite index=0> keeps its tag names and attributes. Matching tags remain paired around the translated text. Asset GUIDs, addresses and paths are not language content and stay outside translation.{0}, a named argument, a plural and a rich text label in Play Mode. Test TextMeshPro font assets, fallback locales and your longest menu labels at the smallest supported resolution. That catches missing glyphs and text overflow before the next build.Take the table that's holding up your release. Translate your Unity game files with protected keys, variables and markup, then bring them back into the Editor.
