# Localization \(l10n\)

Localization adapts a product’s language, content, and regional conventions for a specific audience or locale.

- Type: practice
- Domain: Experience & interface
- Level: Intermediate
- Last reviewed: 2026-10-19
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/localization/>)

## What it means

Localization, commonly abbreviated l10n, adapts an interface and its supporting material to a target locale. Translation is one part; formats, examples, imagery, terminology, and task expectations may also change. Internationalization makes such adaptation technically possible, while localization makes the particular experience appropriate and understandable.

## Why it matters

Literal translation can leave users confused by unfamiliar conventions or unsuitable examples. Localized tasks help people understand prices, enter information correctly, and obtain consistent help across the product.

## When to use it

Use it when serving a defined audience with different language or regional needs. Prioritize complete important journeys rather than isolated screens. Validate audience requirements instead of assuming that a locale label captures every user’s preferences.

## How it works

1. Define target audiences, locales, and the journeys in scope.
2. Provide translators with context, terminology, screenshots, and message intent.
3. Adapt text and regional presentation with qualified linguistic and domain review.
4. Test complete tasks for comprehension, layout, direction, and formatting.
5. Maintain translations with source changes and define transparent fallback behavior.

## A practical example

A travel service localizes search, booking, confirmations, and support guidance for Persian-speaking users. Review catches a cancellation phrase that was linguistically correct but unclear about the deadline. The team revises the wording and tests the full booking journey.

## Where it breaks

Accurate language cannot fix unavailable services or a poor market proposition. Translation quality and maintenance require ongoing resources. Regional defaults may not match individual preferences, so users may need explicit language and formatting controls.

## Common mistakes

- Translating interface labels while leaving errors and emails unchanged.
- Giving translators isolated strings without context.
- Inferring every preference from IP location and preventing correction.

## Sources

1. [Localization](<https://developer.mozilla.org/en-US/docs/Glossary/Localization>) — MDN Web Docs · Official documentation
2. [Language Tags and Locale Identifiers for the World Wide Web](<https://www.w3.org/TR/ltli/>) — W3C · Working draft

## Related topics

- [Content Design](<https://wiki.soroush.uk/topic/content-design/>)
- [UX Writing](<https://wiki.soroush.uk/topic/ux-writing/>)
- [Internationalization \(i18n\)](<https://wiki.soroush.uk/topic/internationalization/>)
