> Documentation index: [llms.txt](https://www.i18next.com/llms.txt). Every page is also available as Markdown at its URL plus `.md`.

# 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.

[Get started](https://www.i18next.com/overview/getting-started) [With your agent](https://www.i18next.com/with-your-agent)

`npm install i18next` MIT · 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 })
```

en 3 rye loaves for tomorrow

locales/de/common.json

```
{
  "loaves_one": "Ein Roggenbrot für morgen",
  "loaves_other": "{{count}} Roggenbrote für morgen"
}
```

your code

```
t('loaves', { count: 3 })
```

de 3 Roggenbrote für morgen

## Sites that run i18next

- X
- Eventbrite
- WEF
- NBC News
- GoFundMe
- Elsevier
- BuzzFeed
- IMF
- Freepik
- Xiaomi
- Deezer
- Hootsuite
- NBA
- iHeart
- Strava
- DeepL

i18next runs in the own code of at least **1,188** of the 100,000 most linked websites (Majestic list of 2026-11-17, scan of November 2026; the logos are the first of them by rank, each checked in a browser) · [method](https://www.i18next.com/blog/who-uses-i18next)\
**37.3 million** npm downloads of i18next in the week of 2026-11-15 to 2026-11-21; downloads count installs, CI and agents included, not users · [npm](https://www.npmjs.com/package/i18next)

## 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.

- **React** Apps and SaaS, with `react-i18next`. [Docs](https://www.i18next.com/react)
- **Next** App Router and Pages Router, with `next-i18next` v16. [Docs](https://www.i18next.com/next)
- **Astro** Marketing and content sites, plain i18next at build time. [Docs](https://www.i18next.com/astro)

Also [React Native and Expo](https://www.i18next.com/react/react-native), Node and Deno servers ([i18next-http-middleware](https://github.com/i18next/i18next-http-middleware)), and Vue, Angular, Svelte and more [by the community](https://www.i18next.com/overview/supported-frameworks).

src/Order.jsx

```
import { useTranslation } from 'react-i18next'

export function Order({ count }) {
  const { t } = useTranslation('common')
  return <p>{t('loaves', { count })}</p>
}
```

app/\[lng]/page.tsx

```
import { getT } from '@/i18n.server'  // next-i18next, bound to your config

export default async function Page() {
  const { t } = await getT()
  return <p>{t('loaves', { count: 3 })}</p>
}
```

src/pages/\[lang]/index.astro

```
---
import { getT } from '../../i18n'  // plain i18next, run at build time
const t = getT(Astro.params.lang)
---
<p>{t('loaves', { count: 3 })}</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](https://www.i18next.com/with-your-agent)

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 2011-12-16. Latest release: i18next 27.2.4 on 2026-11-22. (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 2026-11-21, 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 2026-11-22, 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)

## Start in the docs

- [**Getting started** Install i18next, add translations, call `t()`](https://www.i18next.com/overview/getting-started)
- [**i18next** The core library, and where to start](https://www.i18next.com/introduction)
- [**React** `useTranslation`, `Trans`, Suspense](https://www.i18next.com/react)
- [**Next** App Router and Pages Router, `next-i18next` v16](https://www.i18next.com/next)
- [**Astro** Plain i18next at build time, no JavaScript sent](https://www.i18next.com/astro)
- [**More** Vue, Angular, Svelte and other integrations, kept by the community](https://www.i18next.com/overview/supported-frameworks)
- [**CLI** `extract`, `instrument`, `status`](https://www.i18next.com/cli)
- [**Shared i18n syntax** Plurals, context, nesting and formatting in one format](https://www.i18next.com/misc/json-format)

Sponsor

### Locize, from the people who maintain i18next

Locize is our translation management service, and its customers fund the work on i18next. It fits when people who do not write code change the texts, and when every language should be updated in one place.

[Locize with i18next](https://www.locize.com/i18next)
