How to fill App Store Connect locales without copy-paste
If you ship multilingual App Store listings by hand, the slow part is rarely writing the copy. It’s switching locales on App Store Connect and pasting name, subtitle, description, keywords, and What’s New—one field at a time—hoping you didn’t drop Japanese keywords into Korean.
This guide covers a simple workflow: keep one locale pack as source of truth, open the ASC localization page you already use, and fill the current language in one pass (with a quick visual review).
For each localization, App Store Connect expects the same field set. Typical release updates touch:
Name — app name for that storefront language
Subtitle — short line under the name
Description — full product description
Keywords — comma-separated search terms for that locale
What’s New — release notes for the version you’re submitting
Character limits and keyword rules still apply per field; a fill tool doesn’t replace proofreading—it removes the tab-and-paste loop.
Why copy-paste breaks down
You keep translations in a spreadsheet, Notion, or ChatGPT export—then re-type them into ASC.
Locale switchers and long forms make it easy to paste the wrong language into the wrong tab.
Keywords are easy to scramble: same characters, different storefront meaning.
What’s New often needs the same structure in every language right before submit.
Teams that already push metadata through the App Store Connect API, Transporter, or a release pipeline may not hit this pain. This guide is for developers who still edit the web form.
A cleaner workflow
Keep a locale pack — one JSON or CSV with fields per language (name, subtitle, description, keywords, what’s new).
Open the ASC localization page for the language you’re editing (you’re already signed in).
Import the pack and Fill the current language — fields populate on the page you’re viewing.
Review highlights — skim diffs; undo if something looks off before you save in ASC.
Repeat per locale — switch language on ASC, fill again from the same pack.
Using ASC Fill (Chrome)
ASC Fill is a small Chrome extension that runs on appstoreconnect.apple.com. It does not replace ASO research or keyword tools—it only fills the form you’re looking at.
Load unpacked (important)
Unzip the extension package.
Open chrome://extensions → turn on Developer mode → Load unpacked.
Select the extension root folder — the one that contains manifest.json (and usually popup.html, content.js, icons/).
Do not select the icons/ folder or a nested parent zip folder. Chrome needs the directory that has manifest.json at the top level.
Open App Store Connect → your app’s localization page → import your locale pack → Fill for the current language.
Host permission is limited to App Store Connect. The extension does not need your Apple password; you stay logged in as usual in the browser.
Locale pack tips
Use stable language codes that match how you name locales in your pack (e.g. ja, ko, zh-Hans) and map them to the ASC locale you’re viewing.
Keep keywords as a single string per locale (comma-separated), the way ASC expects.
Treat What’s New as version-scoped: update that field in the pack when you cut a release, then refill each locale.
After fill, still click through ASC’s own validation—character limits and required fields are Apple’s rules.
When this helps (and when it doesn’t)
Helps if: you maintain several storefront languages and still edit ASC in the browser.
Less useful if: metadata is already pushed via ASC API / Fastlane / similar and you rarely open the localization form.
Next step
If you’re mid-release and tired of pasting the same five fields across languages, try the fill loop on one locale first—then decide if it’s worth keeping in your release checklist.