# 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
Published Aug 17, 2026

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

In this guide

Contributors

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

Try the workflow, not just the idea.

Start with 500 free credits to explore creation, translation and personalization in Vitra Universe.
[Start creating free →](https://universe.vitra.ai/auth/sign-up)[Or use a free working template](https://www.vitra.ai/templates)

> **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.

Put this guide to work

## Website & app localization

Keep website, app and structured-content translation connected to terminology, context and review.

[Follow the website & app localization guides](https://www.vitra.ai/blog/topics/website-app-localization)[Use the free translation brief template](https://www.vitra.ai/templates/translation-brief)[Explore software localization](https://www.vitra.ai/solutions/software-localization)

Continue the topic

## Related guides

Read the next explanation, example or review step for this subject.

General

[App Store Listing Localization for iOS](https://www.vitra.ai/general/app-store-listing-localization)
An App Store listing has tight character limits and its own indexing. What really drives installs in a market, and which fields are searched at all.

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

General

[Headless CMS Localization Patterns](https://www.vitra.ai/general/headless-cms-localization)
A headless CMS gives you a choice about how locales are modelled, and the wrong choice is expensive to undo. The three patterns and what each costs.

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

General

[Mobile App Localization AI Compared](https://www.vitra.ai/general/mobile-app-localization-ai)
App localization is four separate jobs and most tools do one of them. What to check beyond string translation, and where store review blocks a release.

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

[Browse the topic guides](https://www.vitra.ai/blog/topics)

---

## 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",
      "url": "https://www.vitra.ai/author/samhitha"
    }
  ],
  "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": "Translation & content workflows",
      "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."
      }
    }
  ]
}
```