Support multiple languages, with your app code becoming simpler instead of more complex.
📣 Support for Next.js 13 and the App Router has arrived →import {useTranslations} from 'next-intl';import OnlineStatus from './OnlineStatus'; function UserDetails({user}) { const t = useTranslations('UserDetails'); return ( <section> <h2>{t('title')}</h2> <p>{t('followers', {count: user.followers.length})}</p> <OnlineStatus lastSeen={user.lastSeen} /> </section> );}
{ "UserDetails": { "title": "User details", "followers": "{count, plural, ↵ =0 {No followers yet} ↵ =1 {One follower} ↵ other {# followers} ↵ }",
Localize your messages with interpolation, plurals, ordinal pluralization, enum-based label selection and rich text.
// "Feb 28, 2023"format.dateTime(lastSeen, 'medium'); // "2 hours ago"format.relativeTime(lastSeen); // "$1,499.90"format.number(1499.9, {style: 'currency', currency: 'USD'});
Apply appropriate formatting without worrying about server/client differences like time zones.
function UserDetails({user}) { const t = useTranslations('UserDetails'); return ( <section> <h2>{t(''titlefollowers)}</h2> </section> );}
Speed up development with autocompletion for message keys and catch typos early with compile-time checks.
const t = useTranslations('UserDetails'); t('followers', {count: user.followers.length}); // stringt.rich('bio', {b: (chunks) => <b>{chunks}</b>}); // ReactNode const format = useFormatter();const timeZone = useTimeZone();const locale = useLocale();const now = useNow();
Learn a single API that can be used across your code base to turn translations into plain strings or rich text.
$ next build Route Size First load JS┌ ● / 637 B 90.1 kB├ ● /about 512 B 92.5 kB└ ● /contact 931 B 91.2 kB ● (SSG) automatically generated as static HTML + JSON
Get the best performance from your app by supporting internationalization on both static and dynamic pages.
Intl.LocaleIntl.DateTimeFormatIntl.NumberFormatIntl.PluralRulesIntl.RelativeTimeFormatIntl.ListFormat IntlMessageformat
Use the best parts of built-in JavaScript APIs and the battle-tested ICU parser from Format.JS.
Founder & CEO of Daybridge
“We were initially worried that adding support for multiple languages to our app would add overwhelming complexity, but next-intl genuinely made the process so much smoother than we expected.”
Co-founder & CEO of Clerk
“Interop with next-intl was a design requirement”
Using next-intl too? Let us know!