i18next is not only one of the top open source internationalization frameworks,
it's a complete ecosystem that helps you to localize your product from web to mobile and desktop.
i18next was created in late 2011. It's older than most of the libraries you will use nowadays, including your main frontend tech (React, Angular, Vue, ...).
Based on how long i18next already is available open source, there is no real i18n case that could not be solved with i18next.
There is a plenty of features and possibilities you'll get with i18next compared to other regular i18n frameworks.
Here you can find more information about why i18next is special.
At first, i18next seems to be a simple key/translation dictionary, but in reality it is an elaborated and very extensible i18n framework with a lot of power.
It offers translations to be provided from different sources, a language detection, plural form resolutions, caching, post processing, alternative i18n formats and more. You see it does not only offer the standard i18n features, like interpolation, formatting, etc.
But the best thing about it is certainly the limitless ecosystem around i18next. We don't know of any other i18n framework with such a large community.
That's why we like i18next that much!
With using locize you directly support the future of i18next.
The i18next community provided us with great feedback. Out of that response and our own experiences we learnt providing instrumentation for doing proper internationalization just is not enough.
Helping developers to get their applications translated is great - but there is more to it.
Having created the foundation with i18next it was a long journey to localization as a service.
Then the locize integration will be a breeze and you will manage your translation files with ease.
Here you can find a step by step guide, which will unleash the full power of i18next in combination with locize.
See how your developer experience with this localization workflow could look like.
There's also the possibility to have an even more focused developer experience, with the help of the auto-machinetranslation workflow and the use of the save missing keys functionality, new keys not only gets added to locize automatically, while developing the app, but are also automatically translated into the target languages using machine translation (like Google Translate).
Check out this tutorial blog post: "How to properly internationalize a React application using i18next"
Here you can find an example with different approaches and a blog post explaining this.
Or this blog post, if you're using Next.js 13 with app directory.
Here you can find a simple example and a step by step tutorial.
Here you can find an example and an appropriate blog post.
Use the locizify script, like shown in this video.
In this tutorial blog post you can check out how this works.
And in this tutorial blog post you can see it working also in Deno.
Check out this blog post.
Check out this blog post.
Here you can check if there is a supported i18next framework for you.
If there is none suitable for your needs, there's always the possibility to directly integrate the locize API on your own.
Get any questions you may have about our pricing or platform answered by one of our team members.Contact us!