Choose the outputs for this release
Select the stores, device sizes, languages, page order and file format you intend to deliver. Review those choices before exporting so the folder contains the screenshot set you need.
Microsoft Store targets require PNG; other presets enforce their own dimensions and accepted formats.
Run preflight
Preflight checks the selected matrix for missing assets and translations, unsafe bounds, invalid page counts, output dimensions, and target-format rules.
Treat errors as blockers. Review warnings in context and record why an intentional exception is acceptable before producing the final folder.
Export the screenshot set
Choose the destination folder and naming pattern, then export the selected pages. Free exports one size and one language per export within its daily image allowance. Pro produces selected sizes and languages in one batch.
Watch the progress and review the export summary. If you change the source artwork during the process, cancel and export the updated selection so the delivered files belong to the same version.
- Write to a clean release destination.
- Use collision-safe filenames.
- Keep the recorded summary with the reviewed output.
Inspect the release folder
Open every file from every device family and language, then verify ordering and file counts against the matrix. Check actual pixels rather than trusting filenames alone.
If a problem is found, fix the project and render a fresh batch. Avoid hand-editing generated output because that breaks repeatability.
Prepare store connections
App Store Connect uses an issuer ID, key ID, app resource ID, and local p8 key. Google Play uses a package name and local service-account JSON. The Microsoft Store uses the app's Store ID, its package type (MSIX, or MSI or EXE), and a local Partner Center JSON file for a Microsoft Entra app.
Credential contents remain local and are not copied into ordinary project data. Confirm the store application identity before authorizing a dry run.
- Use credentials scoped to the intended app and action.
- Keep key files outside shared project exports.
- Remove obsolete store connections.
Dry run, confirm, and publish
A dry run renders and checks the planned upload. With Direct API it also signs in to the store to check the app and its listings, but uploads nothing. Its approval is bound to a fingerprint of project state, selected languages and sizes, connection, and upload engine.
Any relevant change invalidates that approval. A confirmed upload replaces the intended screenshot group only while the fingerprint still matches, preventing a review of one release from authorizing another.