String Catalog Logo
String Catalog
Start Free Log In
$ pricing_calculator estimate --before-you-buy

Free tool for iOS & Android teams

Estimate localization spend before you choose a plan.

Use the calculator to model .xcstrings and Android strings.xml work, then share a clearer plan with product, finance, and localization before the next release gets expensive.

estimate_cost() → see_pricing() →

One free calculator • share the link with your team

sample_scenario.sh
  • > 5,000 base strings
  • > 20 target languages
  • > 5 teammates collaborating
  • > 10 releases per month with monitoring

$45 /month

Pro plan for a team shipping frequent localized releases

string_volume()

Base string count

See how the number of source strings pushes you between Hobby, Pro, and Business before you commit.

release_cadence()

How often you ship

Model one launch or many. Frequent releases usually change the economics faster than teams expect.

review_needs()

QA and collaboration

Compare plans with and without monitoring, review links, and team support so stakeholders can align earlier.

> Run The Numbers

Enter your assumptions once, then copy the URL with query parameters to share a live estimate with the people who need to sign off on the plan.

// estimate_investment()

Estimate Your Localization Investment

Adjust the variables on the left to see which String Catalog plan fits your base string catalog and how the subscription breaks down per release.

Base string keys
Target languages

All plans include translations for up to 40 languages—no extra per-language fees.

Releases per month
Team size

Team support is included starting with the Pro plan. Invite collaborators without extra seats.

Accuracy monitoring

Enable if you need automated localization accuracy monitoring. Available on Pro and Business.

// how_we_size_plans

  • - Base string allowance is counted once—localized variants are unlimited.
  • - All plans include up to 40 languages with no additional cost.
  • - Monthly view divides the plan price across your release cadence.
  • - Pro and Business unlock team support plus accuracy monitoring.

// recommended_plan

Pro

$45.00 per month · $432.00 yearly

Save $108 per year when billed annually (20% off)

PRO
// view_totals

Per release

$22.50

Plan price allocated across 2 releases.

Monthly

$45.00

Flat subscription—translations included.

Annualized

$432.00

Equivalent annual billing (translations still included).

// what's_included

  • Unlimited localized strings across 5 languages.
  • Automated syncs for every push—no overages for frequent releases.
  • Team support: Included · Accuracy monitoring: Included.
  • Release notes localization: Unlimited (App Store and Google Play release-note workflows)
  • Store metadata localization: Included for App Store and Google Play workflows.
  • Upgrade when your base string catalog grows past 7,500 keys.
start_free_trial()

> What Affects App Localization Cost

The more base-language strings you manage, the more plan capacity you will need. The calculator maps that volume to the tier that best fits.
Teams shipping often feel the value of automation sooner. Releases per month help explain what the spend looks like per launch.
All plans cover up to 40 languages. The calculator helps you see how that coverage interacts with the rest of your workflow.
Accuracy monitoring, shareable review links, and team collaboration can shift the right plan faster than string count alone.
You can use the estimate to think beyond app strings and include launch copy, store listings, and update notes in the same planning conversation.

estimate_strings()

Quick Benchmarks

If you do not know your exact string count yet, these rough ranges are usually enough to model a realistic first pass.

  • Authentication flow
    Login, signup, forgot password, and 2FA typically land around 20 to 40 strings.
  • Settings and preferences
    Profile, notifications, and accessibility settings often land closer to 150 to 250 strings.
  • In-app product content
    Tours, empty states, tooltips, and upgrade copy commonly add 300 to 600 strings or more.
  • Release notes and store copy
    You can also model App Store and Google Play release-note text so launch planning is not siloed from the app.

Tip: Export your .xcstrings or Android XML files for an exact count before the next localization sprint if you need a tighter estimate.

next_step.sh

> Turn The Estimate Into A Plan

When the numbers look right, compare plans and choose the level of automation and review support that fits your release workflow.

see_pricing() contact_us()