Multi-language
JSON file

Multi-language JSON is a file format which contains translation strings for multiple languages. Save time on managing content by yourself.

Upload JSON file
Free 14-day trial, No credit card required, Easy setup
web translation editor

What is multi-language JSON?

Multi-language JSON is one of the most common JSON formats for web applications and software localization programs. It contains translations for many languages, where the first level JSON is a language key or locale. For example, for English, Polish, and German it would contain keys: en_US, pl_PL, de_DE. Each of the language keys contains an object with key-values, where the key is usually a translation key and the values are translations for the corresponding language. A sample file is shown below:

{
  "de_DE": {
    "SALE": "Verkauf",
    "ADDRESS": "Adresse"
  },
  "en_US": {
    "SALE": "Sale",
    "ADDRESS": "Address"
  },
  "pl_PL": {
    "SALE": "Sprzedaż",
    "ADDRESS": "Adres"
  }
}

In some cases, multi-language JSON files can contain additional levels of translation keys, but the rule of thumb is that the first level always contains locales or languages.

{
  "de_DE": {
    "navbar": {
      "title": "Titel",
      "home": "Startseite"
    }
  },
  "en_US": {
    "navbar": {
      "title": "Title",
      "home": "Homepage"
    }
  },
  "pl_PL": {
    "navbar": {
      "title": "Tytuł",
      "home": "Strona główna"
    }
  }
}

When to use multi-language JSON?

Multi-language JSON format is a very elegant way of keeping translations because it's only one file with all translations for all languages. It's commonly used in applications where the translations are loaded once and kept in application memory, or in an application that works on server-side. Thanks to that, client (end-user) never downloads the whole file. The server application returns only a subset of content to the user.

Client-side applications built with ReactJS or VueJS without any additional frameworks like NextJS or NuxtJS usually uses more sophisticated approaches to download translations to the client. One of the ways is to split translations into a multiple files by language.

No matter which type of application you need to translate, you have two options to access translations. One is to host translations on CDN, which offers fast access to translations for your end-users and option to change translations without re-deploying your application.The second option is to include translations with your project bundle, by downloading translations files locally and add them to the application package.

What is translation hosting?

translation hosting process

SimpleLocalize offers a translation hosting service that splits localization files automatically and upload them to the fast server, from which every end-user can freely download translations just for his language. A more sophisticated solution is to split translations even more and use only required translations for certain website. In such case, translations are additionally split by translation namespaces and loaded automatically by i18n plugin.

How to manage translation files locally?

SimpleLocalize also offers an option to upload and download translations thanks to open-source CLI which can be installed on any machine with any operating system including CI/CD sever machines.

Install SimpleLocalize CLI or download it manually.

$ curl -s https://get.simplelocalize.io/2.0/install | bash

Upload your translation files using upload command

$ simplelocalize upload \
        --apiKey YOUR_PROJECT_API_KEY \
        --uploadFormat multi-language-json \
        --uploadPath ./locales/translations.json

After adding new languages or changing translation strings, you can download translation files again to your project files by invoking download command with parameters like below

$ simplelocalize download \
        --apiKey YOUR_PROJECT_API_KEY \
        --uploadFormat multi-language-json \
        --uploadPath ./locales/translations.json

Need help? See our documentation page.

  • Multi Language JSON
  • Android
  • Jekyll
  • FormatJS
  • Webhooks
  • Laravel
  • Zapier
  • Expo
  • Yaml file
  • Vue
  • Slack
  • Localizable strings
  • TypeScript
  • GatsbyJS
  • Angular
  • PHP Array
  • Spring Boot
  • iOS
  • FormatJS CLI
  • CSV file
  • Ionic
  • SimpleLocalize JSON
  • next-translate
  • FormatJS CLI
  • Cordova
  • React
  • PO/POT file
  • NodeJS
  • macOS
  • JavaScript
  • Google Translate
  • Resource XML
  • Excel
  • i18next
  • Kotlin language
  • Single Language JSON
  • next-i18next
  • Unity
  • Module exports
  • Swift language
  • GitHub
  • [object Object]
  • React Native
  • Excel file
  • Java language
  • Java Properties
  • Expo
  • Multi Language JSON
  • Yaml file
  • GitHub
  • Kotlin language
  • Angular
  • Webhooks
  • Excel
  • Vue
  • Spring Boot
  • Single Language JSON
  • i18next
  • Excel file
  • iOS
  • Localizable strings
  • NodeJS
  • TypeScript
  • Ionic
  • Resource XML
  • next-i18next
  • next-translate
  • Laravel
  • Google Translate
  • PHP Array
  • SimpleLocalize JSON
  • Java language
  • Zapier
  • FormatJS CLI
  • GatsbyJS
  • CSV file
  • Swift language
  • [object Object]
  • React Native
  • Unity
  • Java Properties
  • FormatJS
  • Cordova
  • Jekyll
  • JavaScript
  • Module exports
  • macOS
  • Slack
  • PO/POT file
  • Android
  • FormatJS CLI
  • React
  • Kotlin language
  • i18next
  • GitHub
  • Jekyll
  • Unity
  • macOS
  • Java language
  • Google Translate
  • Java Properties
  • JavaScript
  • Yaml file
  • Laravel
  • React
  • Spring Boot
  • Multi Language JSON
  • Slack
  • PO/POT file
  • Android
  • PHP Array
  • FormatJS CLI
  • TypeScript
  • Expo
  • CSV file
  • [object Object]
  • SimpleLocalize JSON
  • Zapier
  • NodeJS
  • next-translate
  • iOS
  • Swift language
  • GatsbyJS
  • Angular
  • Excel file
  • Single Language JSON
  • FormatJS
  • Vue
  • Resource XML
  • Webhooks
  • Localizable strings
  • React Native
  • FormatJS CLI
  • Excel
  • Ionic
  • next-i18next
  • Module exports
  • Cordova

Integrated with your favourite tools

Have you already integrated an i18n library? We got good news! You can connect SimpleLocalize without doing any changes in the application code! We don't bound you with our own 'yet another i18n library'.

Browse integrations
Ready to say

Greet your customers in their mother language

Start 14-day trialNo credit card required
waves

Resources

Java 19: Internationalization

Java 19: Internationalization

Jakub PomykałabyJakubNovember 19, 2022

Learn how to implement internationalization in your Java application. This tutorial will show you how to use Spring Boot to create a simple application with messages.properties.

Continue reading
Spring Boot 3.0: Internationalization

Spring Boot 3.0: Internationalization

Jakub PomykałabyJakubNovember 18, 2022

Learn how to implement internationalization in your Spring Boot application. This tutorial will show you how to use Spring Boot to create a simple application with messages.properties.

Continue reading
What is CORS?

What is CORS?

Jakub PomykałabyJakubOctober 04, 2022

Article explains what is CORS, popular among web developers CORS, what are the common problems and how to fix them.

Continue reading
How to optimize your website for AI translation

How to optimize your website for AI translation

Kinga WojciechowskabyKingaAugust 19, 2022

Learn how to translate your website with AI translation services like DeepL or Google Translate and optimize your website for translation.

Continue reading