iOS localization tool
for Apple string files

Manage .strings, .stringsdict, and xcstrings files,
auto-translate content, and sync with your iOS app via CLI.

Start for free
No credit card required•14-day free trial•Tracking-free service
SimpleLocalize - iOS translation editor
Localizable.stringsStringsdictLocalizable.xcstringsSwift & Objective-CPlural rulesCLI & REST APIDeepL · Google Translate · OpenAITranslation hosting CDNCI/CD syncXcode projectsTeam translation editorLocalizable.stringsStringsdictLocalizable.xcstringsSwift & Objective-CPlural rulesCLI & REST APIDeepL · Google Translate · OpenAITranslation hosting CDNCI/CD syncXcode projectsTeam translation editor

We power your product localization
From first commit to global launch

Used at IntersportUsed at IKEAUsed at InvisalignUsed at AmdocsUsed at OSRAMUsed at project44Used at nglUsed at IQAirUsed at walcuUsed at UNICEFUsed at AstraZenecaUsed at nabooUsed at SagemathUsed at Brite

Why iOS teams
use SimpleLocalize

iOS projects tend to collect several localization formats over time: classic Localizable.strings files, .stringsdict plural rules, and now Localizable.xcstrings in newer Xcode projects. Keeping these files updated by hand across screens, modules, and languages takes time and invites mistakes.

SimpleLocalize keeps Apple translations organized in one place while fitting into the workflow you already use. Upload files with the CLI, review text in the online editor, and export files back to your project when releases are ready. Browse more integrations ->

iOS localization workflow

Built for the iOS localization workflow

From Xcode string files to shipped builds, SimpleLocalize supports the way Apple teams manage translations.

Native Apple format support

Upload and download Localizable.strings, Stringsdict, and Localizable.xcstrings files while preserving the structure your app expects.

CLI pipeline

Use the SimpleLocalize CLI to push source files, translate missing content, and pull finished files back into your iOS repository.

AI auto-translation

Translate new strings with DeepL, Google Translate, OpenAI, and other models. Bring your own API keys when you need full cost control.

Old and new Xcode formats

Work with classic .strings files, plural rules in .stringsdict, and modern xcstrings catalogs in one platform.

Consistent files for every release

Stop editing .lproj files in many branches. Pull current translations into the project during each build or release cycle.

Placeholder and plural validation

Catch invalid format specifiers, missing plural rules, and broken placeholders before they land in production.

How it works

From Apple string files to production in 3 steps

A CLI-first flow that keeps iOS translations current across releases.

1

Upload source files

Run simplelocalize upload to push Localizable.strings, Stringsdict, or xcstrings files from your project.

2

Translate and review

Auto-translate missing text with DeepL or OpenAI, then review translations in the online editor with your team.

3

Download and ship

Run simplelocalize download to pull translated files back into your Xcode project before the next release build.

For a step-by-step walkthrough, see the getting started guide.

Ready to simplify iOS localization?

Start a free project and upload your first Apple translation file in minutes.

Start for free

CLI pipeline

From source strings to release build
in two commands

Push your source strings, translate in the cloud, and pull updated files back into the iOS app.

Terminal
# Upload source Localizable.strings $ simplelocalize upload --uploadFormat localizable-xcstrings --uploadLanguageKey en --uploadPath ./en.lproj/Localizable.xcstrings ✓ Uploaded 154 strings from Localizable.xcstrings # Auto-translate missing content $ simplelocalize auto-translate ✓ Translated 154 strings into 12 languages # Download translated files $ simplelocalize download --downloadFormat localizable-xcstrings --downloadPath ./{lang}.lproj/Localizable.xcstrings ✓ Downloaded 12 Localizable.xcstrings files

Add these commands to CI/CD for automated localization in each build. Read more about the i18n online editor and visit all developer tools.

One project
for iOS, Android, and Flutter

Building mobile apps across several platforms? Manage translations in one SimpleLocalize project and export each platform format separately.

iOS (Strings / Xcstrings)

Manage Localizable.strings, Stringsdict, and xcstrings files for Apple platforms.

Android (XML)

Export strings.xml resources for native Android modules from the same project.

Flutter (ARB)

Export .arb files for Flutter apps while keeping keys aligned across mobile platforms.

One project for iOS, Android, and Flutter

Why SimpleLocalize

Built for iOS developers

Practical tooling that matches Apple localization workflows.

Apple formats
Work with .strings, .stringsdict, and xcstrings files in one localization workflow.
CLI-first
Upload and download translation files from scripts, CI/CD jobs, and release pipelines.
Multi-platform
Use one project for iOS, Android, Flutter, and web applications.
AI translation
DeepL, Google Translate, OpenAI, and other models are available in one place.
Validation
Placeholder and plural validation helps catch message issues before release.
Flat pricing
Predictable key-based pricing with no hidden fees.
CTA FeaturesGo to Editor

Start localizing your iOS app today

  • All-in-one localization platform
  • Web-based translation editor for your team
  • Auto-translation, QA-checks, AI and more
  • See how easily you can start localizing your product.
  • Powerful API, hosting, integrations and developer tools
  • Unmatched customer support
Start for free
No credit card required∙5-minute setup
"The product
and support
are fantastic."
Laars Buur|CTO
"The support is
blazing fast,
thank you Jakub!"
Stefan|Developer
"Interface that
makes any dev
feel at home!"
Dario De Cianni|CTO
"Excellent app,
saves my time
and money"
Dmitry Melnik|Developer

Frequently asked questions

How does SimpleLocalize handle iOS translation files?

SimpleLocalize supports Localizable.strings, Stringsdict, and Localizable.xcstringsfiles used in Apple projects. Upload source files through CLIor API, manage translations in the online editor, and download files back in the format your project expects.

Does this work with Swift and Objective-C projects?

Yes. The workflow works for Swift and Objective-C apps that use traditional .strings files, plural rules in .stringsdict, or newer xcstrings catalogs in Xcode.

Can I use xcstrings and classic .strings files in the same workflow?

Yes. SimpleLocalize supports both older and newer Apple localization formats, so teams can keep current projects moving while adopting xcstrings where it makes sense.

How does this fit into iOS CI/CD pipelines?

Add simplelocalize upload and simplelocalize download commands to your build or release pipeline. Source strings are pushed and translated files are pulled back automatically during each release cycle.

Can I manage iOS and Android translations in one project?

Yes. One SimpleLocalize project can include iOS, Android, Flutter, React Native, and web translations. You keep one shared key set and export the correct file format for each app.