Internationalization

Ship your product in more than one language.

Shipping in more than one language means managing translation files, locale-specific formatting, and often right-to-left layouts. These tools range from translation management platforms to libraries that handle the formatting and routing side inside your app. Start early if international users matter, since retrofitting i18n into an app built assuming one language is more work than building it in.

Crowdin

The heavier-weight option once you have real translators or agencies in the loop, not just AI-drafted strings. Glossary and workflow management for teams.

↗

i18next

Framework-agnostic i18n if you're not on Next.js, or want the same setup across a React Native app and a web app.

↗

Lingo.dev

Open-source CLI/compiler that wires an LLM into your translation pipeline, so new strings get drafted automatically instead of sitting in a spreadsheet for a translator.

↗

Locize

Continuous localization service from the team behind i18next. Ships new translations to production over a CDN without a redeploy.

↗

next-intl

The i18n library most people reach for in a Next.js App Router project. Type-safe messages, ICU plurals, and localized routing out of the box.

↗

Tolgee

Self-hostable translation management with an in-context editor. Hold a key, click text in your running app, and edit the actual translation right there.

↗