All 141 tools / International and inclusive design
Check source strings for translation problems and project how long each will be in other languages
Localisation readinessFreeFor writers, developers and product teams
25/day
free runs a day, no sign-in.
Before: what you give it
The example input, as typed in. You paste text, CSS, markup or notes.
strings:
save = Save
cart.items = You have {count} item(s) in your cart [max 30]
date = Delivery on March 3rd
welcome = Welcome back, {name}! Last seen {0} {1}
frag = to the left of
languages: de, fr, ja
expansion: de=1.35, fr=1.25, ja=0.55
After: what comes back
The first lines of a real run on that input. Nothing here is edited by hand.
5 strings. Expansion source: your table. Languages: de, fr, ja.
Projected length = current length x language factor. Strings of 10 characters or fewer get 1.6x the growth, up to 20 get 1.3x, up to 40 get 1.15x, because short UI words expand most.
4 strings with findings; 1 clean.
cart.items: "You have {count} item(s) in your cart" (30 chars, worst case 43 in de)
- "(s)" plural: many languages have more than two plural forms; use a plural rule (ICU or gettext)
- a number followed by a counted noun with no plural rule: 1 vs many (and few, many, other in some languages) will break
- over the 30 character limit in: de, fr (worst de: 43)
date: "Delivery on March 3rd" (21 chars, worst case 30 in de)
- hard-coded month or weekday name; format dates with the locale
- English ordinal suffix (1st, 2nd); ordinals differ by language
welcome: "Welcome back, {name}! Last seen {0} {1}" (27 chars, worst case 38 in de)
... full output on the tool page
What you get
Projected lengths per language, overflow against limits, and findings on fragments, plurals and placeholders
What it cannot do
Uses your growth factors or our rough planning table, named in the output; projections are not measured translations.
Who it is for
- Writers
- Developers
- Product teams
Free and Pro
| Free | 25 runs a day per IP address, up to 50,000 characters a run. |
|---|---|
| Pro | No daily limit, 300 requests a minute, up to 200,000 characters a run. |
Use it from your assistant
The tool is called localisation_readiness. Connect the server once, then ask for it by name or just describe the job. Install steps for each app.
claude mcp add --transport http designers https://designers.allthepossibles.com/mcp
curl -X POST https://designers.allthepossibles.com/api/localisation-readiness -H 'content-type: application/json' -d '{"strings":"save = Save\ncart.items = You have {count} item(s) in your cart [max 30]\ndate = Delivery on March 3rd\nwelcome = Welcome back, {name}! Last seen {0} {1}\nfrag = to the left of","languages":"de, fr, ja","expansion":"de=1.35, fr=1.25, ja=0.55"}'
Try it here
The form starts with the same example input, so you can run it first and then swap in your own.
More in international and inclusive design
- Localisation stress test
Predict how far UI strings grow in eight languages and flag the ones that overflow their space.
- RTL readiness
Find the left and right CSS that will break in Arabic or Hebrew, with the logical property to use instead
- Font coverage check
Find which scripts your text needs and which listed fonts cover them, with a Noto family for each gap
- Date and number format review
Find dates, numbers, currency and units in UI text that read differently in other locales
- Text expansion planner
Plan how much longer each UI string gets in other languages and flag the ones that overflow
- Name field check
Find name inputs that reject real names: short maxlength, A to Z patterns and forced first and last fields