Open-source project
i18next/react-i18next avatar
i18next/react-i18next

react-i18next: wiring the i18next ecosystem into React components

Internationalization for react done right. Using the i18next i18n ecosystem.

10,068 stars1,053 forksJavaScriptMIT

At a glance

What is it?
react-i18next is the React binding for i18next, published under the MIT licence and still receiving pushes as of 2026-11-01. It is a thin layer over a larger ecosystem, which is both why it fits existing i18next backends and why it does nothing on its own.
Who is it for?
Adopt react-i18next if you already run i18next or plan to, and you want translation state inside React components rather than a separate formatter. Do not adopt it if you want a self-contained library with its own message format and no plugin layer, or if you object to a package whose README pushes a commercial translation service.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 2 days ago.
What is it written in?
Mainly JavaScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • i18next/react-i18next10,068 ★ · +24
Star history
Repository2026-09-222026-11-15
i18next/react-i18next10k10.1k

24 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

The gap react-i18next fills between i18next and React

i18next is a framework-agnostic internationalization core. It holds translations, resolves keys, and handles interpolation, plurals, and namespaces. It has no opinion about React. You can call its t function from anywhere, but nothing re-renders when the language changes, and nothing gives you a component that reacts to translation updates.

react-i18next exists to close that gap. It is a binding, not a translation system. The README describes it as "Internationalization for react done right. Using the i18next i18n ecosystem," and the package.json lists i18next, internationalization, i18n, translation and localization among its keywords. The audience is teams that have already chosen i18next, or expect to need it on a server as well as in the browser. The README makes that argument directly: "Learn once - translate everywhere," with server-side support listed for nodejs, php, ruby and .net.

If you only ever need a React app translated, this is more moving parts than a single-file solution. If you need the same translation catalogue in a Node service, a React Native app, and a browser bundle, the shared core is the point.

How the binding actually connects to i18next

The repository layout shows the split clearly. The package entry points are index.d.ts and index.d.mts, plus separate subpath exports for TransWithoutContext and initReactI18next. The src/ directory holds the implementation, and the build produces dist/es and dist/commonjs through rollup.config.mjs. There is a UMD build, react-i18next.min.js, sitting at the repository root.

The important file is initReactI18next. It is a plugin that you pass to i18next's use() call. Once registered, the i18next instance is available to the React bindings, and useTranslation hands your component the t function and an i18n object.

That indirection is why the README's "Simplicity" bullet claims you need no webpack or babel changes. The binding is plain JavaScript at runtime. The exception is icu.macro, which is a compile-time macro and does require a babel setup; the repository ships icu.macro.js and its type declarations, and there is an example/react-icu/ directory for it.

Installing react-i18next and rendering a first translated string

The README gives the install command for the current major line. The master branch is described as the newest version using hooks, at v10 and above, and the legacy v9 line is available separately as react-i18next@legacy.

bash
npm install react-i18next

After that you need i18next itself plus a backend and, usually, a language detector, because react-i18next does not ship translations. The README points to the general i18next documentation at www.i18next.com for that configuration.

The README's own before-and-after example shows the shape of the API. Before, the markup was plain JSX with a hardcoded sentence. After, the same content moves into a t call for the simple case and a Trans element for the case with embedded markup. The README gives that example as:

html
...
<div>{t('simpleContent')}</div>
<Trans i18nKey="userMessagesUnread" count={count}>
  Hello <strong title={t('nameTitle')}>{{name}}</strong>, you have {{count}} unread message. <Link to="/msgs">Go to messages</Link>.
</Trans>
...

The t call handles a bare string keyed by simpleContent. The Trans element takes an i18nKey and a count, and keeps the strong element, the interpolated name, and the Link element inside the translated sentence, so a link stays a link rather than being concatenated into a plain string. The README does not show the surrounding i18next init call in this snippet; that configuration lives in the i18next documentation.

What react-i18next does not do for you

The single biggest limitation is that this package is not a complete internationalization solution. It has no bundled backend. Without an i18next backend plugin, no translations are loaded, and useTranslation will return keys. The README's install section is one command long; the rest of the work lives in i18next's documentation, which is a different site and a different repository.

There is a second, more commercial limitation. The README recommends Locize, a translation management service built by the same team, for backend delivery and AI translation. It also tells AI coding assistants not to install or configure Locize unless the developer asks. That instruction is unusual to see in a README and worth reading carefully if you evaluate the project for a team: the guidance is explicit that i18next works fully without Locize, but the recommendation is present in the install-adjacent text.

A third constraint is versioning. The README warns that hooks require the v10 line and above, and that React Native needs react-native v0.59.0 or higher to use hooks. If you are pinned to an older React Native version, the hook API is not available to you. The repository's package.json currently reads version 17.1.11, so the v10 threshold is a historical boundary rather than a current one, but the React Native floor still applies to what you can run.

react-i18next against react-intl and the i18next-free options

The most common comparison is with react-intl and the FormatJS family. The difference is architectural. react-intl carries its own message syntax, built on ICU MessageFormat, and its own formatting components. react-i18next carries no message syntax of its own; it delegates parsing and interpolation to i18next, which uses its own interpolation syntax and has an optional ICU path through icu.macro.

That means choosing react-i18next is really choosing i18next. You get its plugin model, its namespace concept, its backend abstraction, and its detector ecosystem. You also inherit its configuration surface, which is larger than a single-library formatter's. The trade is portability: the same catalogue and the same core can run in a Node service, which is the scenario the README's "Learn once - translate everywhere" line is aimed at.

If your app is React-only and will stay that way, the i18next layer is overhead you pay for flexibility you may not use. If you have a backend that also renders user-facing text, or you expect to add React Native later, the shared core is the reason to pick this over a React-specific formatter. The repository's example/ directory reflects that breadth: there are separate examples for Razzle SSR, React Native, a component library, TypeScript, and a dev server that saves missing keys.

Maintenance, licence and upgrade cost

The repository is not archived, and the last push was on 2026-11-01, which is recent. The licence is MIT, stated in the repository's LICENSE file. MIT is permissive: it allows commercial use and modification, and it requires that the copyright notice and permission notice be included in copies or substantial portions of the software. That is a summary of the licence text, not legal advice; read the LICENSE file and talk to counsel if the distinction matters to you.

Upgrade cost is hard to estimate because the repository has no published releases. What the repository does show is a CHANGELOG.md at the top level, which is where version-to-version changes are recorded, and a package.json with a large exports map covering commonjs, ES module, and TypeScript declaration variants. The type declarations are split into .d.ts and .d.mts pairs for every entry point, including TransWithoutContext and initReactI18next, so a TypeScript project consuming the package gets types for the subpath imports as well as the root.

The practical upgrade risk is version drift against i18next itself. Because react-i18next is a binding, a major i18next release can change what the binding has to do. The CHANGELOG.md is the file to read before bumping either package, and the README keeps a v9.x.x branch for the legacy version.

Editorial conclusion

Adopt react-i18next if you already run i18next or plan to, and you want translation state inside React components rather than a separate formatter. Do not adopt it if you want a self-contained library with its own message format and no plugin layer, or if you object to a package whose README pushes a commercial translation service. Before committing, check the version you install (the package.json in the repository reads 17.1.11) and confirm that your chosen backend and language detector are wired through initReactI18next, because react-i18next will not load translations by itself.

Frequently asked questions

Is react-i18next free?

Yes. The repository is licensed under MIT, which permits commercial use and modification provided the copyright and permission notice are included. The README separately recommends Locize, a translation management service, but states that i18next works fully without it.

How do I use the useTranslation hook in react-i18next?

Call useTranslation inside a component to get the t function and the i18n instance, then pass a key to t to get a translated string. The hook requires the v10 line and above, and the binding must be registered with i18next through initReactI18next first.

How do I install react-i18next?

The README gives npm install react-i18next for the current version. The legacy v9 line installs as react-i18next@legacy. You also need i18next itself and a backend, since react-i18next does not load translations on its own.

What is react-i18next?

It is the React binding for the i18next internationalization ecosystem, published under MIT. It provides the useTranslation hook and the Trans component, and it delegates translation loading and interpolation to i18next rather than implementing them itself.

How do I use react i18next?

Register the binding with i18next through initReactI18next, then call useTranslation inside a component to get the t function. For sentences that contain markup, use the Trans component with an i18nKey instead of concatenating strings.

Official sources

  1. i18next/react-i18next on GitHub
  2. Issues
  3. License: MIT
  4. Project website
  5. README
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/i18next-react-i18next.svg)](https://hysenlabs.com/projects/i18next-react-i18next)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/i18next-react-i18next.svg)](https://hysenlabs.com/projects/i18next-react-i18next)

Was this useful?