Back to Glossary
Localisation
Synonyms: localization, L10n, UX localisation, product localisation, cultural adaptation
Do not index
Definition
Localisation is adapting a product so it feels made for one specific market. That covers the words, plus dates, currencies, units, name formats, images, colours, payment methods and sometimes whole flows. Translation is one part of the job.
It exists because 03/04 means 3 April in London and March 4 in New York, so someone turns up a month early. It depends on internationalisation (i18n), the engineering prep that lets text grow and layouts mirror without a rebuild, and on clear UX writing, since idioms such as "hit the ground running" fall apart in translation.
Use cases
Skip localisation and international users get a product that feels second-hand.
Examples:
- Exploding buttons: "Save" becomes "Speichern" in German, and strings can grow 30% or double. Fixed-width buttons cut off to "Speich..." the week before launch.
- Forms that reject real people: "First name / Last name" breaks for Vietnamese users such as Nguyễn Văn An, whose family name comes first.
- Backwards Arabic screens: Without mirroring, the back arrow points forward and progress bars fill from the wrong side.
How it's used in practice
- Design with the longest language: Test with German copy and let containers grow 30%+.
- Pseudo-localise first: Swap copy for padded, accented fake text (e.g. [!!! Šåvé !!!]) to catch hard-coded strings and truncation.
- Use leading and trailing edges: Start/end spacing lets iOS, Android and the web mirror RTL layouts for you.
- Pull formats from locale data: Get dates, currency and plurals from platform APIs or Unicode CLDR. Never hard-code "$" or "MM/DD".
- Give translators context: Send screenshots, character limits and tone notes with every string.
Don't mirror everything in RTL. Numbers, phone numbers, logos, clocks, play buttons and real objects (a magnifying glass, a keyboard) keep their direction.
Challenges & limitations
- Cost grows per market: Each language adds translation, QA, support docs and app store assets.
- Culture data is an average: Ho Chi Minh City and a rural province behave differently. Local research still matters.
- Machine translation fools non-speakers: MT drafts look fine to a team that can't read them. Get native review.
Free resources
- Modify Your Design for Global Audiences: Crosscultural UX Design (NN/g) — Feifei Liu explains translation vs. localisation levels with H&M's Chinese and US sites as examples
- Personal Names Around the World (W3C) — how name order, length and structure differ by culture, and what that means for form design
- International Usability Testing: Why You Need It (NN/g) — why testing in each market catches problems your home team never sees, such as hidden language switchers
- Expand Your App to New Markets (Apple Developer) — Apple's hub for choosing markets, localising apps and localising App Store pages
