Support multiple languages, with your app code becoming simpler instead of more complex.
📣 Support for Server Components has arrived →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> );}
{ "UserProfile": { "title": "{firstName}'s profile", "followers": "{count, plural, ↵ =0 {No followers yet} ↵ =1 {One follower} ↵ other {# followers} ↵ }"
Localize your messages with interpolation, cardinal & ordinal plurals, 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 UserProfile({user}) { const t = useTranslations('UserProfile'); return ( <section> <h1>{t(''titlefollowers)}</h1> </section> );}
Speed up development with autocompletion for message keys and catch typos early with compile-time checks.
const t = useTranslations('UserProfile'); 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┌ ● / 1.4 kB 87.6 kB├ ● /about 205 B 86.2 kB└ λ /[username] 3.24 kB 89.3 kB ● (SSG) automatically generated as static HTML + JSON
App Router, Server Components, static rendering—pick the right tool for the right job, next-intl works everywhere.
/en/blog/es/blog/de/blog /en/about-us/es/sobre-nosotros/de/ueber-uns
Provide unique pathnames per language and optionally localize pathnames for search engine optimization.
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!