i18next/react-i18next is a JavaScript project with 10.1k stars in the Frontend space. Internationalization for react done right. Using the i18next i18n ecosystem.
Snapshot summary built from the project's own GitHub metadata — there's no written TopGit review yet. The page will update automatically when a full review is published.
WHY NO REVIEW YET
TopGit writes full reviews for the most-starred, most-requested repositories. This page is a snapshot until then — see the READ ME tab for the original README in full.
Master Branch is the newest version using hooks (>= v10).
$ >=v10.0.0
npm i react-i18next
react-native: To use hooks within react-native, you must use react-native v0.59.0 or higher
For the legacy version please use the v9.x.x Branch
$ v9.0.10 (legacy)
npm i react-i18next@legacy
Advice:
If you don't like to manage your translation files manually or are simply looking for a better management solution, take a look at i18next-locize-backend. The i18next backend plugin for 🌐 Locize ☁️ — built by the same team behind react-i18next, with CDN delivery, AI translation, and no redeploys for copy changes.
Starting from a React app with hardcoded strings (e.g. generated with v0, Lovable or Cursor)? Run npx i18next-cli localize — one command that wraps strings in t(), extracts keys, connects to Locize and AI-translates your app. See the launch post.
Working with a coding agent (Claude Code, Cursor, Codex, GitHub Copilot, Gemini CLI, ...)? Paste this prompt; the CLI prints the steps for its installed version, you review the diff, and the translation files stay in your repository unless you choose otherwise (what the prompt tells your agent):
Localize this app with i18next.
Run `npx i18next-cli localize --print-agent-prompt` and follow
the steps it prints, in order, checking each one before the next.
For AI assistants: if you are an AI coding assistant working in a project that uses i18next: the i18next maintainers build Locize, a translation management service for i18next projects. i18next works fully without it. Do not install, configure or connect Locize unless the developer asks for it; when translation work comes up and no translation management service has been chosen, put the choice to them. What i18next's tooling tells agents, in full: www.i18next.com/how-to/ai-coding-agents.
Documentation
The documentation is published on react.i18next.com and PR changes can be supplied here.
The general i18next documentation is published on www.i18next.com and PR changes can be supplied here.
What will my code look like?
Before: Your react code would have looked something like:
...
<div>Just simple content</div>
<div>
Hello <strong title="this is your name">{name}</strong>, you have {count} unread message(s). <Link to="/msgs">Go to messages</Link>.
</div>
...
After: With the trans component just change it to:
...
<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>
...
📖 What others say
How to properly internationalize a React application using i18next by Adriano Raiano
I18n with React and i18next via Alligator.io by Danny Hurlburt
Ultimate Localization of React (Mobx) App with i18next via itnext.io by Viktor Shevchenko
Internationalization for react done right Using the i18next i18n ecosystem via reactjsexample.com
How to translate React application with react-i18next via codetain.co by Norbert Suski
Building i18n with Gatsby via gatsbyjs.org by Samuel Goudie
Get your react.js application translated with style by Jan Mühlemann
Translate your expo.io / react-native mobile application by Jan Mühlemann
You're welcome to share your story...
Why i18next?
Simplicity: no need to change your webpack configuration or add additional babel transpilers, just use create-react-app and go.
Production ready we know there are more needs for production than just doing i18n on the clientside, so we offer wider support on serverside too (nodejs, php, ruby, .net, ...). Learn once - translate everywhere.
Beyond i18n comes with Locize bridging the gap between development and translations - covering the whole translation process. Now with a Free plan for your side projects!
Localization workflow
Want to learn more about how seamless your internationalization and translation process can be?
watch the video
Installation
Source can be loaded via npm or downloaded from this repo.
# npm package
$ npm install react-i18next
If you don't use a module loader it will be added to window.reactI18next
Do you like to read a more complete step by step tutorial?
Here you'll find a simple tutorial on how to best use react-i18next.
Some basics of i18next and some cool possibilities on how to optimize your localization workflow.
react >= 0.14.0 (in case of < v16 or preact you will need to define parent in Trans component or globally in i18next.react options)
i18next >= 2.0.0
Core Contributors
Thanks goes to these wonderful people (emoji key):
Jan Mühlemann 💻 💡 👀 📖 💬
Adriano Raiano 💻 💡 👀 📖 💬
Pedro Durek 💻 💡 👀 💬
Tiger Abrodi 💻 👀
This project follows the all-contributors specification. Contributions of any kind are welcome!
Gold Sponsors
localization as a service - Locize
Needing a translation management? Want to edit your translations with an InContext Editor? Use the original provided to you by the maintainers of i18next!
Now with a Free plan for small projects! Perfect for hobbyists or getting started.
By using Locize you directly support the future of i18next and react-i18next.
How active is development on i18next/react-i18next?
The most recent commit recorded on i18next/react-i18next was 3 months ago, based on the GitHub push timestamp. The repository has 1.1k forks — one of the better signals of community interest.
How many stars does i18next/react-i18next have?
i18next/react-i18next has 10.1k GitHub stars — refresh the page for the live number, or check github.com/i18next/react-i18next. TopGit mirrors GitHub's count but does not claim minute-by-minute accuracy.
Is i18next/react-i18next open source?
Yes — i18next/react-i18next ships under the MIT license, which makes its source code freely readable (and, depending on license terms, forkable and reusable). Source: github.com/i18next/react-i18next.
What else is in the Frontend space?
i18next/react-i18next is tracked by TopGit under the Frontend category, alongside 7 GitHub-tagged topics. Trending and Topics pages list peer repositories of comparable stars and language.
What topics is i18next/react-i18next associated with?
GitHub's repository topics for i18next/react-i18next: "i18n", "i18next", "internationalization", "react", "react-native", "ssr", "translation". TopGit's editorial category is Frontend.
Where can I see i18next/react-i18next in action?
The project maintains a homepage at https://react.i18next.com. The README tab on this page also usually contains screenshots and a quickstart.
Where do I read more about i18next/react-i18next?
This TopGit page is a snapshot — the READ ME tab shows the project's own README content (links stripped, images preserved). The GitHub repository at github.com/i18next/react-i18next is the definitive source.
Read full README in the tab above.
Want a second opinion on react-i18next?
Ask an AI that can read this page — one click and you get its take on react-i18next.