Publish metadata to the store
Send approved ASO metadata and optional screenshots to App Store Connect or Google Play with the Publisher.
Updated September 30, 2026
The Publisher sends your approved metadata – and optionally new screenshots – straight to the store, so you don't have to copy text into App Store Connect or Google Play Console by hand.
Before you start
- Connect your app. Publishing needs a store connection. If your app isn't connected, the Publisher shows Connect my app, which takes you to your connections.
- Approve at least one ASO. Only approved generations can be published. See Review, edit and approve generated metadata.
Open the Publisher by clicking Publish ASO on an approved generation, or from ASO Generation > Publisher. On the App Store, changes go to App Store Connect; on Google Play, they go to the Production track.
Step 1: Select languages
Under Choose what to publish, pick one approved version per language. Click Select latest for all to pick the newest approved version everywhere, or Clear to start over. Each version card shows the title, subtitle, hidden keywords, description and patch notes.
Click Continue.
Step 2: Upload screenshots (optional)
Click Skip to keep your current store screenshots, or upload new ones:
- Choose a screenshot size (for example an iPhone display size or iPad Pro 12.9″ on the App Store, or Phone or 10-inch tablet on Google Play).
- Choose Upload images and drop PNG or JPEG files, then drag them into order. Or choose Upload ZIP and use Download ZIP template to get the right folder structure for several locales and sizes at once.
- Click Upload & Continue.
Each locale and size needs 6–10 screenshots on the App Store (6–8 on Google Play). App Store screenshots must match the expected pixel sizes exactly; images with the wrong dimensions are highlighted so you can remove them.
Step 3: Review & publish
Check the summary of locales and screenshots, then click Publish to the store.
This submits changes directly to the store. If you added screenshots, existing screenshots in those groups are replaced. On the App Store, a store-side failure can leave a group partially updated. Make sure everything is correct before publishing.
After publishing
You'll see the progress. You can leave the page – you'll get a notification when it's done. When it finishes, you'll see Published to the store. The store may take a while to show the changes.
If publishing fails, click Try again or Back to review.
After your new metadata goes live, use Timeline and the Keyword Performance tab in Keyword Research to see how it affects installs and rankings.
Related articles
What's next?
Was this page helpful?
Still stuck? Contact support