Upload a Browser extension messages.json file and download it as JSON. Translation keys, plurals and placeholders are preserved. Free, no account needed.
Pick the source format or let the converter detect it from the file.
Used when the source format holds one language per file. Also used as the source language for XLIFF output.
Choose the format you want to download.
A flat or nested key-value JSON file with translations for one language. It is the most common format for web and mobile apps because every language can parse it and it maps directly to the way i18n libraries look up strings.
Need it the other way round? Convert JSON to Extension JSON.
The _locales/xx/messages.json format used by Chrome, Firefox and Edge extensions. Every key holds a message and an optional description for translators.
Used by: Chrome extensions, Firefox add-ons, Edge extensions. One language per file. Read the Extension JSON format guide.
{
"appName": {
"message": "My Extension",
"description": "The name of the extension"
},
"greeting": {
"message": "Hello, $USER$!",
"description": "Greets the user",
"placeholders": {
"user": {
"content": "$1",
"example": "John"
}
}
}
}A flat or nested key-value JSON file with translations for one language. It is the most common format for web and mobile apps because every language can parse it and it maps directly to the way i18n libraries look up strings.
Used by: i18next, react-intl, vue-i18n, next-intl, Angular, Node.js. One language per file. Read the JSON format guide.
{
"hello.world": "Hello World!",
"my_address": "Address",
"nested": {
"translation": {
"key": "nested translation key"
}
}
}de.json or messages_pt-BR.properties.If you need the JSON file in more languages, the fastest route is a free SimpleLocalize project: import the Extension JSON file, add languages, run auto-translation with DeepL, Google Translate, OpenAI, Claude or Gemini, and download the result as JSON. The CLI does the same from CI with upload and download commands, so the conversion becomes part of your build. See also translating Extension JSON files.
Yes. There is no signup and no limit on the number of conversions beyond a few requests per second.
No. The file is parsed in memory, converted and returned in the same request. Nothing is written to disk or a database.
Plural forms are normalized to ICU message syntax and written back in the native form of JSON. Placeholders are kept, and Apple and Android specific syntax is translated between platforms. Read more in the pluralization guide.