A company launching a product in a new market needs something different from one that is simply sharing an internal report with an overseas partner. One case requires localisation. The other needs translation. The distinction seems obvious, but in practice many organisations conflate the two, and that has real consequences.
What separates translation from localisation
Translation converts text from one language to another while preserving content and meaning. That is what is done with a contract, a technical manual, or a financial filing. The goal is accurate comprehension in another language.
Localisation goes further. It adapts content to the cultural, legal, and functional context of the target market. That includes language, but also date and time formats, units of measurement, cultural references, communication register, images, currency, and sometimes the navigational structure of an interface. A properly localised product feels as though it was built for that market, not just translated into it.
The practical difference: a linguistically correct translation can still be culturally inappropriate, technically dysfunctional, or legally insufficient in the target market.
When translation is enough
There are content types where localisation would be a waste of resources. Translation is the right choice when:
- The content is for internal use: reports, minutes, operating procedures, interdepartmental communications.
- The reader is a professional using the document as a technical reference, not as a product experience.
- The document has a short lifespan or single use, such as a preliminary proposal or meeting summary.
- The content contains no cultural references, interface elements, or calls to action directed at an end user.
In these cases, a rigorous translation with a controlled glossary and appropriate sector-specific review is sufficient.
When localisation is required
There are situations where releasing content without localisation is a mistake with measurable consequences, whether in revenue, reputation, or regulatory compliance.
Digital interfaces and software. An application or SaaS platform that simply swaps words into another language fails the moment a user encounters an incomprehensible date format, a button that does not fit its container, or an error message that makes no sense in the local context. Technology and software localisation requires an approach that goes well beyond text.
Marketing and external communications. A campaign designed for one market can be ineffective, off-putting, or simply odd in another. Tone, references, and the values being communicated all need adaptation.
Regulated products. In sectors such as healthcare, food, or medical devices, local authorities may require adaptations that go beyond language: sector-specific regulatory terminology, mandatory legal formats, or the inclusion of information absent from the source document.
E-commerce and purchase flows. A user who encounters the wrong currency, unfamiliar payment methods, or a checkout process that does not match local habits will abandon the process. Localisation is a conversion factor, not just a language exercise.
The practical decision criteria
Before defining what a project requires, it is worth answering four questions:
- Who will consume this content? An internal professional or an end user in the target market?
- Does the content contain functional or interface elements? Buttons, menus, system messages, forms, purchase flows?
- Does the target market have relevant cultural or regulatory specificities? Lusophone Africa, Arabic-speaking markets, Asian markets, and even neighbouring European markets can differ significantly beyond language.
- Does the content represent the brand externally? If so, the level of adaptation required is higher.
If the answer to any of these questions is yes, localisation is probably necessary. If all answers are no, quality translation is sufficient.
How M21Global approaches this decision
M21Global works with companies expanding into new markets who need to understand, before committing resources, what their content actually requires. The team brings over 20 years of experience in distinguishing what can be resolved with rigorous translation and what demands a full localisation process, including cultural adaptation, software engineering, and in-country review. Making that distinction early saves time, budget, and avoidable errors down the line.
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 content from one language to another while preserving meaning. Localisation adapts content to the cultural, legal, and functional context of the target market, including formats, cultural references, register, and technical interface elements.
When is localisation required rather than translation?
Localisation is required when content is directed at end users, involves digital interfaces, represents the brand externally, or must meet specific regulatory requirements in the target market.
Is localisation always more expensive than translation?
It depends on the project. Localisation typically involves more stages, including cultural adaptation, engineering work, and in-country review, which makes the process more complex. For internal documents or technical content with no interface elements, rigorous translation is sufficient and more efficient.
Can localisation be applied to only part of a product?
Yes. It is common to localise the user-facing interface and communications while keeping internal technical documentation at the translation level. The decision should be driven by who consumes each type of content.
Does localisation always include translation?
Yes. Translation is the foundational component of localisation, but localisation adds cultural, technical, and functional adaptation on top. It is possible to translate without localising, but not to localise without translating.
