# Internationalization vs Localization | Vitra.ai

> Internationalization is engineering you do once; localization is content you do per market. Confusing them is why translated products still break.

**Canonical URL**: https://www.vitra.ai/general/internationalization-vs-localization
**Source**: This is the Markdown rendering of https://www.vitra.ai/general/internationalization-vs-localization, generated at build time from that page.

---

3 min read

# Internationalization vs Localization

Internationalization is engineering you do once; localization is content you do per market. Confusing them is why translated products still break.

[Samhitha J Bhatt](https://www.vitra.ai/author/samhitha)
Senior Product Manager , Vitra.ai
Updated Aug 17, 2026

![Internationalization vs Localization](https://www.vitra.ai/static/images/blog/internationalization-vs-localization.jpg)

Table of contents

[Two different jobs, two different teams](#two-different-jobs-two-different-teams)

[What belongs to each](#what-belongs-to-each)

[Skipping i18n is the expensive mistake](#skipping-i18n-is-the-expensive-mistake)

[The practical sequence](#the-practical-sequence)

[FAQ](#faq)

Contributors

[Samhitha J Bhatt](https://www.vitra.ai/author/samhitha)
Senior Product Manager

Subscribe to our newsletter

Subscribe

> **Quick answer —** Internationalization is the engineering that makes a product capable of supporting other languages. Localization is the content work for each market. Skipping the first makes the second produce broken output.[Vitra.ai Universe](https://www.vitra.ai/platform) creates, translates, adapts and publishes from one place.

## Two different jobs, two different teams

Internationalization — i18n — is preparation. Externalising [strings](https://www.vitra.ai/solutions/software-localization), handling Unicode, supporting different date and number formats, allowing text to expand, supporting right-to-left layout.

Localization — l10n — is the per-market work. Translation, cultural adaptation, local formats, market-specific content.

The first is engineering, done once. The second is content, done repeatedly.

## What belongs to each

Task

i18n

l10n

Externalise strings from code

Yes

—

Unicode and encoding

Yes

—

Date, number, currency formatting

Yes

—

Layout that tolerates expansion

Yes

—

[RTL support](https://www.vitra.ai/general/rtl-layout-localization)

Yes

—

Plural rule handling

Yes

—

Translating the strings

—

Yes

Local imagery and examples

—

Yes

Market-specific legal text

—

Yes

Plural rules are the clearest example of the split. English has two forms; several languages have more, and some have one. Handling that is engineering. It cannot be solved by a translator, and a product that assumes two forms produces wrong grammar no translation fixes.

## Skipping i18n is the expensive mistake

Translating a product that was never internationalised produces text hard-coded in components, dates in one format, layouts that break at longer strings and concatenated sentences that cannot be reordered.

Concatenation is the worst of them.

Building a sentence by joining fragments assumes the source language's word order, and there is no correct translation of a fragment whose position changes.

## The practical sequence

Internationalise, then [pseudo-localize](https://www.vitra.ai/general/localized-website-testing) to prove it — padded accented strings expose hard-coded text and fixed-width containers before any translator is involved and while fixes are cheap.

Only then start localizing, with [memory](https://www.vitra.ai/features/translation-memory), terminology and a [quality gate](https://www.vitra.ai/features/quality-control) set up so the first market's decisions carry into every one after it.

Doing it in that order costs one sprint. Doing it in reverse costs the sprint anyway, plus re-translating everything the fixes changed.

## FAQ

**What is the difference between internationalization and localization?** Internationalization is the engineering that makes a product capable of other languages — externalised strings, Unicode, formats, expandable layout. Localization is the per-market content work such as translation.

**Can you localize without internationalizing first?** Not successfully. Text hard-coded in components, fixed-width layouts and concatenated sentences cannot be fixed by translation, so the output is broken regardless of translation quality.

**Why are concatenated sentences a problem?** Because joining fragments assumes the source language's word order. When a translation needs a different order there is no correct rendering of a fragment whose position must change.

**How do you verify internationalization is complete?** Pseudo-localization. Rendering every string padded and accented exposes hard-coded text, fixed-width containers and encoding faults before a translator is involved and while fixes are cheap.

Our blog

## Lastest blog posts

Tool and strategies modern teams need to help their companies grow.

Automotive

[Automotive Brochure Localization by Market](https://www.vitra.ai/automotive/automotive-brochure-localization)
A car brochure is a spec grid, a legal footer and a photo library, all market-specific. What actually has to change, and why the layout decides the schedule.

[Samhitha J Bhatt](https://www.vitra.ai/author/samhitha)
Aug 18, 2026

Automotive

[Automotive Campaign Localization Across Markets](https://www.vitra.ai/automotive/automotive-campaign-localization)
Campaigns run through national companies and dealer networks, so one master becomes hundreds of files. Where the offer text and the disclaimers actually break.

[Samhitha J Bhatt](https://www.vitra.ai/author/samhitha)
Aug 18, 2026

Automotive

[Car Service Manual Translation for Technicians](https://www.vitra.ai/automotive/automotive-service-manual-translation)
A workshop manual is read mid-repair by someone with the car on a lift. What that demands of procedures, torque figures and fault codes, in every language.

[Samhitha J Bhatt](https://www.vitra.ai/author/samhitha)
Aug 18, 2026

[View all posts](https://www.vitra.ai/blog/page/1)

---

## Structured data

```json
{
  "@context": "https://schema.org",
  "@type": "Article",
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://www.vitra.ai/general/internationalization-vs-localization"
  },
  "headline": "Internationalization vs Localization",
  "image": [
    {
      "@type": "ImageObject",
      "url": "https://www.vitra.ai/static/images/blog/internationalization-vs-localization.jpg"
    }
  ],
  "datePublished": "2026-08-17T00:00:00.000Z",
  "dateModified": "2026-08-17T00:00:00.000Z",
  "author": [
    {
      "@type": "Person",
      "name": "Samhitha J Bhatt"
    }
  ],
  "publisher": {
    "@type": "Organization",
    "name": "Vitra.ai",
    "logo": {
      "@type": "ImageObject",
      "url": "https://www.vitra.ai/static/images/vitra-v-logo.png"
    }
  },
  "description": "Internationalization is engineering you do once; localization is content you do per market. Confusing them is why translated products still break."
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://www.vitra.ai"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "General",
      "item": "https://www.vitra.ai/general"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Internationalization vs Localization",
      "item": "https://www.vitra.ai/general/internationalization-vs-localization"
    }
  ]
}
```

```json
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is the difference between internationalization and localization?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Internationalization is the engineering that makes a product capable of other languages — externalised strings, Unicode, formats, expandable layout. Localization is the per-market content work such as translation."
      }
    },
    {
      "@type": "Question",
      "name": "Can you localize without internationalizing first?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Not successfully. Text hard-coded in components, fixed-width layouts and concatenated sentences cannot be fixed by translation, so the output is broken regardless of translation quality."
      }
    },
    {
      "@type": "Question",
      "name": "Why are concatenated sentences a problem?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Because joining fragments assumes the source language's word order. When a translation needs a different order there is no correct rendering of a fragment whose position must change."
      }
    },
    {
      "@type": "Question",
      "name": "How do you verify internationalization is complete?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Pseudo-localization. Rendering every string padded and accented exposes hard-coded text, fixed-width containers and encoding faults before a translator is involved and while fixes are cheap."
      }
    }
  ]
}
```