> Frequently Asked Questions

Find answers to common questions about String Catalog and localizing your application.

String Catalog is a developer-focused service for localizing app strings, release notes, and store metadata. It supports .xcstrings uploads, Android strings.xml through connected repositories, and app-update workflows for App Store and Google Play. Learn more in our Xcode localization guide.
Our Auto Sync feature, when enabled, automatically runs each time you push code to a connected repository. It detects new or changed strings, updates translations accordingly, and removes obsolete ones, keeping your localizations in sync without manual cleanup.
String Catalog automates translation and localization updates by connecting to your source control repository and generating reviewable updates with localized strings. This streamlines review and integration, improving accuracy and accelerating your release cycle.
Yes. Developers can customize the localization tone and style to better match their brand voice. You can also provide custom prompts to guide our AI engine for more accurate, on-brand results.
We offer flexible subscription plans starting at $15/month, designed to suit projects of all sizes—from indie apps to enterprise-level solutions. Run the numbers with our app localization price calculator to see how your app localization cost changes by strings, languages, and release cadence.
Yes. TestFlight reviewer notes are supported at no additional cost, making it easy for iOS teams to localize their “What to Test” files alongside app strings. Learn more in our guide to localizing TestFlight release notes.
Yes. The Hobby plan supports up to 3,000 base strings, Pro up to 7,500, and Business up to 15,000 strings. Each string can contain up to 400 characters to ensure full coverage of your app’s text.
Translation converts text from one language to another, while localization adapts content to cultural, regional, and contextual nuances. String Catalog focuses on localization to make your app more relevant and engaging in each market.
We support a wide range of languages—including English, Spanish, Chinese, and many more—covering major global languages as well as regional ones to help you reach diverse audiences. View all supported languages in our languages list.
String Catalog was built to solve the complexities developers face managing and localizing app strings, making localization faster, easier, and more reliable on Apple platforms and Android.
Create an account, connect GitHub, GitLab, or Bitbucket, or start with a manual .xcstrings upload. Then choose your target languages and let String Catalog prepare localized updates you can review before shipping.
We use AI-powered translation models with custom prompts, but we recommend reviewing results to ensure they match your brand voice and audience.
Absolutely. You control your data and can modify or delete any information anytime via your account settings to maintain your privacy and security.
We only access the localization-related files in the repositories you authorize, such as .xcstrings, Android strings.xml, and supported app-update files. Access is granted using secure, limited-scope tokens. All data is encrypted in transit and at rest. You can revoke access at any time from your source control provider settings.
Yes, it's optimized for Apple platforms like iOS and macOS, integrating tightly with Xcode and supporting Android app localization via Android XML. It supports developers working with Swift, Objective-C, Kotlin, and Java.
Yes. Payments are securely processed through Stripe, ensuring your financial data is protected with industry-standard security.
You can reach out anytime via our contact page. We welcome your questions and feedback to continually improve String Catalog.
Start with one free language on a project to evaluate the workflow. After that, a subscription is required to continue using String Catalog.
Yes. Team collaboration is supported on the Pro plan and above, allowing multiple users to contribute and manage localization projects together.
While we don't offer a full CI/CD integration yet, you can connect GitHub, GitLab, or Bitbucket so String Catalog can automatically track string changes, localize them, and prepare reviewable updates for your team.
Yes. In addition to repository-based reviewable updates, you can download localized files directly from your dashboard.
The core self-serve workflow supports .xcstrings uploads, Android strings.xml in connected repositories, and app-update workflows such as release notes. Store metadata is also supported as part of paid launch workflows.
We use advanced AI models and custom prompts tailored to app localization to deliver high-quality, context-aware translations.

> Still have questions?

Can't find the answer you're looking for? Please chat with our support team.