--- title: "Localisation" description: "Adapting content and experience for another language, region or culture." category: "Operations" canonical: "https://contentlexicon.com/localisation" updated: "2026-10-14" --- # Localisation _Operations_ > Adapting content and experience for another language, region or culture. Localisation is the work that makes a product or page feel as if it was made for the place it's used, whatever language or culture it started in. A faithful translation can still be a poor local experience: the words may be correct while the payment method is unavailable, the joke meaningless or the instruction legally wrong. Localisation asks whether the whole thing works here. Three related terms are easy to mix up. Translation changes the language. Localisation adapts everything else as well. Internationalisation comes first: designing content, templates and systems so they can be localised without being rebuilt, for example by allowing for longer words, right-to-left scripts and different date formats. What gets localised goes well beyond the text: date, time, number and address formats; currencies and prices; units of measurement; images, colours and icons that carry different meanings; examples, names and cultural references; legal requirements such as consumer rights, privacy notices and age limits; and [voice](https://contentlexicon.com/voice) and [tone](https://contentlexicon.com/tone), since formality and directness land differently from one culture to another. In Wales, public bodies work under the Welsh Language Standards, which require them not to treat Welsh less favourably than English. That makes bilingual publishing a test of maintenance as much as translation. The Welsh version needs to be as current, complete and easy to find as the English one, rather than a translation that lags weeks behind, so teams that publish both at once tend to build translation into the content [workflow](https://contentlexicon.com/workflow) from the start. ## Why it matters for content Localisation affects inclusion, trust and task completion. People shouldn't receive a second-rate version because they use another language or live in another region. Planning for localisation early lets [content models](https://contentlexicon.com/content-model), layouts and workflows accommodate variation rather than treating it as a late export job. Maintenance is critical. Source content changes, but translated versions are often updated later or not at all. Teams need relationships between variants, visible status and clear responsibility for review. A changed delivery restriction, for example, needs to reach the source page and every affected language version. The working tools make consistency possible at scale. A [glossary](https://contentlexicon.com/glossary) or terminology [database](https://contentlexicon.com/database) records approved translations of key terms. Translation memory stores previously translated sentences so they can be reused, which keeps wording consistent and cuts the cost of updates. A localisation [style guide](https://contentlexicon.com/style-guide) covers tone, formality and formatting for each language. Translators and local reviewers also need the purpose, audience and product behaviour, not isolated strings. ## How AI changes the picture AI can speed up translation, terminology checks and first-pass adaptation. It can make support for more languages affordable, particularly when paired with approved glossaries and translation memory. Fluency doesn't guarantee accuracy or cultural fit. Models may alter names, legal meaning or tone, and performance varies between languages, often falling for languages with less training data, Welsh among them. High-risk content needs qualified human review and testing with people who use the local version. Structured source content helps machines and people track variants. Clear fields, locale [metadata](https://contentlexicon.com/metadata) and shared terminology reduce drift, while change notifications can alert reviewers to affected variants. Someone still needs to act on them. ## Questions people ask **Does every language version need the same content?** Not always. The core facts and rights should match, but examples, emphasis and even page structure can differ where local needs differ. No version should be missing something its readers need. **Should we write the source content differently?** Yes. Clear, consistent source content with fewer idioms and explicit context is easier to localise without losing meaning. **Can AI replace translators?** It can support routine work, but human expertise is still essential for nuance, consequence and quality, particularly in legal, medical or public-service content. **When should localisation begin?** During research and design, before layouts, fields and workflows make language variation expensive. ## Learn more - [Localization vs. Internationalization](https://www.w3.org/International/questions/qa-i18n) – W3C's explanation of how the two differ, with a list of what localisation can involve beyond translation, from date formats and currency to legal requirements. - [Don’t alienate your user](https://prototypr.io/post/dont-alienate-your-user-a-primer-for-internationalisation-localisation) – a visual, practical primer on designing beyond one language and cultural context. - [Bilingual technology toolkit: good user experience](https://www.welshlanguagecommissioner.wales/media/vokjtkka/20220622-dg-s-pecyn-cymorth-prosiectau-tgch.pdf) – the Welsh Language Commissioner's case study of the Welsh Government's checklist for bilingual digital services, written for people commissioning technology rather than building it. Related terms: [Content inventory](https://contentlexicon.com/content-inventory), [Content maintenance](https://contentlexicon.com/content-maintenance) This page was last reviewed in October 2026.