Ask your question and get a summary of the document by referencing this page and the AI provider of your choice
Version History
- "Init history"v9.0.013/06/2026
The content of this page was translated using an AI.
See the last version of the original content in EnglishIf you have an idea for improving this documentation, please feel free to contribute by submitting a pull request on GitHub.
GitHub link to the documentationCopy doc Markdown to clipboard
Migrate from next-i18next to Intlayer
For a complete and detailed step-by-step tutorial, please see our full next-i18next Migration Guide.
Intlayer handles all Next.js Pages Router and App Router implementations transparently. Using the adapter lets you migrate your next-i18next implementation with zero code rewrite.
What to do
To begin, run:
Copy the code to the clipboard
npx intlayer initThis creates the required Intlayer setup file. To swap to Intlayer behind the scenes, update your next.config.ts:
Copy the code to the clipboard
import type { NextConfig } from "next";import { createNextI18nPlugin } from "@intlayer/next-i18next/plugin";const withIntlayer = createNextI18nPlugin();const nextConfig: NextConfig = {};export default withIntlayer(nextConfig);What it does under the hood
The createNextI18nPlugin composes Next.js's native behavior alongside the core next-intlayer plugin, injecting all required Webpack/Turbopack aliases for next-i18next, react-i18next, and i18next.
Under the hood:
serverSideTranslations&appWithTranslation: They now function as wrappers for Intlayer's internal loaders, circumventing large static JSON injection.- Client hooks: Delegates immediately to
@intlayer/react-i18nextretaining all formatting, plurals, and nested namespace features.