top of page

Internationalization vs. Localization: How They Differ

Writer: Umar Usman
Umar Usman
Nov 10
10 min read

Colleagues review a localized mobile app

Internationalization (i18n) is the engineering and design work that lets a product handle any language, region or culture. Localization (l10n) is the adaptation of that product for one specific market: its language, formats, imagery and legal requirements. You internationalize once, early, and then localize for every market you enter. Skip the first step and the second gets slower, costlier and more fragile.

 

This guide explains both terms with concrete examples, shows where each one sits in a product timeline, and covers testing, the “globalization” confusion and the mistakes that cost teams the most.



TL;DR

 

  • Internationalization prepares the product: Unicode, externalized text, flexible layouts, locale-aware dates, numbers and currencies. It is mostly developer and designer work.

  • Localization adapts the prepared product to a given locale: translation, formats, visuals, legal and cultural details. It is mostly translator and localizer work.

  • Internationalization comes first and is done once. Localization repeats for each new market.

  • Retrofitting a product that was built for one culture is far harder than designing it for many from the start.

  • “Globalization” is used inconsistently: sometimes it means internationalization, sometimes both steps together.

 

Table of Contents

 

 

The difference at a glance

 

Internationalization (i18n)

Localization (l10n)

Goal

Make the product able to support many markets

Make the product feel native in one market

Main people

Developers, designers, product managers

Translators, localizers, linguistic reviewers

When

During design and development

After the product is prepared, then for each new market

Frequency

Once, then maintained as the product evolves

Every language or region, plus every update

Typical output

Code and design that separate text and data from logic

Translated text, adapted formats, images and legal content

Typical risk if skipped

Hardcoded strings, broken layouts, garbled characters

Stilted, literal or culturally off content

The W3C’s definitions put it simply: internationalization is the design and development that enables easy localization for audiences varying in culture, region or language. Localization is the adaptation of a product, application or document content to meet the language, cultural and other requirements of a specific target market, called a locale. In short, developers internationalize so translators and localizers can do their work without touching the code.

 

What internationalization actually involves

 

Think of internationalization as removing every assumption that your product will only ever be used by one kind of person. Oracle’s Java tutorials describe an internationalized program as one where the same executable can run worldwide once localized data is added, where text is stored outside the source code and retrieved dynamically, and where new languages do not require recompiling.

 

The W3C lists the typical building blocks:

 

  • Removing barriers to localization, including enabling Unicode and handling legacy character encodings correctly.

  • Supporting features that may not be used until later, such as bidirectional text markup for right-to-left scripts.

  • Locale-aware behavior: date and time formats, local calendars and number formats.

  • Separating localizable elements from source code or content, and taking care over string concatenation.

 

Microsoft’s software internationalization guidance adds practical rules. User data should not be limited to a particular script. Stored data should not be tied to one country, time zone or unit of measurement (storing times in UTC is the example it gives). The application should respect the operating system’s locale settings for numbers, currency, time and dates. The same page stresses thinking about this from the very beginning of design, even if the first release is not translated at all.

 

Internationalization in practice

 

A few examples of what this looks like on a real team:

 

  1. A checkout form accepts postal codes of different lengths and formats, not just five-digit ZIP codes, and does not insist on a state field.

  2. A user’s name field allows one name, several names and non-Latin characters, instead of splitting into “first” and “last”.

  3. A button label lives in a resource file, not in the code, and the button can grow when the text gets longer.

  4. A sentence assembled from fragments (“You have” + number + “new messages”) is replaced by a single translatable string with a placeholder, because word order and plural rules differ by language.

  5. Timestamps are stored in UTC and shown in the user’s local format.

 

None of this involves a single translated word. That is the point: the product is ready, and no language has been added yet.

 

What localization actually involves

 

Localization takes the prepared product and adapts it to a locale. The American Translators Association describes it as more than translating software: the goal is for the product to look and feel as if it had been developed for the target market from the start.

 

According to the W3C, localization can involve:

 

  • numeric, date and time formats, and currency

  • keyboard layout and sorting rules

  • symbols, icons and colors

  • culturally sensitive text and graphics

  • legal requirements

  • address and contact formats

  • readability of the script itself

 

Microsoft gives a neat, small example in its localization overview: a US-English sentence about a train ticket’s cost on a given date may need the price in local currency and the date switched from month-day-year to day-month-year for German or Egyptian readers.

 

Where language quality decides the outcome

 

Localization is where a native-sounding result is won or lost. Terminology has to be consistent across screens, documentation and marketing. Tone has to match what users in that market expect. Humor, idioms and references often need replacing rather than translating. Content written to persuade is a good case: web copywriting that adapts to readers works because it starts from how the target audience thinks and searches, and the same principle drives good localization of marketing pages.

 

For teams working into Hungarian, this is also where subject knowledge matters. A medical device interface, a legal template and a car’s infotainment menu each carry their own terminology, and a consistent glossary keeps them stable across releases. Our guide to terminology management in translation shows how to build one.

 

Why the order matters

 

Localization uses the flexibility that internationalization provides. Microsoft’s .NET globalization guide lays out three steps for a world-ready application: globalization (building it culture-neutral and language-neutral), a localizability review, and then localization. Following them, it says, spares you from retrofitting an application designed for one culture such as U.S. English.

 

Oracle’s Siebel documentation makes the dependency blunt: a product must be internationalized first or most localization cannot be performed. The W3C adds that retrofitting a deliverable built for one culture is much more difficult and time-consuming than designing it for a global audience from the outset.

 

In practical terms, here is what each path looks like:

 

Situation

What happens

Internationalized early

New language added by delivering translated resource files; layout holds; dates and numbers adapt automatically

Not internationalized

Engineers dig through code to extract text, fix encodings and rebuild screens before translation can even start

Internationalized but never localized

The product works technically but reads as foreign, with literal text, wrong formats or unsuitable imagery

The third row is the one people forget. Internationalization is not a substitute for localization. It only makes localization possible.

 

Internationalization vs. localization: worked examples

 

A mobile app for a US market. The team stores all interface text in resource files, uses a library that formats dates and currency by locale, and designs buttons that can stretch. That is internationalization. When the company later launches in Hungary, a localizer translates the strings, adapts the date format, switches to forint, rewrites a promotional message that relied on an American idiom and checks the legal notice. That is localization.

 

A video game. Internationalization means subtitles and dialogue live in external files, fonts support the characters of every target language, and menus do not break when a string expands. Localization means the dialogue, jokes, character names and cultural references are adapted so players in each region get the intended experience, not a literal rendering.

 

An e-learning course. Internationalization covers text kept separate from video and graphics, and layouts that tolerate longer words. Localization covers narration, on-screen text, examples and units. See our article on e-learning translation and course localization for how that plays out.


Four examples contrasting preparation and adaptation

Translation files. Many teams hand localizers structured files rather than raw documents. Returning those files with the structure intact is its own skill, covered in our guide to XLIFF file translation.

 

Internationalization testing vs. localization testing

 

The split carries over into quality assurance. According to Tricentis, internationalization testing checks that the codebase is ready for global use and can support different languages, generally during development and mostly by developers. Localization testing checks that the software feels natural in a given language and cultural context, usually after development, often by translators and testers native to the region.

 

Microsoft’s validation guide describes both halves:

 

  • Before translation: confirm data is not limited to one script, the app can display text in the scripts of target markets, it respects operating system conventions, and strings are externalized with consistent source terminology.

  • After translation: confirm interface text displays correctly under each language’s conventions, carries the same meaning as the source, and that the product meets market needs such as regional standards, legal requirements and payment methods.

 

A useful bridge between the two is pseudo-localization. The ATA notes it replaces translatable text with fake text that simulates problems like accented characters and string expansion of 30% or more, which exposes internationalization bugs before any real translation is paid for.

 

Linguistic review has a limit worth planning around. Microsoft points out that reviewers need to see translations in the running product because appropriateness is hard to confirm without the user context. Build in time for in-context review rather than checking a spreadsheet alone.

 

Is globalization the same as localization?

 

No. The W3C notes that some people use “globalization” to mean the same thing as internationalization. Microsoft’s glossary observes that internationalization is sometimes treated as a synonym for globalization and sometimes as globalization plus localization, and recommends using it for all activities that improve a product in a worldwide context.

 

Because usage varies, define your terms at the start of any project. When you brief a vendor, say exactly which tasks you mean: engineering readiness, translation, adaptation, testing, or all of them.

 

Common mistakes and how to avoid them

 

  1. Treating localization as translation only. Formats, images, colors, legal text and contact details are part of the job.

  2. Hardcoding text. Every string in code is a future bug and a future delay.

  3. Concatenating sentence fragments. Grammar differs by language; give translators whole sentences with placeholders.

  4. Designing fixed-size interfaces. Text expands in translation, so leave room.

  5. Ignoring terminology. Without an approved glossary, the same feature gets three names across the interface.

  6. Leaving review for the last day. Plan in-context checks and a realistic schedule. If a release is urgent anyway, see how we approach rush translation.

  7. Neglecting confidentiality. Unreleased software and documents often need protection; our guide to confidential translation services covers it.

 

A simple readiness checklist

 

Before you send content to a localizer, check that:

 

  • Text is externalized and no sentence is built from fragments.

  • Unicode is enabled everywhere, including databases and file exports.

  • Dates, times, numbers and currencies come from locale settings.

  • Layouts tolerate longer text and, if needed, right-to-left scripts.

  • A glossary and style guide exist, even a short one.

  • Context is available to the translator: screenshots, notes, character limits.

  • You know who reviews the result in the product and how long that takes.

 

Our perspective on it

 

Most of the trouble we see in localization projects was planted months earlier, in development. Text sits inside images, sentences are glued together from pieces, and nobody wrote down what a key term should be called. Good internationalization does not remove the need for a skilled linguist. It gives the linguist room to work.   We handle every project personally, as one experienced translator who combines subject knowledge with current CAT tools. That means one person who learns your terminology and keeps it consistent from the first string to the last update. It also means a single point of contact, including outside regular business hours when a release is close.   Our advice is to bring the localizer in before the interface is frozen. A short conversation about placeholders, character limits and context saves far more time than it costs, and it makes the finished product read as if it had been written in the target language from day one.   Bernadett

 

Localization with Wordsbyme

 

If your product is ready and you need Hungarian, English, German or French content that reads naturally, we translate and localize technical, medical, legal, automotive, financial, marketing, software, website, multimedia and video game content. We also offer machine translation post-editing; the levels, workflow and pricing are explained on our blog.

 

Published starting rates are per word: translation into Hungarian from €0.05, translation into English, German or French from €0.07, full post-editing from €0.04 and light post-editing from €0.03. Localization is quoted per project, since the scope depends on your product.


Wordsbyme

Send us your files or a sample through wordsbyme.hu and we will reply with a clear scope and timeline.

 

FAQ

 

What is an example of internationalization?

 

Storing all interface text in resource files instead of in code is a classic one. The W3C also lists enabling Unicode, taking care with string concatenation and avoiding code that depends on interface string values. None of it adds a language; it just makes adding one easy.

 

What is an example of localization?

 

A US sentence about a train ticket price on a date, adapted for German readers, gets the local currency and a day-month-year date. Microsoft uses this exact case. Translating the text, adapting images and updating legal notices for that market are further examples.

 

What is the difference between internationalization and localization testing?

 

Internationalization testing checks, mostly during development, that the code can support different languages and regions. Localization testing happens after translation and checks that the product reads and works naturally for one locale, usually with native-speaking testers.

 

Is globalization the same as localization?

 

No. Globalization is sometimes used as another word for internationalization, and sometimes for both steps together. Localization is only the market-specific adaptation, so it is best to define the terms before briefing anyone.

 

Do I need both for a small product?

 

If you plan to serve more than one market, yes. Even a modest amount of internationalization up front, such as externalized text and locale-aware formats, keeps later localization quicker and cheaper.

 

Sources

 

Recommended

 

 
 
 

Comments


bottom of page