next-i18next VS next-intl VS intlayer | Next.js Internationalisation (i18n)

Let’s take a look into the similarities and differences between three i18n options for Next.js: next-i18next, next-intl, and Intlayer.

This is not a full tutorial. It’s a comparison to help you pick.

We focus on Next.js 13+ App Router (with React Server Components) and evaluate:

1. Architecture & content organisation
2. TypeScript & safety
3. Missing translation handling
4. Routing & middleware
5. Performance & loading behaviour
6. Developer experience (DX), tooling & maintenance
7. SEO & large-project scalability

tl;dr: All three can localise a Next.js app. If you want component-scoped content, strict TypeScript types, build-time missing-key checks, tree-shaken dictionaries, and first-class App Router + SEO helpers, Intlayer is the most complete, modern choice.

One confusion often made by developers is to think that next-intl is the Next.js version of react-intl. It's not—next-intl is maintained by Amann, while react-intl is maintained by FormatJS.

In short

• next-intl - Lightweight, straightforward message formatting with solid Next.js support. Centralised catalogues are common; DX is simple, but safety and large-scale maintenance remain mostly your responsibility.
• next-i18next - i18next in Next.js clothing. Mature ecosystem and features via plugins (e.g., ICU), but configuration can be verbose and catalogues tend to centralise as projects grow.
• Intlayer - Component-centric content model for Next.js, strict TS typing, build-time checks, tree-shaking, built-in middleware & SEO helpers, optional Visual Editor/CMS, and AI-assisted translations.

Move

Library	GitHub Stars	Total Commits	Last Commit	First Version	NPM Version	NPM Downloads
aymericzip/intlayer				April 2024
amannn/next-intl				Nov 2020
i18next/i18next				Jan 2012
i18next/next-i18next				Nov 2018

Badges update automatically. Snapshots will vary over time.

Side-by-Side Feature Comparison (Next.js focused)

Introduction

Next.js provides built-in support for internationalised routing (e.g. locale segments). However, that feature does not perform translations on its own. You still need a library to render localised content to your users.

Many i18n libraries exist, but in the Next.js ecosystem today, three are gaining traction: next-i18next, next-intl, and Intlayer.

Architecture & scalability

• next-intl / next-i18next: Default to centralised catalogues per locale (plus namespaces in i18next). Works fine early on, but often becomes a large shared surface area with increasing coupling and key churn.
• Intlayer: Encourages per-component (or per-feature) dictionaries co-located with the code they serve. This reduces cognitive load, facilitates duplication/migration of UI pieces, and minimises cross-team conflicts. Unused content is naturally easier to identify and remove.

Why it matters: In large codebases or design-system setups, modular content scales better than monolithic catalogues.

Bundle sizes & dependencies

After building the application, the bundle is the JavaScript that the browser will load to render the page. Bundle size is therefore important for application performance.

Two components are important in the context of a multi-language application bundle:

• The application code
• The content loaded by the browser

Application Code

The significance of application code is minimal in this case. All three solutions are tree-shakable, meaning that unused parts of the code are not included in the bundle.

Here is a comparison of the JavaScript bundle size loaded by the browser for a multi-language application with the three solutions.

If we do not require any formatter in the application, the list of exported functions after tree-shaking will be:

• next-intlayer: useIntlayer, useLocale, NextIntlClientProvider, (Bundle size is 180.6 kB -> 78.6 kB (gzip))
• next-intl: useTranslations, useLocale, NextIntlClientProvider, (Bundle size is 101.3 kB -> 31.4 kB (gzip))
• next-i18next: useTranslation, useI18n, I18nextProvider, (Bundle size is 80.7 kB -> 25.5 kB (gzip))

These functions are merely wrappers around React context/state, so the overall impact of the i18n library on bundle size is minimal.

Intlayer is slightly larger than next-intl and next-i18next because it incorporates more logic in the useIntlayer function. This is related to markdown and intlayer-editor integration.

Content and Translations

This part is often ignored by developers, but let us consider the case of an application composed of 10 pages in 10 languages. Let us assume that each page integrates 100% unique content to simplify the calculation (in reality, much content is redundant between pages, e.g., page title, header, footer, etc.).

A user wanting to visit the /fr/about page will load the content of one page in a given language. Ignoring content optimisation would mean loading 8,200% ((1 + (((10 pages - 1) × (10 languages - 1)))) × 100) of the application content unnecessarily. Do you see the problem? Even if this content remains text, and while you probably prefer to think about optimising your site's images, you are sending useless content across the globe and making users' computers process it for nothing.

Two important issues:

• Splitting by route:

  If I'm on the /about page, I don't want to load the content of the /home page

• Splitting by locale:

  If I'm on the /fr/about page, I don't want to load the content of the /en/about page

Again, all three solutions are aware of these issues and allow managing these optimisations. The difference between the three solutions is the DX (Developer Experience).

next-intl and next-i18next use a centralised approach to manage translations, allowing splitting JSON by locale and by sub-files. In next-i18next, we call the JSON files 'namespaces'; next-intl allows declaring messages. In intlayer, we call the JSON files 'dictionaries'.

• In the case of next-intl, like next-i18next, content is loaded at the page/layout level, then this content is loaded into a context provider. This means the developer must manually manage the JSON files that will be loaded for each page.

In practice, this implies that developers often skip this optimisation, preferring to load all content in the page's context provider for simplicity.

• In the case of intlayer, all content is loaded in the application. Then a plugin (@intlayer/babel / @intlayer/swc) takes care of optimising the bundle by loading only the content used on the page. The developer therefore doesn't need to manually manage the dictionaries that will be loaded. This allows better optimisation, better maintainability, and reduces development time.

As the application grows (especially when multiple developers work on the application), it is common to forget to remove content that is no longer used from JSON files.

Note that all JSON is loaded in all cases (next-intl, next-i18next, intlayer).

This is why Intlayer's approach is more performant: if a component is no longer used, its dictionary is not loaded in the bundle.

How the library handles fallbacks is also important. Let us consider that the application is in English by default, and the user visits the /fr/about page. If translations are missing in French, we will consider the English fallback.

In the case of next-intl and next-i18next, the library requires loading the JSON related to the current locale, but also to the fallback locale. Thus, considering that all content has been translated, each page will load 100% unnecessary content. In comparison, intlayer processes the fallback at dictionary build time. Thus, each page will load only the content used.

Here is an example of the impact of bundle size optimisation using intlayer in a vite + react application:

Move

Optimised bundle	Bundle not optimised

TypeScript & safety

Why it matters: Strong typing shifts failures left (CI/build) instead of right (runtime).

Missing translation handling

next-intl

• Relies on runtime fallbacks (e.g., show the key or default locale). Build doesn’t fail.

next-i18next

• Relies on runtime fallbacks (e.g., show the key or default locale). Build doesn’t fail.

intlayer

• Build-time detection with warnings/errors for missing locales or keys.

Why it matters: Catching gaps during build prevents “mystery strings” in production and aligns with strict release gates.

Routing, middleware & URL strategy

• Generates strict types from your content. IDE autocompletion and compile-time errors catch typos and missing keys before deployment.

  </Column> </Columns>

Why it matters: Strong typing shifts failures left (CI/build) instead of right (runtime).

Missing translation handling

next-intl

• Relies on runtime fallbacks (e.g., show the key or default locale). Build does not fail.

next-i18next

• Relies on runtime fallbacks (e.g., show the key or default locale). Build does not fail.

intlayer

• Build-time detection with warnings/errors for missing locales or keys.

Why it matters: Catching gaps during build prevents “mystery strings” in production and aligns with strict release gates.

Routing, middleware & URL strategy

Why it matters: Fewer custom glue layers; consistent UX and clean SEO across locales.

Server Components (RSC) alignment

Why it matters: Cleaner mental model and fewer edge cases in hybrid trees.

DX, tooling & maintenance

Why it matters: Lowers operational costs and shortens the feedback loop between developers and content authors.

Integration with localisation platforms (TMS)

Large organisations often rely on Translation Management Systems (TMS) like Crowdin, Phrase, Lokalise, Localizely, or Localazy.

• Why companies care

  • Collaboration & roles: Multiple actors are involved: developers, product managers, translators, reviewers, marketing teams.
  • Scale & efficiency: continuous localisation, in‑context review.

• next-intl / next-i18next

  • Typically use centralised JSON catalogues, so export/import with TMS is straightforward.
  • Mature ecosystems and examples/integrations for the platforms above.

• Intlayer

  • Encourages decentralised, per-component dictionaries and supports TypeScript/TSX/JS/JSON/MD content.
  • This improves modularity in code, but can make plug‑and‑play TMS integration harder when a tool expects centralised, flat JSON files.
  • Intlayer provides alternatives: AI‑assisted translations (using your own provider keys), a Visual Editor/CMS, and CLI/CI workflows to catch and prefill gaps.

Note: next-intl and i18next also accept TypeScript catalogues. If your team stores messages in .ts files or decentralises them by feature, you may encounter similar TMS friction. However, many next-intl setups remain centralised in a locales/ folder, which is somewhat easier to refactor to JSON for TMS.

Developer Experience

This section provides a detailed comparison between the three solutions. Rather than considering simple cases, as described in the 'getting started' documentation for each solution, we will examine a real use case, more akin to an actual project.

App structure

The app structure is important to ensure good maintainability of your codebase.

.├── public│   └── locales│       ├── en│       │  ├── home.json│       │  └── navbar.json│       ├── fr│       │  ├── home.json│       │  └── navbar.json│       └── es│          ├── home.json│          └── navbar.json├── next-i18next.config.js└── src    ├── middleware.ts    ├── app    │   └── home.tsx    └── components        └── Navbar            └── index.tsx

.├── locales│   ├── en│   │  ├── home.json│   │  └── navbar.json│   ├── fr│   │  ├── home.json│   │  └── navbar.json│   └── es│      ├── home.json│      └── navbar.json├── i18n.ts└── src    ├── middleware.ts    ├── app    │   └── home.tsx    └── components        └── Navbar            └── index.tsx

.├── intlayer.config.ts└── src    ├── middleware.ts    ├── app    │   └── home    │       └── index.tsx    │       └── index.content.ts    └── components        └── Navbar            ├── index.tsx            └── index.content.ts

Comparison

• next-intl / next-i18next: Centralised catalogues (JSON; namespaces/messages). Clear structure, integrates well with translation platforms, but can lead to more cross-file edits as apps grow.
• Intlayer: Per-component .content.{ts|js|json} dictionaries co-located with components. Easier component reuse and local reasoning; adds files and relies on build-time tooling.

Setup and Loading Content

As mentioned previously, you must optimise how each JSON file is imported into your code. How the library handles content loading is important.

module.exports = {  i18n: {    locales: ["en", "fr", "es"],    defaultLocale: "en",  },};

import { appWithTranslation } from "next-i18next";const MyApp = ({ Component, pageProps }) => <Component {...pageProps} />;export default appWithTranslation(MyApp);

import type { GetStaticProps } from "next";import { serverSideTranslations } from "next-i18next/serverSideTranslations";import { useTranslation } from "next-i18next";import { I18nextProvider, initReactI18next } from "react-i18next";import { createInstance } from "i18next";import { ClientComponent, ServerComponent } from "@components";export default function HomePage({ locale }: { locale: string }) {  // Explicitly declare the namespace used by this component  const resources = await loadMessagesFor(locale); // your loader (JSON, etc.)  const i18n = createInstance();  i18n.use(initReactI18next).init({    lng: locale,    fallbackLng: "en",    resources,    ns: ["common", "about"],    defaultNS: "common",    interpolation: { escapeValue: false },  });  const { t } = useTranslation("about");  return (    <I18nextProvider i18n={i18n}>      <main>        <h1>{t("title")}</h1>        <ClientComponent />        <ServerComponent />      </main>    </I18nextProvider>  );}export const getStaticProps: GetStaticProps = async ({ locale }) => {  // Only preload the namespaces required for THIS page  return {    props: {      ...(await serverSideTranslations(locale ?? "en", ["common", "about"])),    },  };};

import { getRequestConfig } from "next-intl/server";import { notFound } from "next/navigation";// Can be imported from a shared configconst locales = ["en", "fr", "es"];export default getRequestConfig(async ({ locale }) => {  // Validate that the incoming `locale` parameter is valid  if (!locales.includes(locale as any)) notFound();  return {    messages: (await import(`../messages/${locale}.json`)).default,  };});

import { NextIntlClientProvider } from "next-intl";import { getMessages, unstable_setRequestLocale } from "next-intl/server";import pick from "lodash/pick";export default async function LocaleLayout({  children,  params,}: {  children: React.ReactNode;  params: { locale: string };}) {  const { locale } = params;  // Set the active request locale for this server render (RSC)  unstable_setRequestLocale(locale);  // Messages are loaded server-side via src/i18n/request.ts  // (see next-intl docs). Here we only send a subset to the client  // that is needed for client components (payload optimisation).  const messages = await getMessages();  const clientMessages = pick(messages, ["common", "about"]);  return (    <html lang={locale}>      <body>        <NextIntlClientProvider locale={locale} messages={clientMessages}>          {children}        </NextIntlClientProvider>      </body>    </html>  );}

import { getTranslations } from "next-intl/server";import { ClientComponent, ServerComponent } from "@components";export default async function LandingPage({  params,}: {  params: { locale: string };}) {  // Strictly server-side loading (not hydrated on the client)  const t = await getTranslations("about");  return (    <main>      <h1>{t("title")}</h1>      <ClientComponent />      <ServerComponent />    </main>  );}

export default {  internationalization: {    locales: ["en", "fr", "es"],    defaultLocale: "en",  },};

import { getHTMLTextDir } from "intlayer";import {  IntlayerClientProvider,  generateStaticParams,  type NextLayoutIntlayer,} from "next-intlayer";export const dynamic = "force-static";const LandingLayout: NextLayoutIntlayer = async ({ children, params }) => {  const { locale } = await params;  return (    <html lang={locale} dir={getHTMLTextDir(locale)}>      <IntlayerClientProvider locale={locale}>        {children}      </IntlayerClientProvider>    </html>  );};export default LandingLayout;

import { PageContent } from "@components/PageContent";import type { NextPageIntlayer } from "next-intlayer";import { IntlayerServerProvider, useIntlayer } from "next-intlayer/server";import { ClientComponent, ServerComponent } from "@components";const LandingPage: NextPageIntlayer = async ({ params }) => {  const { locale } = await params;  const { title } = useIntlayer("about", locale);  return (    <IntlayerServerProvider locale={locale}>      <main>        <h1>{title}</h1>        <ClientComponent />        <ServerComponent />      </main>    </IntlayerServerProvider>  );};export default LandingPage;

Comparison

All three support per-locale content loading and providers.

• With next-intl/next-i18next, you typically load selected messages/namespaces per route and place providers where needed.

• With Intlayer, it adds build-time analysis to infer usage, which can reduce manual wiring and may allow a single root provider.

Choose between explicit control and automation based on team preference.

Usage in a client component

Let's take an example of a client component rendering a counter.

{  "counter": {    "label": "Counter",    "increment": "Increment"  }}

{  "counter": {    "label": "Compteur",    "increment": "Incrémenter"  }}

"use client";import React, { useMemo, useState } from "react";import { useTranslation } from "next-i18next";const ClientComponentExample = () => {  const { t, i18n } = useTranslation("about");  const [count, setCount] = useState(0);  // next-i18next doesn't expose useNumber; use Intl.NumberFormat  const numberFormat = new Intl.NumberFormat(i18n.language);  return (    <div>      <p>{numberFormat.format(count)}</p>      <button        aria-label={t("counter.label")}        onClick={() => setCount((count) => count + 1)}      >        {t("counter.increment")}      </button>    </div>  );};

{  "counter": {    "label": "Counter",    "increment": "Increment"  }}

{  "counter": {    "label": "Compteur",    "increment": "Incrémenter"  }}

"use client";import React, { useState } from "react";import { useTranslations, useFormatter } from "next-intl";const ClientComponentExample = () => {  // Scope directly to the nested object  const t = useTranslations("about.counter");  const format = useFormatter();  const [count, setCount] = useState(0);  return (    <div>      <p>{format.number(count)}</p>      <button        aria-label={t("label")}        onClick={() => setCount((count) => count + 1)}      >        {t("increment")}      </button>    </div>  );};

import { t, type Dictionary } from "intlayer";const counterContent = {  key: "counter",  content: {    label: t({ "en-GB": "Counter", en: "Counter", fr: "Compteur" }),    increment: t({ "en-GB": "Increment", en: "Increment", fr: "Incrémenter" }),  },} satisfies Dictionary;export default counterContent;

"use client";import React, { useState } from "react";import { useNumber, useIntlayer } from "next-intlayer";const ClientComponentExample = () => {  const [count, setCount] = useState(0);  const { label, increment } = useIntlayer("counter"); // returns strings  const { number } = useNumber();  return (    <div>      <p>{number(count)}</p>      <button aria-label={label} onClick={() => setCount((count) => count + 1)}>        {increment}      </button>    </div>  );};

Comparison

• Number formatting

  • next-i18next: no useNumber; use Intl.NumberFormat (or i18next-icu).
  • next-intl: useFormatter().number(value).
  • Intlayer: built-in useNumber().

• Keys

  • Maintain a nested structure (about.counter.label) and scope your hook accordingly (useTranslation("about") + t("counter.label") or useTranslations("about.counter") + t("label")).

• File locations

  • next-i18next expects JSON in public/locales/{lng}/{ns}.json.
  • next-intl is flexible; load messages however you configure.
  • Intlayer stores content in TS/JS dictionaries and resolves by key.

Usage in a server component

We will take the case of a UI component. This component is a server component, and should be able to be inserted as a child of a client component. (page (server component) -> client component -> server component). As this component can be inserted as a child of a client component, it cannot be async.

import type { GetStaticProps } from "next";import { useTranslation } from "next-i18next";type ServerComponentProps = {  count: number;};const ServerComponent = ({ count }: ServerComponentProps) => {  const { t, i18n } = useTranslation("about");  const formatted = new Intl.NumberFormat(i18n.language).format(count);  return (    <div>      <p>{formatted}</p>      <button aria-label={t("counter.label")}>{t("counter.increment")}</button>    </div>  );};

type ServerComponentProps = {  count: number;  t: (key: string) => string;};const ServerComponent = ({ t, count }: ServerComponentProps) => {  const formatted = new Intl.NumberFormat(i18n.language).format(count);  return (    <div>      <p>{formatted}</p>      <button aria-label={t("label")}>{t("increment")}</button>    </div>  );};

import { useIntlayer, useNumber } from "next-intlayer/server";const ServerComponent = ({ count }: { count: number }) => {  const { label, increment } = useIntlayer("counter");  const { number } = useNumber();  return (    <div>      <p>{number(count)}</p>      <button aria-label={label}>{increment}</button>    </div>  );};  );};

Intlayer exposes server-safe hooks via next-intlayer/server. To function, useIntlayer and useNumber use hook-like syntax, similar to the client hooks, but rely under the hood on the server context (IntlayerServerProvider).

Metadata / Sitemap / Robots

Translating content is excellent. However, people often forget that the main goal of internationalisation is to make your website more visible to the world. I18n is an incredible lever to enhance your website's visibility.

Here is a list of best practices regarding multilingual SEO.

• set hreflang meta tags in the <head> tag > This helps search engines to understand which languages are available on the page
• list all page translations in the sitemap.xml using the http://www.w3.org/1999/xhtml XML schema >
• do not forget to exclude prefixed pages from the robots.txt (e.g. /dashboard, and /fr/dashboard, /es/dashboard) >
• use a custom Link component to redirect to the most localised page (e.g. in French <a href="/fr/about">À propos</a>) >

Developers often forget to properly reference their pages across locales.

export const locales = ["en", "fr"] as const;export type Locale = (typeof locales)[number];export const defaultLocale: Locale = "en";export function localizedPath(locale: string, path: string) {  return locale === defaultLocale ? path : "/" + locale + path;}const ORIGIN = "https://example.com";export function abs(locale: string, path: string) {  return ORIGIN + localizedPath(locale, path);}

import type { Metadata } from "next";import { locales, defaultLocale, localizedPath } from "@/i18n.config";export async function generateMetadata({  params,}: {  params: { locale: string };}): Promise<Metadata> {  const { locale } = params;  // Dynamically import the correct JSON file  const messages = (    await import("@/../public/locales/" + locale + "/about.json")  ).default;  const languages = Object.fromEntries(    locales.map((locale) => [locale, localizedPath(locale, "/about")])  );  return {    title: messages.title,    description: messages.description,    alternates: {      canonical: localizedPath(locale, "/about"),      languages: { ...languages, "x-default": "/about" },    },  };}export default async function AboutPage() {  return <h1>About</h1>;}

import type { MetadataRoute } from "next";import { locales, defaultLocale, abs } from "@/i18n.config";export default function sitemap(): MetadataRoute.Sitemap {  const languages = Object.fromEntries(    locales.map((locale) => [locale, abs(locale, "/about")])  );  return [    {      url: abs(defaultLocale, "/about"),      lastModified: new Date(),      changeFrequency: "monthly",      priority: 0.7,      alternates: { languages },    },  ];}

import type { MetadataRoute } from "next";import { locales, defaultLocale, localizedPath } from "@/i18n.config";const ORIGIN = "https://example.com";const expandAllLocales = (path: string) => [  localizedPath(defaultLocale, path),  ...locales    .filter((locale) => locale !== defaultLocale)    .map((locale) => localizedPath(locale, path)),];export default function robots(): MetadataRoute.Robots {  const disallow = [    ...expandAllLocales("/dashboard"),    ...expandAllLocales("/admin"),  ];  return {    rules: { userAgent: "*", allow: ["/"], disallow },    host: ORIGIN,    sitemap: ORIGIN + "/sitemap.xml",  };}

import type { Metadata } from "next";import { locales, defaultLocale } from "@/i18n";import { getTranslations } from "next-intl/server";function localizedPath(locale: string, path: string) {  return locale === defaultLocale ? path : "/" + locale + path;}export async function generateMetadata({  params,}: {  params: { locale: string };}): Promise<Metadata> {  const { locale } = params;  const t = await getTranslations({ locale, namespace: "about" });  const url = "/about";  const languages = Object.fromEntries(    locales.map((locale) => [locale, localizedPath(locale, url)])  );  return {    title: t("title"),    description: t("description"),    alternates: {      canonical: localizedPath(locale, url),      languages: { ...languages, "x-default": url },    },  };}// ... Rest of the page code

import type { MetadataRoute } from "next";import { locales, defaultLocale } from "@/i18n";const origin = "https://example.com";const formatterLocalizedPath = (locale: string, path: string) =>  locale === defaultLocale ? origin + path : origin + "/" + locale + path;export default function sitemap(): MetadataRoute.Sitemap {  const aboutLanguages = Object.fromEntries(    locales.map((l) => [l, formatterLocalizedPath(l, "/about")])  );  return [    {      url: formatterLocalizedPath(defaultLocale, "/about"),      lastModified: new Date(),      changeFrequency: "monthly",      priority: 0.7,      alternates: { languages: aboutLanguages },    },  ];}

import type { MetadataRoute } from "next";import { locales, defaultLocale } from "@/i18n";const origin = "https://example.com";const withAllLocales = (path: string) => [  path,  ...locales    .filter((locale) => locale !== defaultLocale)    .map((locale) => "/" + locale + path),];export default function robots(): MetadataRoute.Robots {  const disallow = [    ...withAllLocales("/dashboard"),    ...withAllLocales("/admin"),  ];  return {    rules: { userAgent: "*", allow: ["/"], disallow },    host: origin,    sitemap: origin + "/sitemap.xml",  };}

import { getIntlayer, getMultilingualUrls } from "intlayer";import type { Metadata } from "next";import type { LocalPromiseParams } from "next-intlayer";export const generateMetadata = async ({  params,}: LocalPromiseParams): Promise<Metadata> => {  const { locale } = await params;  const metadata = getIntlayer("page-metadata", locale);  const multilingualUrls = getMultilingualUrls("/about");  return {    ...metadata,    alternates: {      canonical: multilingualUrls[locale as keyof typeof multilingualUrls],      languages: { ...multilingualUrls, "x-default": "/about" },    },  };};// ... Rest of the page code

import { getMultilingualUrls } from "intlayer";import type { MetadataRoute } from "next";const sitemap = (): MetadataRoute.Sitemap => [  {    url: "https://example.com/about",    alternates: {      languages: { ...getMultilingualUrls("https://example.com/about") },    },  },];

import { getMultilingualUrls } from "intlayer";import type { MetadataRoute } from "next";const getAllMultilingualUrls = (urls: string[]) =>  urls.flatMap((url) => Object.values(getMultilingualUrls(url)) as string[]);const robots = (): MetadataRoute.Robots => ({  rules: {    userAgent: "*",    allow: ["/"],    disallow: getAllMultilingualUrls(["/dashboard"]),  },  host: "https://example.com",  sitemap: "https://example.com/sitemap.xml",});export default robots;

Intlayer provides a getMultilingualUrls function to generate multilingual URLs for your sitemap.

And the winner is…

It’s not simple. Each option has trade-offs. Here’s how I see it:

If you prefer minimal setup and accept some manual wiring, next-intl is a good choice. If you need all the features and don’t mind complexity, next-i18next works. But if you want a modern, scalable, modular solution with built-in tools, Intlayer aims to provide that out of the box.

Alternative for enterprise teams: If you need a well-proven solution that works perfectly with established localisation platforms like Crowdin, Phrase, or other professional translation management systems, consider next-intl or next-i18next for their mature ecosystem and proven integrations.

Future roadmap: Intlayer also plans to develop plugins that work on top of i18next and next-intl solutions. This will give you the advantages of Intlayer for automation, syntax, and content management while keeping the security and stability provided by these established solutions in your application code.

GitHub STARs

GitHub stars are a strong indicator of a project's popularity, community trust, and long-term relevance. While not a direct measure of technical quality, they reflect how many developers find the project useful, follow its progress, and are likely to adopt it. For estimating the value of a project, stars help compare traction across alternatives and provide insights into ecosystem growth.

Conclusion

All three libraries succeed at core localisation. The difference is how much work you must do to achieve a robust, scalable setup in modern Next.js:

• With Intlayer, modular content, strict TS, build-time safety, tree-shaken bundles, and first-class App Router + SEO tooling are defaults, not chores.
• If your team prizes maintainability and speed in a multi-locale, component-driven app, Intlayer offers the most complete experience today.

Refer to 'Why Intlayer?' doc for more details.