How to improve your project with multilingual capabilities

How to unlock multilingual capabilities of your React website

At first, we create our app in English. We face adding multilingual support when the project grows or needs to serve people from countries that have multiple official languages. How can you tackle this with React and headless CMS?

Ivan KiráľPublished on Sep 6, 2022

You started small – you have a headless CMS as your content hub and your React website as a single channel. As time passed, you found out that you needed more channels and languages to reach new markets and be more accessible. This article will help you set up your React site to be multilingual.

Project Overview

The application we will create will use React in combination with Typescript. I recommend using Create React App with a Typescript template as it sets up some of the dependencies automatically. If you want to do it manually, bear in mind we’ll use React hooks and, therefore, in React in at least version of 16.8. We will also need the following libraries to manage the React application successfully: 

npm i @kontent-ai/delivery-sdk react-router-dom@6 react-intl  universal-cookie --save
npm i @kontent-ai/backup-manager@4.1.0 -g

If you are already familiar with React Router, the new version comes with a few changes, such as that routes are selected based on the best match instead of being traversed in order. For a detailed change log, see React Router | Upgrading from v5.

Using headless content storage

In the example, we’ll fetch content from the headless CMS It should contain a couple of movies and also some other pages such as About us and Home. Our project will be a simple app consisting of a few pages – Home, About, Movies, and Movie detail. The URLs will be analogical except for the Home page whose URL will be simple "/" and Movie, which we will identify as /movies/:codename.

The URL structure will slightly change when we add another language. The most typical approach is to use language prefixes, so our URLs will then look like this: /en/about-us. Before we continue, create a new project in and note the project ID and Management API key from the project settings.

Next, import the following .zip file with the help of Backup Manager using the following command: 

kbm --action=restore --apiKey=xxx --projectId=xxx --zipFilename=backupFile

You can download the zip via this link.

After the import finishes, you should see the content items in your project.

Note: Acknowledge that your language prefixes should be the same as the localization codenames of your project.

Add a new language to content

Let’s start with adding a new language to our content. In, head to the Project Settings and  Localization. Add a new language and set fallback to the default language. I added a new language and called it sk. I also have changed the name and codename of the default language to en to keep language prefixes and codenames intact. Now you are ready to create new language variants of your content items. It’s common that some content items don’t have language variants in all languages. For those cases, features language fallbacks that deliver language variants of other languages in a defined order. Find out more here.

React application

Now we are ready to start working on our React application. Let’s see how our application will be structured:

- src
| - components
  | - LocalizedApp.tsx
| - localization
  | - en.json
  | - sk.json
| - utils
  | - clients.ts
| - views
  | - Home.tsx
  | - About.tsx
  | - Movies.tsx
  | - Movie.tsx
- App.tsx
- index.tsx

Fetching content from the CMS

To obtain data from, we will use the Delivery SDK. For starters, we will initialize a client which will be used for querying data. Create a /utils folder, and inside it, create a client.ts file with the code below. Remember to replace <YOUR_PROJECT_ID> with your actual project ID that you can find in Project settings in

import {createDeliveryClient} from "@kentico/kontent-delivery";

export const deliveryClient = createDeliveryClient({
    projectId: <YOUR_PROJECT_ID>

Prepare our local content 

Apart from fetching our content from, for some texts, it’s more beneficial to store them locally. It is typical for the data you want to have always ready and don’t want to wait till they are fetched. One of the cases for this scenario is navigation link titles which we’ll keep in JSON files – en.json and sk.json. Keep in mind that React Intl support only key:value hierarchy, meaning you can’t use nested objects. Although, you might use a separator such as '_' to give your labels a taste of hierarchy:

// en.json
"header_home_link_title": "Home",
"header_about_link_title": "About us",
"header_movies_link_title": "Movies"

// sk.json
"header_home_link_title": "Domov",
"header_about_link_title": "O nas",
"header_movies_link_title": "Filmy"

Initialize routing

Now the fun begins! Firstly, we will add support for routing in the index.tsx which you can find at the top level of our files structure. As mentioned before, we support multilanguage routes using prefixes, therefore every route that has one of our supported languages in route in format /en/... should navigate us to a component LocalizedApp which is a semi-step that gets us to the application which will view our pages. The plain URL / will navigate us to the language prefix stored in cookies. If no cookie for language is set yet, then it will use the English language by default. Every other route will fall under the 404 page.

const cookies = new Cookies(document.cookie);
const lang = cookies.get('lang') ?? 'en';

                {["en", "sk"].map((value) => (
                        element={<LocalizedApp lang={value} />}
                <Route path="/" element={<Navigate to={`/${lang.toLowerCase()}`} />} />
                <Route path="*" element={<Navigate to={`/${lang.toLowerCase()}/404`} />} />


Initializing React Intl in LocalizedApp

Our next challenge is to tell components which language is currently being used. We will use the React Intl IntlProvider component for that. Let’s create a /LocalizedApp.tsx component, which will wrap our app in IntlProvider. This allows every component of the app to access the necessary data – locale, defaultLocale, and messages. In the previous code file, we have already passed a lang variable to our new component LocalizedApp. We can now obtain it and pass it to IntlProvider also with messages from the JSON file and the default language option. In the useEffect block, we will save our current language into a cookie to make it available for subsequent requests. 

import messages_en from "../localization/en.json";
import messages_sk from "../localization/sk.json";

export const messages: { [index: string]: any } = {
    'en': messages_en,
    'sk': messages_sk

interface LocalizedAppProps{
    lang: string

export const LocalizedApp: React.FC<LocalizedAppProps> = ({lang}) => {
    const cookies = useMemo(() => new Cookies(document.cookie), []);

    useEffect(() => {
        cookies.set('lang', lang, { path: '/' });
    }, [lang, cookies])

    return (

Routing and local translations of our app

Great job there! Now we can create links and routes to navigate users around. Let’s look at our simple navigation header first in app.tsx. We get access to formatMessage function via useIntl() hook. Then we use this function to tell React Intl to translate our link titles. It automatically takes provided JSON file from IntlProvider and gives us the right text according to the specified id. Then we specify the routes that our app can navigate through. Notice that the Route for the Movie component consists of /movies/:codename. The suffix tells us that there is a variable codename, which can be then obtained via hook from the URL.

function App() {
    const { formatMessage } = useIntl();

  return (
    <div className="App">
                <Link to={``}>{formatMessage({id:"Header.homeLinkTitle"})}</Link>
              <Link to={`${formatMessage({id:"Routing.about-us"})}`}>{formatMessage({id:"Header.aboutLinkTitle"})}</Link>
              <Link to={`movies`}>{formatMessage({id:"Header.movieLinkTitle"})}</Link>

                <Route path="" element={<Home />} />
                <Route path="/about-us" element={<About />} />
                <Route path="/movies" element={<Movies />} />
                <Route path={"/movies/:codename"} element={<Movie />} />
                <Route path={"*"} element={<Navigate to={"/404"} />}/>
                <Route path="404" element={<NotFound />}/>

Fetching translated content from

Now it’s time to fetch data from and display it. We will first process the movie component. Let’s create a /views folder and a /views/Movie.tsx file inside it. Firstly, we define a Movie type according to our content type in We obtain our locale via useIntl() and the codename of the movie via useParams() hook, which lets us obtain data from the URL. Then, we prepare a function that uses our previously defined delivery client to fetch a movie with the given codename. We also need to provide a language parameter, so that the CMS knows which language version we want. For that, we use .languageParameter(locale). Then we call the function inside of useEffect, so it is executed anytime the codename or locale gets changed. Lastly, we can easily render our data in the return function.
export type Movie = IContentItem<{
    title: Elements.TextElement;
    description: Elements.TextElement;

export const Movie: React.FC = () => {
    const [movie, setMovie] = useState<Movie|undefined>();
    const { locale } = useIntl();
    const { codename } = useParams();

    useEffect(() => {
        getMovie().then(val => {
    }, [codename, locale])

    const getMovie = async () => {
        if (codename === undefined){
        return await deliveryClient.item<Movie>(codename).languageParameter(locale).toPromise();


Note: Analogically, you can create all the other views.

Handling 404

To handle 404 errors, it might seem like a good idea to have one /404 page for all languages. In our example, we decided to go in a way that every language has its own route – e.g., /en/404. The reason is that it’s better for SEO as it is recommended to use different URLs for different languages. 

To sum up...

We created a new sample app and installed the necessary dependencies for internationalization and content fetching. We adjusted the implementation to support multiple languages, used the delivery SDK to fetch appropriate content, and finally added multiple 404 pages to handle non-existing pages. We have discussed how to make a basic react app with routing and multilanguage support using If you are more interested in, you can check React Sample App that can show you more of the integration between React and

Written by

Ivan Kiráľ

As a developer advocate, I take care of the developer community. I learn new technologies and apply my knowledge in our open source projects.

More articles from Ivan

Feeling like your brand’s content is getting lost in the noise?

Listen to our new podcast for practical tips, tricks, and strategies to make your content shine. From AI’s magic touch to content management mastery and customer experience secrets, we’ll cover it all.

Listen now
Kontent Waves