CheckOps
pseudo-localization
pseudo-localization is an MIT JavaScript library that transforms UI strings into pseudo-languages, accented or bidirectional, to catch localisation issues before translations exist.
Latest public signals
Not refreshed yet. Refresh reads the public site and, when the entry has a GitHub repository, the latest release.
Introduction
pseudo-localization helps developers test UI elements for localisation issues before real translations are available. It transforms text into a pseudo-language that simulates text overflow from longer translations, font rendering of larger glyphs, and right-to-left layouts.
pseudoLocalizeString converts strings, and PseudoLocalizeDom pseudo-localises the DOM and watches for changes in real time. Strategies include accented and bidi. A live demo applies it to Hamlet.
In the quality loop it finds hard-coded strings and layout breaks early.
The source code is at tryggvigy/pseudo-localization on GitHub under the MIT licence, with about 141 stars; the most recent commit was on 24 September 2026.
Features
- Accented strategy: Longer, accented text.
- Bidi strategy: Right-to-left simulation.
- DOM mode: Live page transformation.
- String API: pseudoLocalizeString.
- Mutation observer: Real-time updates.
- Framework-agnostic: Any web UI.
Pros
- Zero translation cost: Tests before translators.
- Free to use: Open source under the MIT licence, so the core tool costs nothing to use.
- Actively maintained: The repository had commits as recent as 24 September 2026.
Cons
- Small project: Few maintainers.
- Web only: JavaScript environments.
- Not real translation: Cannot catch grammar issues.
Usage and Links (Example)
import { pseudoLocalizeString } from 'pseudo-localization';
import { PseudoLocalizeDom } from 'pseudo-localization/dom';
pseudoLocalizeString('Save changes', { strategy: 'accented' });
const stop = new PseudoLocalizeDom().start();
Resources:
Pricing
pseudo-localization is free and open source under the MIT licence.
Recommended for?
- Front-end teams preparing products for many languages.
Conclusion
pseudo-localization is a quick way to find i18n bugs early.
Run it in a dev build or visual tests.
On CheckOps, pseudo-localization is filed under the End-to-end & functional and Prototype & UX testing stages. Related tools listed here include i18n-tasks, Percy, Chromatic, Applitools, BackstopJS and Playwright. Which one fits best depends mostly on your stack, your team’s size and skills, and whether you prefer to run tools yourself or pay for a managed service. This page reflects the official website, documentation and repository as they stood on 11 November 2026.
Alternatives
Other tools on CheckOps that cover similar ground. Open a page, or compare one with pseudo-localization side by side.
Ii18n-tasksi18n-tasks is an MIT Ruby gem that statically finds missing and unused translation keys in Rails and Ruby i18n projects, with normalisation, health checks and spec integration.Compare with pseudo-localization
PPercyPercy is BrowserStack's visual testing service. SDKs upload screenshots from your tests; reviewers accept or reject the diff.Compare with pseudo-localization
CChromaticChromatic publishes Storybook and snapshots UI for visual review. The capture service is paid after a free monthly snapshot allowance.Compare with pseudo-localization
AApplitoolsApplitools is an AI-powered end-to-end testing platform that combines our proven Visual AI with the latest GenAI and no-code approaches to maximize your test coverage while…Compare with pseudo-localization
BBackstopJSBackstopJS is an MIT-licensed visual regression testing tool for web apps that compares screenshots over time, with Playwright or Puppeteer scripting, Docker rendering and an in-browser report; its README says it needs a new maintainer.Compare with pseudo-localization
PPlaywrightPlaywright is a framework for Web Testing and Automation.Compare with pseudo-localization