Free tool
Convert .xcstrings to Excel, CSV and strings.xml
Open a String Catalog as a spreadsheet, send it to a translator, and merge their column back into the same file. Plurals, substitutions and comments come along. It runs in your browser, so the file never leaves your machine.
Runs in your browser. Your file is not uploaded.
The sheet
A row per string and plural form, a column per language.
The source language comes first. Rows for plural forms the source language does not use stay empty in its column; they are there for the languages that need them.
| key | variable | plural | comment | en | de | pl |
|---|---|---|---|---|---|---|
| Welcome back | Home screen title | Welcome back | Willkommen zurück | |||
| %lld files | one | Toolbar count | %lld file | %lld Datei | ||
| %lld files | few | Toolbar count | ||||
| %lld files | many | Toolbar count | ||||
| %lld files | other | Toolbar count | %lld files | %lld Dateien |
Round trip
From Xcode to a translator and back.
Step 1: Drop your String Catalog
Drop Localizable.xcstrings above, pick Excel, and type the languages you want translated. Each one becomes an empty column, with a row for every plural form that language needs: Polish gets few and many, Arabic all six.
Step 2: Send the sheet
The translator fills their column in Excel, Numbers or Google Sheets and sends it back as .xlsx or CSV. Semicolon CSVs from Excel in German or French settings read the same.
Step 3: Merge it back
Drop the returned sheet together with the original .xcstrings. You get the same catalog back with the new text in it, every string you changed marked translated.
Step 4: Commit the catalog
Replace the file in your Xcode project. Keys, order, comments and extraction state are as Xcode left them, so the diff shows only the new translations.
Good to know
- Device and width variations stay in the catalog but not in the sheet.
- A string you change comes back marked translated.
- Files up to 25 MB.
What carries over
What makes the round trip safe.
Plural forms per language
A row for every CLDR plural form the sheet's languages need, so a translator sees few and many for Polish instead of guessing.
Substitutions included
A string like "%#@files@ in %#@folders@" gets its template row plus a row per form of each variable, and a new language inherits the argument numbers.
Unchanged means unchanged
Merging a sheet nobody edited gives back the catalog byte for byte. An empty cell never deletes a translation.
Comments for context
Each row carries the key's comment, so the translator sees where the text appears.
Protected keys stay put
Keys marked Don't Translate, and device variations a sheet can't hold, are left out of the sheet and left exactly as they were on merge.
Nothing uploaded
The page converts in your browser: no upload, no account, nothing stored.
Questions
- Is my .xcstrings file uploaded anywhere?
- No. The conversion runs in your browser, and the page sends nothing anywhere when you drop a file.
- Can I convert an Excel or CSV file back to .xcstrings?
- Yes. Drop the sheet together with the catalog it came from and you get that catalog back with the new text merged in. Drop a sheet on its own and you get a new catalog whose source language is the first language column.
- What happens to plural strings?
- Each plural form is its own row, labelled with its CLDR category: one, few, many, other and so on. The sheet has a row for every form any of its languages needs, and merging writes them back as Xcode's plural variations.
- What does not survive the round trip?
- Device and width variations are left out of the sheet, and the merge leaves them as they were. A string you change comes back marked translated, whatever state it had, and an empty cell never deletes a translation.
- Can I turn .xcstrings into Android strings.xml?
- Yes. Pick Android strings.xml and you get a zip with a values folder per language and the source language in values. Keys become valid Android resource names, plural keys become plurals, and format specifiers like %@ become %s.
- Can I convert .xcstrings to .strings files?
- Yes. Pick .strings and .stringsdict and you get an .lproj folder per language, with plurals in the .stringsdict, for code or tools that still read the older formats.
Start with the file your app already ships.
After checkout, import one strings file and read the first drafts within minutes.
Nothing to connect and nothing to install. The CLI is optional.