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.

No credit card required 14-day free trial Tracking-free service
online translation editor interface
  • Auto-translation
  • Characters counter
  • Translation history
  • File export & import
  • Acceptance status
  • Customizable view
  • Translator descriptions
  • Namespaces support
  • Side-by-Side view
  • Last seen indicators
  • Spreadsheet view
  • Quick search

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.1/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.

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

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

List of country flag icon projects

List of country flag icon projects

Jakub PomykałabyJakubMarch 10, 2023

This is a practical compilation of resources for country flags, which can benefit both designers and developers.

Continue reading
How to create a language selector with Tailwind CSS

How to create a language selector with Tailwind CSS

Jakub PomykałabyJakubMarch 09, 2023

Learn how to create a language selector for your website easily using Tailwind CSS. Follow our step-by-step guide for seamless localization.

Continue reading
SimpleLocalize: Tips & Tricks

SimpleLocalize: Tips & Tricks

Kinga WojciechowskabyKingaMarch 07, 2023

Learn our tips for using SimpleLocalize. Take advantage of the i18n editor's capabilities, automate the translation process and localize your software.

Continue reading
What is ICU? Our guide for ICU message formatting and syntax.

What is ICU? Our guide for ICU message formatting and syntax.

Kinga WojciechowskabyKingaFebruary 02, 2023

ICU message format is the most widely used format for Unicode strings. Learn more about ICU message formatting and syntax for plurals, numbers, dates and time and more.

Continue reading