The history of i18next

How all began - back in 2011

All started back in 2011 when we were in search for an internationalization library that meets our demand - allowing to run both on server side Node.js and on our client side single page applications.

I18next was born and fastly grown to one of the most used frameworks for translating web applications and in Node.js. The response of the community was amazing and a fast growing ecosystem established itself around i18next.


With v2 of i18next, released in 2015, we completely rebuild i18next to be as extensible as possible.

Since v1 all newer releases can be dropped in as a replacement for v1 by just adding a minimal compatibility layer. The v1 API is still actively tested, here.

Shortly after the i18next v2 release in 2015, another big community driven i18next extension was released: react-i18next.

Internationalization (i18n) is not enough

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

  • How do you integrate any translation services / agencies?

  • How do you keep track of new or removed content?

  • How do you handle proper versioning?

  • How do you deploy translation changes without deploying your complete application?

  • and a lot more...

locize to the rescue

Having created the foundation with i18next it was a long journey to localization as a service.

🙏 The best way to directly support the future of i18next is to use locize. 💙

<<We aim to simplify localization, making it an efficient process that aligns with the ever-evolving demands of the modern business landscape.>> read the full interview.

Last updated