Deterministic localization QA
Catch localization file issues before release.
Compare source and target files, protect placeholders and structure, and export audit-ready reports using repeatable, rule-based checks.
JSON•YAML•XLIFF•Android•Apple•Java
LocaleQA
5 checks selected
No glossary
Run your first check to save reports and create share links.
File check
Run a localization file check
Upload a reference file and its target-language counterpart, then run the selected checks. Both files must use the same format and each file must be 5 MB or smaller.
Supported: JSON, YAML, XLIFF 1.2/2.x, Android XML, Apple .strings/.xcstrings, and Java .properties.
Step 1
Reference file
No reference file selected
Step 2
Target file
No target file selected
Rules
5 checks will run
Glossary
None uploaded
Outputs
HTML, PDF, JSON, ZIP
Status
Waiting for files
Files are processed server-side. Stored reports may include filenames, paths, glossary terms, and short source or target excerpts. Review data handling before uploading confidential material.
Run your first check to save reports and create share links.
Need help or found a problem? Send feedback with the format, expected result, and scan ID. Do not email confidential file contents.
No reports yet
Catch preventable localization file issues before release, handoff, or delivery.
Catch file drift before it reaches release
Find missing entries, extra content, same-as-source strings, and structure drift across web, mobile, and Java localization files.
Protect placeholders, tags, and structured text
Check placeholders, tags, and multiplicity mismatches on intersecting string paths before they reach QA or engineering.
Keep formatting and glossary rules intact
Preserve whitespace, line endings, internal runs, and exact-match glossary requirements for repeatable review.
Learn more
LocaleQA checks JSON, YAML, XLIFF, Android XML, Apple strings catalogs, and Java properties as-is. It is a deterministic localization QA checkpoint for translation file validation, localization file validation, placeholder validation, untranslated strings, and missing translation keys. It is not a translation system or linguistic review layer.
Rule set
Deterministic checks
✓ All checks enabled
Check set
Choose the scan rule profile for this run.
The General checks set runs the 10 core checks for all supported formats.
All checks enabled
General checks are selected. Open Advanced options only if you need to adjust individual checks.
Glossary
Glossary terms
Glossary (CSV)
Accepted format: CSV file with 2 or 3 columns.
source,target,caseSensitive Password,パスワード,false Pricing,料金,false scan,スキャン,false
- source: word or phrase in original text
- target: required translation
- caseSensitive: optional, true or false
If omitted, case-sensitive matching is used.
Partial matches are supported. For example, "Password reset" will match "Password".
CSV is a simple text format where values are separated by commas.
Enter terms directly
You can also add terms below with source => target.
Entries: 0