Two companies expanding into a new market can take very different approaches to the same challenge. One translates its website. The other localises it. The results are not the same, and neither is the investment required. Understanding what separates these two services is the first step to choosing the right one.
What translation is and what localisation is
Translation is the transfer of content from one language to another while preserving the original meaning. A technical manual translated from Portuguese into English remains the same document, covering the same procedures, expressed in a different language.
Localisation is a broader process. It adapts content to the cultural, legal, and functional context of a target market. Language is part of it, but so are date and time formats, currency, units of measurement, cultural references, communication tone, images, and, in digital products, interface structure and layout. A product localised for the German market does not simply speak German: it follows German conventions for formal address, displays prices with a comma as the decimal separator, and meets the legal requirements for consumer information that apply in Germany.
When translation is the right approach
Translation alone is appropriate when the goal is to transfer information accurately, without the end user's experience being a primary concern. Common cases include internal documents, technical reports, meeting minutes, business correspondence, and compliance records.
In these situations, what matters is content precision. The reader already understands the product, the sector, or the process. There is no need to adjust tone, reformat visual elements, or review cultural references. A rigorous translation carried out by a qualified linguist is sufficient.
The same applies to documents with legal standing: contracts, powers of attorney, certificates. Here, fidelity to the source is the priority, not cultural adaptation.
When localisation is necessary
Localisation is necessary when content will interact directly with an end user in a consumption or product-use context. The most evident cases are institutional and e-commerce websites, mobile applications, enterprise software, marketing materials, and digital platforms with a user interface.
A practical example: a financial management application launched in Angola cannot simply translate the text from the Portuguese version. It needs to reflect the local currency (kwanza), the date formats used in the country, the appropriate communication tone for that market, and potentially the regulatory requirements of the Angolan financial sector. Without that adaptation, the product exists in another language but does not belong to the market.
The same reasoning applies to marketing campaigns for Brazil, software interfaces for the French market, or e-commerce content for the UK. Technology and software localisation also involves technical considerations: text expansion (some languages take up significantly more space than English), character encoding, and integration with content management systems.
How to identify the right service for each project
The central question is: who will read or use this content, in what context, and with what expectations?
If the reader is a business partner, an internal team member, or a regulatory body that needs access to precise information, translation is sufficient. If the reader is a customer who will buy, use, or evaluate a product on the basis of that content, localisation is the right approach.
There are also mixed situations. A technical manual may require rigorous translation for the specification chapters and localisation for usage examples and culturally sensitive notes. The boundary is not always clear, and it is worth discussing it with the service provider before the project begins.
Volume and frequency are also relevant. Ongoing localisation projects, such as regular software updates, benefit from translation memories and terminology glossaries that maintain consistency over time and reduce costs in future iterations.
M21Global: translation and localisation with direct market experience
M21Global has been working in translation and localisation since 2005, with over 300 million words processed across projects ranging from technical documentation to digital platforms serving markets in Africa, Europe, and Brazil. The team has direct experience in Lusophone and European markets, which means cultural adaptation is not treated as an add-on: it is part of the process from the start. To identify which service fits a specific project, contact M21Global and describe the context in which the content will be used.
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 goes further: it adapts content to the cultural, legal, and functional context of the target market, including formats, conventions, and communication tone.
When is translation alone sufficient?
Translation is sufficient for internal documents, reports, contracts, and technical correspondence where the goal is accurate information transfer, without the need to adapt the experience for an end user.
What types of content require localisation?
Websites, mobile applications, software with a user interface, marketing materials, and e-commerce platforms generally require localisation because end users interact directly with the content and bring specific cultural expectations.
Does localisation always include translation?
Yes. Localisation includes translation as a base component, but adds cultural adaptation, reformatting of elements such as dates and currencies, and technical adjustments for digital products.
How do I know which service is right for my project?
The key question is who will use the content and in what context. For end users in external markets, localisation is generally required. For internal communication or technical documentation, translation is sufficient. When in doubt, it is worth discussing the context with a specialist provider.
