Localization

Great products don't stay in one language for long. Somewhere out there is a user reading your words in their second language, in another alphabet, in a culture you've never visited — and they deserve to feel just as at home as your very first users did.

Learn on the move: press play and turn your commute, walk or drive into time that grows your design career.

Listen to the full Localization course on DesignPath
Share
Share

Copy that travels well is a quiet act of respect: it tells people, in their own words, that this was built for them too.

When It Matters Most

  • Multi-region or global products — anywhere you serve more than one market.
  • High-context cultures and right-to-left languages — where tone, formality, and even direction differ sharply.
  • Regulated or high-trust domains — finance, health, legal — where the wrong term breaks confidence.

If you might ever localize, writing for it from the first word is a gift to your future self — and to users you haven't met yet.

What This Module Covers

Two sides of writing for the world: adapting copy to each market's culture and expectations, and crafting source copy that's ready to travel. The next articles show you how.

Localizing Microcopy

A literal translation is not a localization. The moment your copy leans on a metaphor or idiom — "It's raining cats and dogs!" — it breaks the instant it leaves its home language.

Adapt the Culture, Not Just the Words

Airbnb found that conversion improved when they culturally adapted their UX writing rather than translating it word for word — the gains were clearest in East Asian and Latin American markets, where tone and phrasing expectations differ most. The job is to preserve the meaning and feeling, not the literal sentence. AI can produce a first-pass translation in seconds, but it doesn't feel cultural nuance — use it as a draft for a native speaker to adapt, never as final copy.

Match Regional Expectations

Use the terms people in each region actually use. Shopify writes "post code" for UK users instead of "zip code" — same field, but it matches what the user expects to see and removes a tiny moment of friction. Small mismatches in everyday terminology quietly signal that the product wasn't built for them.

Found this useful? Pass it on.
Share