The Translation Management for i18next and any other i18n setup

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.

Why i18next?


Sustainability

I18next was created in late 2011. It's older than most of the libraries you will use nowadays, including your main frontend tech (react, vue, ...).

Maturity

Based on how long i18next already is available open source, there is no real i18n case that could not be solved with i18next.

Extensibility

i18next can be used in any javascript (and a few non-javascript - .net, elm, iOS, android, ruby, ...) environment, with any UI framework, with any i18n format, ... the possibilities are endless.

Richness

There is a plenty of features and possibilities you'll get with i18next compared to other regular 18n frameworks.

Here you can find more information about why i18next is special.

We love open source

With using locize you directly support the future of i18next.


The creators of i18next are also the founders of locize

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.

  • How do you integrate any translation services / agency?
  • How do you keep track of new or removed content?
  • How you handle proper versioning?
  • How 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.


locize is the perfect translation management tool for your i18next project

➡️ i18next + locize = true continuous localization

Already using i18next?

Then the locize integration will be a breeze and you will manage your translation files with ease.


Just use i18next-locize-backend as i18next backend

import i18next from 'i18next';
import Backend from 'i18next-locize-backend';
 
i18next
  .use(Backend)
  .init({
    // ...other options
    backend: {
      projectId: '[PROJECT_ID]',
      apiKey: '[API_KEY]',
      referenceLng: '[LNG]'
    }
  });

Are you using React?

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

Using React, but new to i18next?

Check out this tutorial blog post: "How to properly internationalize a React application using i18next"

Are you using Next.js?

Here you can find an example with 2 different approaches.

Are you using a different technology?

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.

Need some assistance?

Get any questions you may have about our pricing or platform answered by one of our team members.

Contact us!