i18next/next-i18next

Health v2 · maintenance only

Adoption not part of the score

6161 stars · 759 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

next-i18next is a thin layer on top of i18next and react-i18next that handles Next.js-specific internationalization wiring, including middleware, server/client splits, and resource hydration. It supports the App Router, Pages Router, and mixed setups with locale-in-path or cookie-based language detection.

Use cases

• translate a next.js app into multiple languages
• add internationalization to next.js app router project
• serve localized routes like /en/about in next.js
• detect user language via cookie in next.js
• use i18next with server components in next.js
• migrate a pages router next.js app to app router with i18n
• manage translation files for a react next.js site

When to choose

• you are building a Next.js app (App Router, Pages Router, or mixed) and want i18next-based translations
• you want locale routing or cookie-based language detection handled for you
• you already know i18next/react-i18next and need Next.js wiring

When to avoid

• you are not using Next.js (use react-i18next directly)
• you need a fully managed translation platform rather than a library (consider locize backend)
• you use a framework other than Next.js with its own i18n solution

Facets

library · maturity active

internationalization ssr middleware routing web-development frontend nextjs i18next react app-router translation localization nodejs web-server

Member repositories

For agents

markdown · JSON · MCP: product_card(name="i18next/next-i18next")