A company launches its website in French. Every sentence is translated accurately. The grammar is correct, the vocabulary is appropriate, but the page still reads as foreign. Prices are listed without local tax conventions, the date format follows a different standard, and the tone sits somewhere between stiff and unfamiliar. The content exists in French, but it does not speak to a French reader. That gap is what separates translation from localisation.
Translation and localisation are distinct processes
Translation is a linguistic operation. It moves meaning from one language to another, producing a target text that corresponds faithfully to the source. Localisation is a broader process. It adapts content so that it functions naturally within a specific cultural, legal, and technical context, as if it had been created for that market in the first place.
This distinction matters because readers do not process content in a vacuum. They respond to tone, format, cultural references, and the small signals that tell them whether something was made for them or merely converted from somewhere else. Content that reads as translated, rather than local, erodes trust before a single claim is evaluated.
What localisation actually involves
Localisation operates across layers that word-for-word translation does not reach:
- Date, time, and number formats. The same figure rendered as "1.500,00 €" in Portugal appears as "£1,500.00" in the UK. A date written as 04/07/2026 means 4 July in most of Europe and 7 April in the United States.
- Currency and pricing conventions. Converting a currency symbol is not enough. Consumer price expectations and market positioning vary significantly between countries.
- Tone and register. Some markets expect directness and informality; others expect a more formal register. The same product description may need a different voice for different audiences.
- Cultural references and imagery. A metaphor that works in one culture may have no equivalent in another. Images involving gestures, symbols, or human figures carry culturally specific readings.
- Legal and regulatory requirements. Privacy policies, terms of service, and legal disclaimers must reflect local law, not simply be translated from the source version.
- Software and interface elements. Localising a digital product involves more than text. German text is typically around 30% longer than English, which affects interface layout. Arabic and Hebrew follow right-to-left reading conventions. Form fields, date pickers, and input validation all require adjustment.
These adaptations, taken together, are what make a localised version genuinely functional rather than merely translated.
When localisation is needed and when translation is sufficient
Not every document requires full localisation. The decision depends on who the content is for and what it needs to do.
Internal documents, operational reports, and interdepartmental communications benefit from accurate translation, but they do not require deep cultural adaptation. The reader shares enough organisational context to interpret references that are not locally calibrated.
User-facing content is a different matter. Websites, mobile applications, marketing materials, software interfaces, and product documentation need to work as if they were native to the target market. Any signal that the content was produced elsewhere and then converted reduces user confidence and, in commercial contexts, conversion rates.
For digital products and platforms, the level of localisation required goes further still. Software localisation involves string management, character encoding, locale settings, and testing across environments. For organisations working on technology products entering new markets, M21Global offers a dedicated technology and software localisation service that addresses these layers as an integrated process.
Localisation works best when it starts early
Organisations that get consistent results from localisation tend not to treat it as a final step after content is finished. They build for it from the start, through a process called internationalisation.
Internationalisation prepares content and systems to support multiple languages and markets. It means avoiding idioms that resist adaptation, structuring software code to accommodate variable text lengths and data formats, and building terminology glossaries that ensure consistency across languages.
When this groundwork exists, localisation is faster, more consistent, and less likely to produce errors. When it does not, each new language starts without a foundation, which increases both cost and risk.
How M21Global approaches content localisation
With more than 20 years of experience and over 300 million words translated and localised, M21Global works on projects ranging from corporate websites and marketing campaigns to software interfaces and mobile applications across European and Lusophone markets. The process involves sector-specialist linguists, translation memory tools for terminological consistency, and review focused on the cultural context of the target market. To discuss what type of service fits a specific project, contact the team with details of the content and target markets.
Related Services
Request a free software localisation quote
- Request a free software localisation quote
- Mobile App Localisation Angola Mozambique
- Iso 17100 Localization For Saas Platforms
- A Surprising Amount Of Content Available Online Is Generated By Artificial Intelligence
Frequently Asked Questions
What is the difference between translation and localisation?
Translation converts text from one language to another while preserving linguistic meaning. Localisation adapts content to fit the cultural, legal, and technical context of the target market, covering tone, formats, cultural references, and regulatory requirements.
What is internationalisation and how does it relate to localisation?
Internationalisation is the process of preparing content and systems to support multiple languages and markets from the outset. When done well, it makes subsequent localisation faster, more consistent, and less prone to errors.
Which types of content require full localisation?
User-facing content such as websites, mobile applications, software interfaces, marketing materials, and product documentation typically requires full localisation. Internal and operational documents generally need accurate translation but not deep cultural adaptation.
Does localisation only apply to text?
No. Localisation can include adapting images, icons, date and number formats, currency conventions, legal disclaimers, tone of voice, and technical aspects of software interfaces such as text expansion and reading direction.
How long does a localisation project take?
Timescales depend on content volume, number of target languages, and technical complexity. Simple web content can be completed in a few days; software platforms with multiple languages typically involve several weeks of structured work.
