Internationalization (i18n) for Next.js
π£ Support for the App Router and Server Components has arrived β
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.
// 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": "{username}'s profile",
"membership": "Member since {memberSince, date, short}",
"followers": "{count, plural, β΅
=0 {No followers yet} β΅
=1 {One follower} β΅
other {# followers} β΅
}"
}
}