Web app i18n stack 2026

Localizing a web app is more than translating strings. Dates, numbers, currencies, plurals, RTL, SEO — all different.

Web app i18n stack 2026

Localizing a web app is broader than "translate the buttons". Teams that treat it as a string-replacement job end up retrofitting dates, plurals and URLs months later, which is far more expensive than getting the foundation right. The full job looks like this:

Web app i18n stack 2026
Full i18n pipeline — four stages, each with its own tools.
  • UI strings: buttons, labels, error messages, emails.
  • Long-form content: articles, product descriptions, help pages.
  • Dates and times in local format and the user's time zone.
  • Numbers, currencies and units.
  • Pluralization: "1 file" vs "2 files" vs "0 files", with rules that vary widely by language.
  • Right-to-left scripts: Arabic, Hebrew, Persian.
  • SEO: locale URLs, hreflang, sitemap entries.

A stack that works

  • react-i18next or next-intl for UI strings in React and Next.js; vue-i18n is the equivalent for Vue and Nuxt.
  • The built-in Intl API for dates, numbers, currencies, relative time and plural categories. Moment.js is in maintenance mode, and its own docs point to alternatives; you rarely need a date library just for formatting.
  • ICU MessageFormat for plurals and complex substitutions, so translators control word order and plural forms.
  • Content translations in a CMS or the database, not inside the JavaScript bundle.

Once you pass two or three languages, a translation management system that syncs with your repository saves a lot of copy-paste between developers and translators. Until then, JSON files in the repo plus a review step are enough.

Two short examples:

new Intl.NumberFormat('de-DE', { style: 'currency', currency: 'EUR' }).format(1234.5)
// "1.234,50 €"

// ICU message
"{count, plural, one {# file} other {# files}}"

The first formats a price the way German users expect, with no custom code. The second lets each language define its own plural forms; languages with more categories than English simply add them.

How to organize translations

  1. Namespace keys by feature (checkout.summary.total), not by page or by language file size.
  2. Load per route and per locale. Users shouldn't download every language for every screen.
  3. Define a fallback locale so a missing key shows the default language instead of a raw key.
  4. Extract strings automatically and fail CI when a locale is missing keys.
  5. Use pseudo-localization in development: stretched, accented text quickly reveals hardcoded strings and layouts that break on longer words.

SEO for multilingual apps

If public pages are localized, give each locale its own URL (/en/, /de/), not a cookie-based switch on one URL. Add reciprocal hreflang tags on every version plus an x-default, and list each version in the sitemap. Don't force redirects by IP address: let users and crawlers reach any language and offer a switcher instead.

What goes wrong

  • Hardcoded strings in JSX or templates. If you start without i18n, retrofitting it is painful; set up the library on day one even with a single language.
  • English plural rules (one/many) applied to languages that have more forms.
  • Concatenating translated fragments ("You have" + n + "messages"), which breaks word order in other languages.
  • hreflang mistakes: missing return links, duplicates, no x-default.
  • All translations in one giant JSON file loaded everywhere.
  • Ignoring RTL even when "we don't support Arabic": user-generated content and names can still be right-to-left in mixed text.
  • Dates stored in local time instead of UTC and converted on display.

Checklist

  • i18n library in place from the first commit.
  • All formatting through Intl, no manual date or number strings.
  • ICU messages for anything with a count.
  • Missing-key check in CI, pseudo-locale in development.
  • Locale URLs, hreflang and sitemap for public pages.
  • Layout tested with long strings and with dir="rtl".

The framework choice matters less here than the discipline; both sides of Next.js vs Nuxt have solid i18n tooling. We build multilingual products as part of web application development, starting with i18n in the foundation rather than as a later patch.

Taking your web app to new markets? Message us on Telegram or MAX.

Web application development
Related service — let's discuss your project.

Got a project on this topic? Tell us the task — we'll come back with an estimate and a schedule.

Message on Telegram → Message on MAX