Convert Extension JSON to XLIFF 2.0 online
Upload a Browser extension messages.json file and download it as XLIFF 2.0. 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.
XLIFF 2.0 is the newer OASIS standard with a simpler structure: files, units and segments. It is the preferred exchange format for modern CAT tools and localization vendors.
Need it the other way round? Convert XLIFF 2.0 to Extension JSON.
From: Browser extension messages.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"
}
}
}
}To: XLIFF 2.0
XLIFF 2.0 is the newer OASIS standard with a simpler structure: files, units and segments. It is the preferred exchange format for modern CAT tools and localization vendors.
Used by: CAT tools, Angular, translation agencies. One language per file. Read the XLIFF 2.0 format guide.
<?xml version="1.0" encoding="UTF-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:2.0" version="2.0" srcLang="en" trgLang="fr">
<file id="app_strings" original="messages.json">
<unit id="hello_world">
<segment>
<source>Hello World</source>
<target>Bonjour le monde</target>
</segment>
<note>My comment</note>
</unit>
</file>
</xliff>How to convert Extension JSON to XLIFF 2.0
- Drop your .json file into the converter above, or paste its content.
- Confirm the language of the file. It is guessed from the file name, for example
de.jsonormessages_pt-BR.properties. - Click Convert. You get one .xliff file per language.
- Preview the result, copy it or download the files.
What changes between Extension JSON and XLIFF 2.0
- The language you enter in the converter becomes the XLIFF source-language, and the same texts fill both source and target elements.
Convert and translate in one place
If you need the XLIFF 2.0 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 XLIFF 2.0. 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.
Frequently asked questions
Is the converter free?
Yes. There is no signup and no limit on the number of conversions beyond a few requests per second.
Are my files stored?
No. The file is parsed in memory, converted and returned in the same request. Nothing is written to disk or a database.
What about plurals and placeholders?
Plural forms are normalized to ICU message syntax and written back in the native form of XLIFF 2.0. Placeholders are kept, and Apple and Android specific syntax is translated between platforms. Read more in the pluralization guide.
Convert Extension JSON to other formats
Translate your XLIFF 2.0 files
- Import Extension JSON or XLIFF 2.0 files into a free project
- Auto-translate with DeepL, Google, OpenAI, Claude or Gemini
- Download in any of the supported formats or publish to the CDN