Publishing to stores
Connect App Store Connect / Play Console and push sets straight to your listings.
On this page
Connect your store account once, then send a finished set from the editor’s export dialog to your listing.
Connect a store
| Store | Credentials | Setup guide |
|---|---|---|
| App Store Connect | Issuer ID, Key ID, and .p8 team key | Set up Apple access |
| Google Play | Service account JSON key and app permissions | Set up Google Play access |
Manage both accounts in Settings → Connections. Credentials are encrypted on the server and are not returned to the browser after saving.
Prepare your set
Finish your headlines, check the screenshot order, and choose export presets for the store you are targeting. Each selected store size needs a supported number of screenshots:
| Store | Screenshots per selected size |
|---|---|
| App Store Connect | 1–10 |
| Google Play | 2–8 |
AppStaged validates the count and size mapping before publishing. Adjust a set that falls outside these limits before trying again.
Publish from the editor
- Open the export dialog and choose the store publishing option.
- Select your app. Google Play requires its package name; Apple apps are loaded from your connection.
- Choose the available version, locale, and screenshot sizes.
- Review the target and rendered screenshots, then confirm publication.
Publishing replaces existing screenshots in the selected store sizes and locale. Check the target and order before confirming.
Review in the store console
For Apple, check the screenshots on the selected app version in App Store Connect. For Google Play, changes are staged in Play Console and have not been sent for review. Review and submit them there.
If Apple reports an incomplete replacement, inspect the listing before retrying: some previous screenshots may already have been removed. Use the job’s result to check which files were confirmed.