Upload a Xcode String Catalog (.xcstrings) 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.
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 String Catalog.
String Catalogs were introduced in Xcode 15 and store all languages, plural variants and device variations of a project in one JSON-based .xcstrings file.
Used by: Xcode 15+, SwiftUI, iOS 17+. All languages in one file. Read the String Catalog format guide.
{
"sourceLanguage" : "en",
"strings" : {
"hello world" : {
"comment" : "My Hello World description",
"extractionState" : "manual",
"localizations" : {
"pl" : {
"stringUnit" : {
"state" : "translated",
"value" : "Witaj Świecie!"
}
}
}
}
},
"version" : "1.0"
}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"
}
}If you need the Multi-language JSON file in more languages, the fastest route is a free SimpleLocalize project: import the String Catalog 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 String Catalog 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.