Internationalization for Next.js.

Internationalization (i18n) is an essential part of the user experience, therefore next-intl gives you all the parts you need to get language nuances right.

• 🌟 ICU message syntax: Localize your messages with interpolation, cardinal & ordinal plurals, enum-based label selection and rich text.
• 📅 Dates, times & numbers: Apply appropriate formatting without worrying about server/client differences like time zones.
• ✅ Type-safe: Speed up development with autocompletion for message keys and catch typos early with compile-time checks.
• 💡 Hooks-based API: Learn a single API that can be used across your code base to turn translations into plain strings or rich text.
• 🚀 Next.js-native and performance-obsessed: App Router, Server Components, static rendering—pick the right tool for the right job, next-intl works everywhere.
• 🌍 Internationalized routing: Provide unique pathnames per language and optionally localize pathnames for search engine optimization.

→ Read the docs

// UserProfile.tsx
import {useTranslations} from 'next-intl';

export default function UserProfile({user}) {
  const t = useTranslations('UserProfile');

  return (
    <section>
      <h1>{t('title', {firstName: user.firstName})}</h1>
      <p>{t('membership', {memberSince: user.memberSince})}</p>
      <p>{t('followers', {count: user.numFollowers})}</p>
    </section>
  );
}

// en.json
{
  "UserProfile": {
    "title": "{firstName}'s profile",
    "membership": "Member since {memberSince, date, short}",
    "followers": "{count, plural, ↵
                    =0 {No followers yet} ↵
                    =1 {One follower} ↵
                    other {# followers} ↵
                  }"
  }
}

As an app grows, messages may drift and become inconsistent.

A companion tool, eloqnt/cli, catches this by analyzing your source code and messages statically:

$ eloqnt lint

messages/de.json
│
│  "UserProfile.title": "Dein Profil"
│                        ─┬──────────
│                         ╰─ Inconsistent ICU arguments: missing {firstName} (inconsistent-args)
│
│  "UserProfile.membership": "Member since {memberSince, date, short}"
│  ─┬──────────────────────
│   ╰─ Missing translation for de (missing-translation)

✗ 1 error
! 1 warning

→ Rule details: https://cli.eloqnt.dev/docs/lint-rules/<rule>
→ Run `eloqnt translate` to fill in 1 missing translation

It can optionally also fill in missing translations with eloqnt translate, using your source code as context.

Hosted on Vercel