Organized, Type-Safe Localizable.strings anyone?

Using StringBuddy you can import your existing iOS / macOS localizations, add new ones, keep track of missing translations, add new languages and even tag your keys so they're easy to find.

Once you or your team mates are done translating, just hit export and get the Localizable.strings and an auto-generated Swift export of your strings.

Using CI to build your App? We've got you covered! Just use our CLI tool!

Howto & FAQ

Impressum, Privacy & Terms



Below you'll find some useful tips on getting started with StringBuddy. If you've got any questions, don't hesitate to get in touch via mail.

Importing or exporting Localizable.strings from or to an existing Xcode Project

When importing or exporting localizations from or to an existing Xcode Project, StringBuddy needs to be pointed to the App Target's folder:

As you can see in the screenshot above, not the folder containing the .xcodeproj but rather the App Target folder which lives next to the .xcodeproj has been selected.

Installing and using StringBuddy CLI

StringBuddy has a companion commandline interface which can be either downloaded here or installed using the code below.

curl -L -o stringbuddy-latest.tar.gz && tar -zvxf stringbuddy-latest.tar.gz && cp ./stringbuddy /usr/local/bin/

To convert your .stbd File into Cocoa compatible Localizable.strings, just call stringbuddy with your input file and the output directory:

stringbuddy --in ./MyAppLocalizations.stbd --out /path/to/project

You can also integrate StringBuddy on your build server to always keep your Localizable.strings up to date. If you've successfully integrated StringBuddy we'd love to get some feedback.