As you may remember I already did an episode about [localization and internationalization](https://watch-learn.com/making-websites-nextjs-and-strapi/multi-language), but at the time of recording that video Strapi didn’t have options for translating content. So we had to create additional fields in our content type that would serve as translations for original fields.

This is an OK solution if you only have 1 additional language, but imagine that you wanna translate your site or app to five languages. That would mean that you would have 5 additional fields for every translatable field.

Not an elegant soultion by any stretch.

But with version 3.6 of Strapi you get translation options out of the box. And to make things even better Next.js also got **Internationalized Routing** in version 10.


So in this episode we are going to take a look at how these two features play together.

Earth Icon by [Prosymbols](https://www.flaticon.com/authors/prosymbols) from [www.flaticon.com](https://www.flaticon.com/)

In this episode we are going to take look at new internationalization features of both Strapi and Next.js.

Internationalization (i18n)

Now I'm going to show you how to make your Next.js and Strapi site handle multiple languages. We are going to do this by using [next-i18next](https://github.com/isaachinman/next-i18next) plugin that is using [i18next](https://www.i18next.com/) and [react-i18next](https://react.i18next.com/) plugins under the hood.

So I'm going to show you how to handle namespaces, how to use translation strings, how to create a language switcher and how to fake multi language support in Strapi. And at the end of the video our site should have full multilingual support.

In this episode we are going to make our Next.js and Strapi site be multilingual.

Tutorials tagged with: i18n

Get in touch