Update one locale, ten, or every locale you ship — in one click.
A faster way to update App Store Connect metadata. Preview every change before it goes live. Update only the fields you touched — leave the rest alone.
What's different about the push
Diff preview before every push
Side-by-side comparison of what's currently in App Store Connect vs. what you're about to write. Nothing goes live until you confirm.
Partial updates by design
Push only "What's New" for a release. Push only the keywords field. Empty fields are skipped — your existing App Store Connect content stays untouched.
One click, every locale
Update 30+ locales in parallel through Apple's official App Store Connect API. No tabbing between locale dropdowns in the web UI.
Character-limit safety
Every field is fitted to Apple's per-field caps before write. No more 422 errors from a German translation that grew past 30 characters.
Locale auto-detection
Pull your current App Store Connect listing in one click. The tool auto-selects every locale you're already shipping for — re-translate or update each.
Built on Apple's official API
No browser automation, no scraping. The push uses Apple's documented App Store Connect API with your own .p8 team key — the key is held in memory only, never stored.
When this matters
Shipping a new version
Update "What's New" across every locale you ship. Instead of 12 web-UI clicks, one push covers them all. Description and other fields stay exactly as they were.
Running a promotional A/B test
Promotional text is editable without a new app version. Push a new variant to all locales at once; revert in one click if the experiment doesn't work.
Launching a new locale
Push name, subtitle, keywords, description, and "What's New" for a brand-new locale in a single API call instead of pasting field by field in App Store Connect.
Updating brand name or product positioning
Renaming a feature, updating a tagline, or swapping a brand mention? Push the same edit across every locale's metadata in one go.
Managing multiple apps
Sign in once with one App Store Connect team key. Switch between apps in the dropdown. Push to any app + version without re-authenticating.
Marketing + dev workflow split
Marketing edits the metadata. Developer signs the API key. Once set up, marketing can push updates without touching Xcode, Fastlane, or any tooling.
How a push actually works
-
Pull current metadata
One click fetches every field from App Store Connect via the official API — name, subtitle, description, keywords, promotional text, what's new. Auto-detects the locales you're already shipping for.
-
Edit, translate, or both
Type new content directly into any field. Or click Translate to AI-generate translations for every selected locale with character-limit and brand-name handling built in.
-
Review the diff
Side-by-side comparison per locale: current App Store Connect value on the left, your new value on the right. Empty fields are flagged as "Won't be updated — existing value preserved" so you know exactly what changes.
-
Push
One click writes every selected locale's changes to App Store Connect through Apple's API. Per-field character limits validated before write. No 422 errors, no silent truncations, no copy-paste.
What about translation?
Translation is built in. If you only need to push (not translate), use the push and ignore it. If you also need to translate — paste your source metadata once, pick locales, AI translates with character-limit fitting and brand-name preservation, review side-by-side, then push.
The split: push is for the workflow pain (App Store Connect's web UI is slow, copy-paste is error-prone, Fastlane is overkill for metadata alone). Translation is for the localization pain (30+ languages × 7 fields = 210 strings per release, growing every time you change the source). Most teams have one or the other; we built one tool for both.
One-time purchase. No subscription.
€2.99 for a single push, €19.99 for a 10-pack. Credits never expire.
Try App Connect Translate →FAQ
Do I need to know the App Store Connect API?
No. You provide your App Store Connect API key (Key ID, Issuer ID, and the .p8 file — step-by-step setup guide). After that the tool runs everything for you. No Ruby, no Fastfile, no CI.
How is this different from Fastlane?
Fastlane is a full iOS release toolchain (builds, signing, screenshots, TestFlight, submission, and metadata). App Connect Translate is purpose-built for the metadata push, with AI translation built in. Many teams use both — Fastlane for builds and signing, App Connect Translate for the metadata. See the full comparison.
Can I push without translating?
Yes. Type or paste your metadata directly into each locale, skip the Translate step, and push. Translation is optional.
What happens to fields I don't fill in?
They're skipped on push. Whatever's currently in App Store Connect for that field stays untouched. This means you can push only "What's New" for a release and the description / keywords / promotional text stay exactly as they were.
Can a non-developer use it?
Yes — once the App Store Connect API key is set up (a one-time, 5-minute task usually done by an engineer), the tool runs entirely in the browser. Marketing teams, ASO specialists, and project managers can push updates without touching Xcode or any dev tooling.
What about screenshots, build uploads, and TestFlight?
App Connect Translate handles only text metadata. Screenshots, build uploads, signing, and TestFlight are out of scope — Fastlane (or Xcode Cloud) is the right tool for those. The two coexist cleanly through the same App Store Connect API.
Is my App Store Connect key safe?
The .p8 private key is held in memory only — never written to disk, never persisted to a database. It's used to sign short-lived (15-minute) JWTs for the API calls and discarded after each request. See our Privacy Policy for details.