Localization tools
Inspect locale formatting, validate string files, measure translated text width, and estimate project cost. The CLDR explorer and budget estimator save their settings in the URL so you can share any view as a link.
CLDR explorer
Format one date, number, or price across your target locales.
Highlights field order, separators, numeral systems, sign placement, and invisible characters that break parsers. Exports to Markdown and CSV.
For engineering specs and bug reports
String audit
Lint source strings before handoff and verify translated files before import.
Detects string concatenation, broken ICU syntax, missing keys, dropped placeholders, and missing CLDR plural forms.
For vendor handoffs and catalog imports
Text expansion
Measure how much a UI string expands or contracts in translation.
Translates one string into 55 languages and measures character count, rendered pixel width, and ink height.
For UI layout specs and design reviews
Budget estimator
Calculate per-locale cost and schedule for a translation round.
Applies language-pair rate multipliers, translation memory discounts, and one-time engineering setup hours. Exports to CSV.
For release scoping and finance
Background reading
- Formatters - how CLDR and ECMA-402 format dates, numbers, and currencies
- Pseudolocalization - automated pre-translation checks for hardcoded strings and clipping
- Translation pipeline - string externalization, file formats, and translation memory leverage