LocCheck is a localization QA and table management tool for Unreal Engine. It helps you review, search, validate, and clean up localized text directly inside the editor before localization problems reach your players.
Unreal Engine already has powerful localization tools, but once a project grows, it can become hard to see the full picture. A few languages can quickly turn into hundreds or thousands of strings spread across tables, UI widgets, archives, and assets. LocCheck gives you one clear place to check the health of your localization and find issues faster.
With LocCheck, you can scan your project for missing translations, empty entries, broken placeholders, rich text tag problems, repeated text, long translations, unsupported font characters, risky key names, unused entries, and hardcoded Widget Blueprint text.
The goal is simple: make localization review easier, cleaner, and less painful.
Run a scan, check your localization health score, browse your tables, filter problems, inspect individual entries, review hardcoded text, find where strings are used, add review notes, and export reports for QA, production, or team handoff.
LocCheck does not replace Unreal Engine localization. It works alongside it as a practical QA layer for developers who want to catch localization problems earlier and keep their text data organized.
3. Why LocCheck Is Useful
Localization problems are easy to miss because they often hide in places you do not check every day.
A project can look ready, but still contain:
Missing translations
Empty translated entries
Broken format placeholders
Broken rich text tags
Text that is too long for the UI
Font glyph issues for certain languages
Duplicate keys
Repeated source text
Old unused entries
Hardcoded UI text inside Widget Blueprints
LocCheck brings these problems into one focused editor window so you can review them without manually digging through every table, widget, and localization file.
It is especially useful before release builds, Steam demos, marketplace submissions, client handoffs, internal QA passes, and major localization updates.
4. Key Features
Localization Health Score
Get a project-wide score from 0 to 100 based on detected localization issues and severity. This gives you a quick overview of whether your localization looks clean, risky, or needs attention.
Large Table Browser
Browse localization entries in a dedicated table view with search, filters, sorting, status filtering, issue visibility, and a detailed inspector panel. It is designed to make large localization tables easier to review.
Missing and Empty Translation Detection
Find entries where a target culture is missing a translation or contains an empty value.
Placeholder Validation
Detect translations where format placeholders do not match the source text. This helps catch issues that can break formatted text at runtime.
Rich Text Tag Validation
Find broken, missing, or mismatched rich text tags so localized UI text does not display incorrectly.
Duplicate Key and Repeated Text Detection
Spot duplicate keys and repeated source text that may indicate messy localization data, accidental duplication, or entries that should be cleaned up.
Long Translation Detection
Flag translated text that may become too long for UI layouts. This is useful for languages that naturally expand compared to English.
Font Glyph Coverage Scanner
Check whether translated characters are covered by available font face assets. LocCheck includes native glyph coverage logic and does not require external font tools.
Key Naming Checks
Find risky localization key names, such as keys with spaces, overly generic names, or keys that do not follow your configured prefix rules.
Unused Entry Detection
Find string table entries that appear to have no asset references, helping you clean up old localization data left behind after UI or content changes.
Hardcoded Text Scanner
Scan Widget Blueprints for hardcoded text in common UI text widgets, including TextBlock, RichTextBlock, EditableText, and EditableTextBox.
Usage Finder
See which assets reference localization entries and quickly open related assets from the editor.
Review Workflow
Mark entries as Unreviewed, Needs Review, Approved, Ignored, or Locked. Add developer notes, context notes, per-entry character limits, and issue ignores. Review data is saved between editor sessions.
Exportable Reports
Export useful reports for QA, production reviews, sprint planning, or team handoff.
Supported exports include:
Markdown localization QA report
HTML localization QA report
CSV issue export
Markdown table split plan
CSV review status export
Configurable Settings
Adjust target cultures, source culture, include and exclude paths, scanner toggles, long text thresholds, naming rules, score penalty multiplier, unused entry ignore namespaces, and report output paths.
Double-click an issue to reveal the related String Table, Blueprint, Widget Blueprint, or asset in the Content Browser.
Important Technical Notes
LocCheck is an editor-only plugin. It is designed to help developers review localization data inside Unreal Engine and does not add gameplay systems to packaged builds.
LocCheck does not automatically rewrite your String Tables, localization archives, or source localization files. It scans, reports, reviews, and exports information so you can decide what to fix.
Unused entry detection can produce false positives if your project builds localization keys dynamically at runtime. For this reason, LocCheck includes ignore options to help reduce noise for known dynamic systems.
Font glyph coverage checks require suitable font face assets. If no suitable font assets are available, glyph scanning can be skipped or disabled.
AI Use Notice
AI tools were used only as a support tool for basic tasks such as documentation drafting, wording improvements, and development assistance. LocCheck was designed, reviewed, tested, and finalized by ECal Studios.
Documentation: https://www.ecalstudios.com/loccheck/