Pseudolocalization generator for i18n JSON
Turn your source locale into accented, expanded, or right-to-left test copy. Catch localization bugs before paying for a single translation.
Source locale
Paste JSON or choose your reference locale
Generated pseudolocale
Ready to save as qps-ploc.json
Transformation options
Options update the preview immediately when the source JSON is valid.
Find internationalization problems while they are still cheap
A pseudolocale exercises the same loading and rendering path as a real locale. The strange-looking text is deliberate: every visual difference points toward an interface assumption worth testing.
Expose hardcoded copy
Accented output makes source-language strings that bypass localization immediately visible during testing.
Stress-test layouts
Add 20–50% padding to reveal fixed-width buttons, clipped navigation, and cards that cannot grow.
Find concatenation
Boundary markers show where interfaces assemble sentences from fragments or accidentally trim copy.
Keep runtime syntax intact
Placeholders, ICU controls, markup, links, and JSON structure are protected while visible text changes.
Use the output like a real locale
- 1
Generate qps-ploc.json
Start with accents, brackets, and 30% expansion. Download the resulting JSON file.
- 2
Load it in development
Register qps-ploc as another application locale and exercise important product flows.
- 3
Fix what becomes visible
Look for English copy, clipped controls, reordered placeholders, concatenation, and components that resist RTL layout.
Already have translated files?
Compare source and target locale files for missing keys, empty values, and placeholder mismatches.
Open the JSON translation checkerReady to add real languages?
Import JSON, create AI-assisted drafts, review changes, and publish approved translations through a global CDN.
Start your 14-day trialPseudolocalization questions
What is pseudolocalization?
Pseudolocalization replaces readable source copy with visibly altered text before real translation begins. It helps teams find hardcoded strings, clipped layouts, concatenation, and directionality problems early.
Will the generator change my translation keys?
No. Object keys and JSON structure are preserved. Only string values are transformed; numbers, booleans, null values, arrays, and nested objects retain their structure.
Are placeholders and HTML preserved?
Yes. The generator protects common Mustache, ICU, printf, template, and colon placeholders, along with HTML tags, entities, URLs, and email addresses.
What do qps-ploc and qps-plocm mean?
They are conventional pseudo-locale identifiers. This tool uses qps-ploc for accented and expanded output and qps-plocm when RTL simulation is enabled.
Is my JSON uploaded anywhere?
No. Generation, preview, copy, and download all happen locally in your browser. Troevo does not receive the file contents.