Your site or app in more languages. Every text in a plain file in your repo.

i18next is the open-source way to make a site or app multilingual: the rules of each language, the same in React, Next, Astro and many other frameworks. Written by you or by your agent, readable by both.

npm install i18nextMIT · since 2011
locales/en/common.json
{
  "loaves_one": "One rye loaf for tomorrow",
  "loaves_other": "{{count}} rye loaves for tomorrow"
}
your code
t('loaves', { count: 3 })

en3 rye loaves for tomorrow

Sites that run i18next

i18next runs in the own code of at least 1,188 of the 100,000 most linked websites (Majestic list of , scan of November 2026; the logos are the first of them by rank, each checked in a browser) · method
37.3 million npm downloads of i18next in the week of to ; downloads count installs, CI and agents included, not users · npm

One solution, the same everywhere

The same library, the same translation files and the same t('key') call in your app, your marketing site and your content site. What you or your agent learned once carries over.

  • ReactApps and SaaS, with react-i18next. Docs
  • NextApp Router and Pages Router, with next-i18next v16. Docs
  • AstroMarketing and content sites, plain i18next at build time. Docs

Also React Native and Expo, Node and Deno servers (i18next-http-middleware), and Vue, Angular, Svelte and more by the community.

src/Order.jsx
import { useTranslation } from 'react-i18next'

export function Order({ count }) {
  const { t } = useTranslation('common')
  return <p>{t('loaves', { count })}</p>
}
locales/de/common.json · the same file in all three
{
  "loaves_one": "Ein Roggenbrot für morgen",
  "loaves_other": "{{count}} Roggenbrote für morgen"
}

How i18next works

Extract
i18next-cli finds texts still written into the code, writes their keys into the files and keeps every language in step with the first. Your agent runs the same commands.
Runtime
In the browser, on the server and at build time, with React, Next, Astro or no framework at all. Plurals, numbers, dates and lists follow the rules of each language (Intl). i18next 27 itself installs no other package.
Structure
One plain JSON file per language and namespace, in your repository. Any editor, any agent and any translation tool can read and change it; your code only knows the key.

With your agent

“Make my bakery’s website available in German and French.”

One sentence to your agent, and the site speaks three languages, with i18next beneath it. A week later the shop assistant, who is from France, rewords the French tagline herself. Read the whole conversation, or the one for an app you already have.

Read the conversation

What your agent finds here

  • Every docs page as Markdown, and llms.txt
  • A prompt for each case, from a new site to texts your client edits
  • An agent skill for setting up i18next
  • i18next-cli to extract keys and check every language in CI

What you can check

Since 2011
Open source under the MIT license since the first commit on . Latest release: i18next 27.2.4 on .GitHub, npm registry · read when this page was built
What i18next ships
i18next 27.2.2 with react-i18next 18.0.3: 17.4 KB gzip, once. Your texts add about 35 bytes each per language: 1,000 texts are about 35 KB for the language a visitor loads. A static Astro site that runs i18next at build time sends no i18next code; its texts are in the HTML.Vite build, measured , script rerunnable
Checked in CI
i18next-cli status exits non-zero when a translation is missing. Run in CI, it stops the build before a missing text goes live.i18next-cli 1.93.2, README
Fixed when disclosed
3 security advisories for i18next in the twelve months up to , each published with the release that fixes it. On the latest release, none of them applies.GitHub security advisories, npm registry · read when this page was built