Localization Checker

Localization QA in the Unity Editor

Check your localization
before your players do.

Give every language a test run.

Localization Checker helps you test localized UI in Unity. Find text overflow and overlaps, missing glyphs, placeholder and rich text errors, and untranslated text. Check your selected languages and resolutions in one scan, then use Play mode to check screens created or updated by your game.

It checks existing translations; it does not translate or rewrite them.

Unity Asset Store · coming soonTuanjie Store (China) · coming soonitch.io · coming soon Read the documentation

Supports Unity 2022.3 LTS and later, including Unity 6, and Tuanjie Engine 2022.3. Checks TextMeshPro and legacy UI Text. UI Toolkit checks require Unity 6.

Scan once. See every language.

  1. The top of the plugin window: Translation files, Scope set to Open scenes, Languages to check, Language of the texts set to en, and Resolutions set to 1920x1080.

    Your translations, languages and resolutions

  2. every language × every resolution × 5 checks

    One scan

  3. The overview matrix after a scan: rows de, ja, (no language) and Sources; columns Overflow, Missing glyphs, Placeholders, Rich text tags and Translation; red cells for 2 German overflows and 15 Japanese missing glyphs.

    Which language, which problem: one table

  4. The heat map in the Scene view: the Demo main menu with numbered colored frames on its title and buttons, and a legend from 1 Overflows to 5 Nearly overflows.

    Marked on your own UI, numbered by problem

What it finds

Unity Scene view showing the German Quit label, “Spiel beenden”, extending beyond its button, with a red outline and the label “de · Text overflows · 1920x1080”.
The German Quit label does not fit. The plugin marks the overflow measured in Unity.
The plugin’s issue list after a scan: critical “Missing glyphs” rows for Japanese texts such as 星明かりの物語 and スタート, one row per text, each marked Engine Metadata and ja.
Japanese strings the Demo’s font cannot draw: one scan lists them, one row per text.

One button, nine languages

Unity Scene view showing the German Quit label, “Spiel beenden”, extending beyond its button, with a red outline and the label “de · Text overflows · 1920x1080”.

Browser animation of nine language versions, including English: German text overflows, while the sample fonts lack Chinese, Japanese and Korean glyphs. Diagnostic frames and tags mark both issues.

Missing characters, listed by font

The overview after a scan: the language-by-check matrix counts 15 missing glyphs for Japanese; Language coverage marks Lato SDF as having no Japanese characters; “The scan’s missing characters by font” lists Lato SDF.asset with 56 characters missing and a “Copy for Font Asset Creator” button.
The overview counts missing glyphs per language, shows which font assets cover which language, and lists the missing characters by font. One click copies them for Unity’s Font Asset Creator.

What it checks

  • Text overflow and layout

    Measure a copy of your UI with Unity’s text engine for each selected language and resolution. Find overflow, truncation, and text that Auto Size makes too small. For supported text components, the engine tests suggestions such as the largest font size that fits, Auto Size, or wrapping.

  • Missing glyphs and font coverage

    Check whether the assigned font and its fallback fonts can display your text. Review font coverage against the built-in language character sets and copy missing characters into Font Asset Creator. Coverage presets include Steam’s fully supported languages.

  • Placeholders, tags, and translations

    Find missing or changed placeholders, unclosed or incorrectly nested rich text tags, missing and empty translations, TODO markers, and possible encoding errors. Flag translations identical to the source for review, and identify hard-coded UI text that is not connected to localization.

  • Check screens in Play mode

    Open a screen in your running game, focus the Localization Checker window, and press F8. The patrol uses your localization system to switch through the selected languages, checks the displayed UI, and captures a screenshot for each language. It also checks UI created at run time.

From overview to issue details

Localization Checker overview showing a language-by-check matrix, Canvas hotspots, font coverage by language, and missing characters by font.
Compare languages and issue types, find affected screens, and review font coverage.
Issue list sorted by severity with the German Quit button selected and “Spiel beenden” outlined in the Scene view.
Select an issue to locate its object. Supported scan issues also offer a translation preview.
Scene view heat map with numbered outlines around affected text components, colored by issue type.
Use the heat map to see where issues appear in the UI.

How it works in your project

  • Scans measure copies of your UI in a hidden preview scene and do not edit or save the originals. Scene previews temporarily replace displayed text and restore it afterward. The manual explains preview and Play mode effects.
  • Editor-only: nothing goes into your builds. No third-party DLLs, no network connections. Full C# source included.
  • Works with Unity Localization, I2 Localization, or your own CSV, Excel, JSON, XLIFF and gettext PO files. Interface and documentation in English and Chinese.
  • Export the issue list as CSV or as an offline HTML report. Run checks from the command line in your continuous integration pipeline.