Knowledge Base

Documentation to help you use the POEditor localization platform effectively

How to translate Xcode String Catalogs (.xcstrings)

To translate an Xcode String Catalog, import the .xcstrings file into a POEditor project (just the source language or all the languages in it), translate the strings with the available translation options, and export the catalog back as one .xcstrings file with all your languages.

Import your .xcstrings file

Add the source language to the project, then use Import in the project page to upload the languages from your XCstrings file.

Import XCstrings file (Project page) - POEditor localization platform

You can choose between importing only the source language and importing all the languages in the file:

  • Source language adds only the strings from the source language.
  • All languages adds the strings from the other languages as well. Additionally, if the system finds language codes in your file that match the ones in our language list, it will add those languages to the project too.

Using different language codes? You can create custom languages to import them.

Import XCstrings file using Git integration

After you add the source language to the project, go to Integrations and link the source language to the String Catalog file in your repository.

Link XCstrings source language (Git integration) - POEditor

In the link's settings, check Import all languages to bring all the languages from the linked file into the project.

Import all languages with Git integration - POEditor

After setting the import rule, use Import > Import terms and translations to upload all the languages. Languages that are missing in the project are created automatically, as long as their language code exists in our database.

Import terms uploads only the keys from the .xcstrings file, while Import translations adds only the translations for the linked language, based on the language code (the language code in the project must exist in the file).

The file can be exported back to your repo using the Export option.

Import and export with the API

You can also use the POEditor API to upload and download the languages from your XCstrings files to your localization project.

Use the method projects/upload with the language argument empty in order to bring all the languages to the localization project, and the projects/export method to download the localized .xcstrings file.

If you're a user on the Enterprise plan, you can also set up automated backups to your preferred 3rd party storage service.

Translate your strings

Add the languages you need, then choose how to translate them:

Translation memory (available from the Start plan) suggests earlier translations of identical strings, and QA checks and QE feature catch issues before export.

Export your String Catalog

To export all the localized languages back to one .xcstrings file, check Export all languages in Advanced export options.

Export all languages from Xcstrings file - POEditor

Good to know

  • Plural forms in String Catalogs are imported and shown for each target language.
  • Device and width variants are imported as separate strings, named the same way as in .stringsdict files, so strings from an .xcstrings file can be exported as .stringsdict files, and the other way around.

Localizing a whole iOS app? Follow How to translate an iOS app.
Only need to edit .strings files? Use the Strings Editor.

Additional help

Related articles