Upload a YAML file and download it as Multi-language 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 single JSON file where every translation key holds an object with one entry per language. Handy for small projects, static sites and CDN delivery because all languages travel together.
Need it the other way round? Convert Multi-language JSON to YAML.
YAML translation files use indentation instead of braces, which makes them easy to read and diff. Ruby on Rails, Symfony and many static site generators keep their locale files in YAML.
Used by: Ruby on Rails, Symfony, Jekyll, Hugo. One language per file. Read the YAML format guide.
hello-world: Hello World!
nested:
translation:
key: Nested translation key
other:
translation:
key:
supported: Look this is also supported!A single JSON file where every translation key holds an object with one entry per language. Handy for small projects, static sites and CDN delivery because all languages travel together.
Used by: custom i18n setups, static site generators, CDN delivery. All languages in one file. Read the Multi-language JSON format guide.
{
"en_US": {
"hello.world": "Hello World!",
"my_address": "My address"
},
"pl_PL": {
"hello.world": "Witaj Świecie!",
"my_address": "Mój adres"
}
}de.json or messages_pt-BR.properties.If you need the Multi-language JSON file in more languages, the fastest route is a free SimpleLocalize project: import the YAML file, add languages, run auto-translation with DeepL, Google Translate, OpenAI, Claude or Gemini, and download the result as Multi-language JSON. The CLI does the same from CI with upload and download commands, so the conversion becomes part of your build. See also translating YAML 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 Multi-language JSON. Placeholders are kept, and Apple and Android specific syntax is translated between platforms. Read more in the pluralization guide.