App Localization For iOS & Android Teams
Localize app strings, release notes, and store metadata through the Git workflow your team already trusts. Review updates in GitHub, GitLab, or Bitbucket, then bring in human reviewers when nuance matters.
One free language to see how it works • no credit card required • your repo stays the source of truth
Featured in
The product covers the shipping surfaces developers actually own: app strings, app updates, and store listing copy. One product instead of three.
Ship .xcstrings and Android strings.xml updates without spreadsheet cleanup, broken builds, or one-off scripts.
Try the free editor →Handle App Store and Google Play release notes in the same product instead of maintaining side docs.
Explore release notes →Generate localized store listing content with platform-specific field limits, locale handling, and exportable output for the places growth teams actually ship.
Explore metadata workflow →Keep your release process. Remove the localization overhead. String Catalog is built for teams that already know how they want to ship.
No vendor lock-in. Your repo stays the source of truth.
Connect the workflow you already ship from
Link GitHub, GitLab, or Bitbucket, pick the branch you release from, and let String Catalog work through reviewable updates instead of extra tools.
Carry your product voice into every locale
Choose languages, add tone guidance, protect brand terms, and keep the context reviewers need so output sounds like your app instead of a generic translation.
Review safely, then ship on schedule
Merge clean diffs in Git, share secure no-login review links when nuance matters, and retry low-confidence output before release week turns into cleanup week.
Fast enough for release week. Safe enough for teams that care about quality. Automation that still respects source control, human judgment, and the voice of your product.
Your repo stays the source of truth.
String Catalog is built around branches, pull requests, and scoped source-control access. The product is designed for safe reviewable changes, not silent content mutation.
AI speed with real human checkpoints.
Manual edits, secure review links, review queues with suggested fixes, and bulk acceptance are already part of the product when a translation needs more than an automatic pass.
Native formats stay native.
Apple and Android localization assets, release notes, and store metadata stay in the shapes your build, release, and growth workflows already expect.
Protected terms and tone travel with the product.
Glossary rules, prompts, and brand voice guidance are not an afterthought. They help each new language launch feel like the product your users already know.
Real feedback from developers using the product in their release workflow, not just in a demo environment.
Brett Bauman
@brettunhandled
"String Catalog is by far the best app localization tool on the market. It's rare to find a web-based tool for iOS development that's this polished—String Catalog feels great to use and is quick to set up."
Rudrank Riyam
@rudrankriyam
"Within a few clicks, I could localize my app to 40+ languages! The latest changes also provide confidence in the translation per key, making String Catalog one of the best time-savers for me to reach different markets!"
HAHarry Lachenmayer
@lachenmayer
"Waiting for translations slows down almost every single release, which makes it a huge chore for a tiny team like us trying to move fast. String Catalog has been a lifesaver, allowing us to launch new features globally as quickly as we can..."
Pick the entry point that matches what you need to ship next. Open the editor, localize release notes, plan store metadata, or run the calculator first.
Open .xcstrings files, clean up stale strings, and try the product with one free language.
open_editor() →
Translate App Store and Google Play release notes without hand-copying the same release into every market.
see_workflow() →
Plan App Store and Google Play listing copy with field-level limits, locale mapping, and review-ready exports.
see_metadata() →
Model pricing by strings, languages, and release cadence before you commit to a plan.
run_numbers() →
Check locale coverage and platform-specific codes before you add your next market.
browse_langs() →
Go deeper on String Catalogs, release workflows, and Apple localization gotchas.
read_guide() →
Connect your repo, localize what actually ships, and keep release week focused on QA instead of translation logistics.
