
Internationalisation vs. Localisation (I18n vs L10n): What’s the Difference?
If you want your product or service to succeed in global markets, understanding the difference between internationalisation (i18n) and localisation (l10n) is essential. These two terms are closely related, but they serve distinct roles — and confusing them can cost your business time, money, and credibility in new markets.
What is Internationalisation?
What is internationalisation? Internationalisation is the process of designing and developing a product — most often software, a website, or a digital platform — so that it can be easily adapted for different languages, regions, and cultures without requiring any major changes to the core code or structure. Think of it as building a flexible foundation before you build the house itself.

The term is abbreviated as i18n because there are 18 letters between the “i” and the “n” in the word “internationalisation.” It is an engineering-led process, handled primarily by developers and architects, and it happens before any language-specific adaptation takes place.
At its core, internationalisation means separating content from code. Instead of hardcoding text strings, dates, currencies, or number formats into your application, i18n ensures those elements are stored externally and can be swapped out for any locale without rebuilding the product from scratch.
The Value of Internationalisation
Without proper internationalisation, even a well-funded localisation effort can fall apart. If your software was built for a single language or culture, adapting it for another market requires reworking the entire codebase — an expensive, time-consuming process that could have been avoided with the right groundwork.

Internationalisation gives businesses the ability to scale globally on demand. Once the technical architecture is in place, moving into a new market becomes far more straightforward.
For B2B businesses and software companies especially, i18n is not optional — it is a prerequisite for sustainable international growth. Discover how multilingual technologies can support your business expansion to understand the full scope of what’s involved.
Why Internationalise?
Businesses internationalise their products for several practical reasons:
- To enter new markets faster — a well-structured i18n framework means localisation teams can work independently, without waiting for developers to rebuild components for each new region.
- To reduce long-term costs — fixing internationalisation issues after launch is far more expensive than building them in from the start.
- To maintain consistency — a single, well-internationalised codebase is easier to manage and update than multiple siloed versions for different markets.
- To stay competitive — as the effects of globalisation on the e-commerce industry have shown, businesses that cannot scale globally risk being left behind.
- To support diverse user bases — Unicode support, right-to-left text compatibility, and flexible UI layouts are all part of i18n and are essential for inclusive, accessible products.
Internationalisation (I18n) Example

Imagine a UK-based SaaS company building a project management tool. Initially, the software displays all dates in DD/MM/YYYY format, uses pound sterling (£) for all financial values, and has all text hardcoded in English directly into the source code.
When the company wants to launch in the United States, Japan, and Brazil, they realise the date format conflicts with US expectations (MM/DD/YYYY), the currency needs to change, and the entire Japanese interface requires right-to-left-style character spacing. Because the text was hardcoded, the development team has to rewrite large sections of the application for each market.
Had the company internationalised the product from the start — using Unicode encoding, externalised text strings, and locale-aware date and currency formatting — none of this would have been necessary. That is the real-world value of i18n.
Benefits of Internationalisation
The benefits of internationalisation extend beyond technical convenience:
- Faster time-to-market for each new locale, since the product is already structured to accept different language packs and cultural formats.
- Lower localisation costs over time — structured i18n frameworks dramatically reduce the per-language cost of each localisation project.
- Better user experience — users in every market receive a product that handles their language, date formats, currency, and cultural conventions correctly, right from the start.
- Scalability — internationalised products can grow into dozens of markets without proportional increases in development effort.
- Competitive positioning — companies that invest in i18n early are better placed to respond quickly when new market opportunities arise.
For software and app products specifically, App/Software Localisation services become significantly more efficient when the underlying product has been properly internationalised first.
What Can Go Wrong in Internationalisation?
Poor internationalisation planning leads to predictable — and costly — problems:
- Text truncation and overflow — languages like German or Finnish often produce longer words than English. Without flexible UI components, translated text gets cut off or breaks the layout.
- Hard-coded strings — embedding text directly into source code makes translation extremely difficult and error-prone.
- Incorrect character encoding — failing to use Unicode (UTF-8) can result in garbled or unreadable text in non-Latin scripts such as Arabic, Japanese, or Hindi.
- Date and number format conflicts — a date displayed as 04/05/2025 means 4 May in the UK, but 5 April in the US, and something entirely different in other regions.
- Ignoring right-to-left (RTL) languages — Arabic and Hebrew are read right to left. A product not designed with RTL support will display these languages incorrectly.
- Assuming a one-size-fits-all layout — some languages require significantly more space than English, and designs that do not account for text expansion will break when translated.
These issues are best identified — and resolved — during the internationalisation stage, long before localisation begins.
What is Localisation?
What is localisation? Localisation is the process of adapting a product, piece of content, or service for a specific language, culture, or regional market. Where internationalisation prepares the technical foundation, localisation fills that foundation with culturally relevant, linguistically accurate content.

Localisation is abbreviated as l10n — there are 10 letters between the “l” and the “n” in “localisation.” It goes far beyond direct translation. It includes adapting imagery, adjusting date and currency formats, reworking slogans, updating legal disclaimers, and ensuring that the tone, style, and cultural references all resonate with the target audience.
In short, localisation makes a product feel as though it was built specifically for the user’s market — not merely translated from somewhere else.
The Value of Localisation
Studies consistently show that consumers are significantly more likely to purchase a product when information is presented in their native language. Localisation turns local success into a global phenomenon, as demonstrated by global brands like Netflix, which invested heavily in multilingual content to capture international audiences.
For B2B businesses, localisation builds trust with overseas partners and clients. A proposal, contract, or marketing material that reflects the local culture and language signals respect and professionalism in a way that a direct translation rarely achieves. Marketing localisation takes this further by adapting not just the language but the entire brand messaging strategy for each market.
Why Localise?
Localisation is a business decision, not just a linguistic one. Here is why it matters:
- Consumer trust — people are more likely to engage with, purchase from, and remain loyal to a brand that communicates in their language.
- Market relevance — cultural references, humour, imagery, and tone that work in one country can confuse or offend in another. Localisation prevents costly missteps.
- SEO and discoverability — localised content ranks better in regional search engines and improves visibility with local audiences. Website localisation tips for creating a global-friendly website offer practical guidance here.
- Regulatory compliance — legal text, disclaimers, and terms of service often need to meet local legal requirements, not just be translated from the source language.
- Competitive differentiation — in crowded markets, localised products stand out against generic, poorly translated competitors.
Here’s an Example of Localisation (L10n)

Consider a Singapore-based e-commerce retailer that has internationalised its website platform. The company now wants to launch in Indonesia, Thailand, and Japan. The localisation process for each market would look like this:
- Indonesia — content translated into Bahasa Indonesia, pricing displayed in Indonesian Rupiah (IDR), images updated to reflect local cultural preferences, and customer support content written in a warm, relationship-focused tone that aligns with Indonesian business culture.
- Thailand — Thai script implemented throughout, Buddhist cultural references respected in seasonal campaigns, and payment methods updated to include locally preferred options.
- Japan — Japanese (Kanji, Hiragana, Katakana) used throughout, a more formal, respectful tone adopted, and product descriptions rewritten to emphasise quality and detail in line with Japanese consumer expectations.
None of these changes are simple word-for-word translations. They reflect a deep understanding of each market. How to localise your brand to an Asian market provides further insight into the cultural nuances involved.
Benefits of Localisation
Investing in proper localisation delivers measurable business outcomes:
- Higher conversion rates — localised content reduces friction in the buyer journey, making it easier for customers to understand, trust, and buy.
- Greater brand loyalty — customers who feel understood in their own language and culture are more likely to return.
- Reduced customer support burden — clear, accurate localised content means fewer misunderstandings and support queries.
- Improved app and software performance — tips to localise your mobile app for international audiences highlight how localised apps outperform generic ones in user retention and ratings.
- Stronger competitive positioning in markets where competitors have not fully localised their products.
What Can Go Wrong in Localisation?
Even with the best intentions, localisation can go wrong if not handled professionally:
- Direct, word-for-word translation — machine translation without expert post-editing often produces text that is grammatically correct but culturally tone-deaf or unnatural.
- Ignoring cultural context — a colour, image, or phrase that is neutral or positive in one culture may be offensive or unlucky in another.
- Inconsistent terminology — without a proper glossary and translation memory, the same term may be translated differently across a product, creating confusion for users.
- Overlooking local regulations — failure to adapt legal and compliance content to local law can create serious legal and reputational risks. Things to note for government translation is a useful resource for understanding compliance requirements.
- Neglecting multimedia — localising text but leaving images, videos, and icons untouched creates a disjointed experience that undermines trust.
- Poor font and layout management — some languages require different fonts or significantly more space, and localisation that does not account for this breaks the visual design.
The best way to avoid these pitfalls is to work with professional linguists who are native speakers of the target language and have real knowledge of the target culture.
Localisation (L10n) Process: Adapting Software for Specific Markets
The localisation process for software typically follows these stages:

- Preparation and planning — identifying the target markets, languages, and localisation requirements (date formats, currencies, character sets, RTL support, etc.).
- Content extraction — using the i18n framework to extract all translatable text strings, labels, and UI elements into resource files.
- Translation and adaptation — professional translators — ideally native speakers — translate and culturally adapt all content. This stage often involves content and document translation services for supporting materials.
- Linguistic review — a second linguist reviews the translated content for accuracy, consistency, and cultural appropriateness.
- Technical integration — the translated strings are reintegrated into the product, and the UI is tested for text overflow, layout breaks, and encoding issues.
- Localisation testing (LQA) — quality assurance testing is performed in each target language to ensure the product functions correctly and reads naturally.
- Launch and iteration — the localised product is launched in the target market, and feedback is used to refine future localisation rounds.
Automating parts of this workflow — for example, using translation memory and machine translation with post-editing — can significantly speed up the process. How to automate the localisation of multilingual WordPress sites is an excellent example of how automation tools can be applied practically.
Internationalisation (I18n) Process
The internationalisation process is typically an engineering workflow that runs before localisation begins:

- Unicode and encoding setup — ensuring the entire codebase uses UTF-8 encoding to support all world scripts and character sets.
- Externalising text strings — removing all hardcoded text from source code and placing it in external, locale-specific resource files.
- Locale-aware formatting — implementing libraries and frameworks that automatically format dates, times, numbers, and currencies based on the user’s locale.
- Flexible UI design — designing layouts that expand and contract gracefully to accommodate text in different languages, including RTL languages.
- Right-to-left (RTL) support — building RTL compatibility into the UI for Arabic, Hebrew, and Urdu interfaces.
- Locale detection — implementing logic to detect the user’s locale automatically (via browser settings, IP geolocation, or user preference) and serve the appropriate language version.
- Testing with pseudo-localisation — using dummy translated text to stress-test the UI before real localisation begins, identifying layout and encoding issues early.
Understanding the different types of translation and how they interact with the i18n framework helps teams plan more effectively.
Best Practices for Effective Internationalisation and Localisation
To get the most from both i18n and l10n, follow these proven best practices:
- Start with i18n, not l10n — always internationalise your product before you attempt to localise it. Reversing the order creates significant rework.
- Use translation memory (TM) — TM tools store previously translated segments and reuse them, ensuring consistency and reducing cost across multiple localisation rounds.
- Build a brand glossary — define key terms, brand names, and product-specific vocabulary before translation begins, and enforce consistent use across all target languages.
- Involve native speakers early — do not rely solely on machine translation. Native linguists with subject matter expertise catch cultural and contextual errors that machines miss.
- Localise multimedia content — subtitles, voiceovers, and on-screen text all need localisation attention, not just written copy.
- Test in-context — always review translations in the actual product interface, not just in a spreadsheet, to catch layout issues and contextual errors.
- Plan for continuous localisation — as your product evolves, your localised versions need to keep pace. Build localisation into your product development cycle, not as a one-off project.
- Adapt brand narratives, not just words — engaging viewers on social media through multilingual brand narratives shows how culturally adapted storytelling drives significantly better audience engagement.
The Goal of Internationalisation and Localisation
The ultimate goal of both i18n and l10n is to create a product or piece of content that feels native — one that users in any market can engage with naturally, without feeling as though they are using a foreign tool that has been awkwardly adapted.
Internationalisation creates the technical capability. Localisation delivers the human experience. Together, they enable businesses to grow globally while connecting locally. For businesses considering expansion into Asian markets, brand consistency across cultures and cultural sensitivity are equally as important as technical readiness.
The translation industry itself is evolving rapidly, with AI and automation tools changing how localisation projects are managed and delivered. How AI is changing the translation service industry is essential reading for businesses planning their global content strategy. Similarly, the translation industry’s major trends and challenges in 2026 reflect how continuous localisation for software is becoming the standard expectation, not the exception.
How Elite Asia Can Help With Both
Elite Asia is a full-service translation and localisation agency based in Singapore, serving B2B and B2C clients across Asia and beyond. Whether you need technical consultation on building an i18n-ready digital product, or you are ready to localise your website, app, marketing materials, or legal documents for a specific regional market, Elite Asia has the expertise to help.
Our services include software and app localisation, website localisation, content and document translation, desktop publishing, subtitling, transcription, copywriting, certified translation, and Machine Translation with Post-Editing (MTPE) — all delivered by experienced native linguists with industry knowledge.
We also offer transcreation services for businesses that need more than translation — adapting brand voice, tone, and messaging at a creative level to ensure your campaigns resonate authentically in every market.
Ready to take your business global? Explore Elite Asia’s full range of Business Localisation Services and discover how we can help you connect with new audiences in any language, in any market.
FAQs
What is the Difference Between Internationalisation and Localisation?
Internationalisation (i18n) is the process of designing and building a product so that it can be adapted for multiple languages and regions — it is a technical, engineering-led process. Localisation (l10n) is the process of actually adapting that product for a specific language, culture, or market — it is a linguistic and cultural process. I18n comes first and creates the framework; l10n fills that framework with market-specific content. Think of i18n as building a stage and l10n as the performance that takes place on it.
When Should I Use Internationalisation vs Localisation?
You should use internationalisation during the design and development phase of your product, before you launch in any market. It is about future-proofing your architecture. You use localisation when you are ready to target a specific country, language, or cultural group — taking your internationalised product and making it feel native to that audience. In practice, most global businesses need both: i18n once, and l10n for each new market they enter. For practical guidance on market-specific adaptation, how to localise your brand to an Asian market is a strong starting point.
Why is It Called I18n?
The abbreviation i18n stands for “internationalisation.” The number 18 represents the 18 letters that sit between the first letter “i” and the last letter “n” in the word “internationalisation.” This shorthand originated in the software engineering community as a practical way to refer to the concept without spelling out the entire 20-letter word each time. The convention has since become standard across the technology, translation, and localisation industries worldwide.
Why is It Called L10n?
Similarly, l10n stands for “localisation.” The number 10 represents the 10 letters between the first letter “l” and the last letter “n” in “localisation.” The abbreviation follows the same numeronym convention as i18n and was adopted by the same software and globalisation communities. Other similar numeronyms exist in the industry, such as g11n (globalisation) and t9n (translation), though i18n and l10n remain the most widely used.










