DocsDocsExamplesExamplesBlogBlog
GitHubGitHub (opens in a new tab)
    • Welcome!
    • App Router (Client Components)
    • App Router (Server Components)
    • Pages Router
    • Start
    • Messages
    • Numbers
    • Dates and times
    • Lists
  • Configuration
    • Start
    • Server & Client Components
    • Metadata & Route Handlers
    • Core library
    • Start
    • Middleware
    • Navigation
  • TypeScript integration
    • Checklist
    • Runtime requirements & polyfills
  • FAQ
  • Localization management with Crowdin
      • Welcome!
      • App Router (Client Components)
      • App Router (Server Components)
      • Pages Router
      • Start
      • Messages
      • Numbers
      • Dates and times
      • Lists
    • Configuration
      • Start
      • Server & Client Components
      • Metadata & Route Handlers
      • Core library
      • Start
      • Middleware
      • Navigation
    • TypeScript integration
      • Checklist
      • Runtime requirements & polyfills
    • FAQ
    • Localization management with Crowdin
    • App Router
    • Pages Router
    • Pages Router (advanced)
    • next-intl blog

Presented by

Crowdin logo
Question? Give us feedback → (opens in a new tab)Edit this page
Docs
Routing
Start

Internationalized routing

With the introduction of the App Router, Next.js no longer provides integrated i18n routing. To fill in the gap, next-intl provides the two necessary pieces:

Internationalized routing middleware→Navigation APIs→
Core libraryMiddleware

Docs

 · 

Examples

 · 

Blog

GitHub

 · 

Hosted onVercel