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.

ai localization

We love open source

locize is the official sponsor of i18next. With using locize you directly support the future of i18next.

Why Choose Item Icon
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, Angular, Vue, ...).

Why Choose Item Icon
Maturity

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

Why Choose Item Icon
Extensiblity

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.

Why Choose Item Icon
Richness

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
open link

How does i18next work?

How does i18next work? i18next architecture

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!

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.

- Easy to integrate
- Continuous deployment?
- Continuous localization with a CDN!
- Manage the translation files with ease
- Order professional translations
- Analytics & Statistics
- Profit from our content delivery network
- Versioning of your translations
- Automatic and On-Demand Machine Translation
- Riskfree: Take your data with you
- Transparent and fair pricing and a lot more...

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.

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]'
    }
  });

Which technology are you using

01
Are you using React?
+
02
Using React, but new to i18next?
+
03
Are you using Next.js?
+
04
Are you using Remix?
+
05
Are you using Gatsby?
+
06
Are you using i18nextify?
+
07
It works also on server side, like Node.js or Deno
+
08
Are you using Vue.js?
+
08
Are you still using jQuery?
+
09
Are you using a different technology?
+