Release-Day Checklist: Upload Localized Screenshots to App Store Connect and Google Play Without Surprises

Get the right screenshots into the right language listing, in the right order, and you can finish release day with a page you have actually verified.

The last mile deserves its own checklist. A finished image can still land in the wrong localization, inherit an old screenshot, or sit in changes that have never been submitted.

Disclosure: I build ScreenParcel.

ScreenParcel is a browser tool: upload your app screenshots, paste your own translated headline and subtitle per locale, lay them out across App Store and Google Play sizes, check overflow warnings, and export everything as one ZIP. It does not translate anything.

This checklist starts with approved copy and follows the files through both consoles.

1. Before export: freeze the release scope.

• [ ] Record the app, version, target languages, supported device types, and intended publication window.
• [ ] Choose the screenshot sequence and write down what each position demonstrates.
• [ ] Confirm that every feature shown exists in the release being submitted.
• [ ] Identify whether you are updating the main product page or a separate custom page or listing.

Keep this record outside the screenshot editor. A simple release note with one row per language and columns for export checked, Apple saved, Play saved, and live verified is enough.

Prepare separate iOS and Android captures when their interfaces differ. A correctly sized image still needs to show the experience someone will install.

2. Before export: match captures, copy, and output targets.

Check the app UI inside each image, including menus, sample content, dates, and currency. Your translated headline cannot fix an English interface baked into a capture.

ScreenParcel currently shares uploaded sources across selected locales. Its headline and subtitle are also shared across all source screenshots within each locale. For different localized interfaces, export separate passes with the matching sources and selected language. For different captions on each screenshot, use separate passes with the appropriate copy.

Select output sizes explicitly. Check Apple's current screenshot specifications against the device slots your app needs. Review Google's preview asset requirements for the device types you distribute to.

Clear overflow warnings, then inspect the composition. A passing text measurement does not approve wording, interface accuracy, or readability.

3. After export: approve the files you will upload.

Extract the ZIP into a fresh release folder. Keep earlier exports elsewhere so a file picker cannot quietly mix revisions.

ScreenParcel includes manifest.json with file paths, dimensions, the watermark flag, and overflow warnings. Read it as a handoff check. An empty warnings list only means the renderer detected no caption overflow.

• [ ] Open every final PNG and confirm language, source image, caption, and orientation.
• [ ] Check actual pixel dimensions and the expected number of screenshots.
• [ ] Confirm the intended first image and the complete sequence.
• [ ] Check for placeholders, private information, and preview watermarks.

ScreenParcel numbers files from the uploaded source order. Treat that numbering as your reference, then verify the order displayed inside each console.

Keep a known-good copy of the currently published screenshots before replacing anything. If a new image is wrong, you will have the previous approved asset available.

4. App Store Connect: select the localization before uploading.

Open your app in Apps, select the relevant platform version, and choose the language from the menu at the top right.

If the language is missing, add it from the menu's Not Localized section and complete the required localized information. Apple documents that a newly added language initially receives primary-language screenshots. Seeing images already present does not prove that localization is finished. Apple's localization instructions

Read the selected language again before opening the file picker. Then open only the matching language's release folder. Finish that localization before switching languages.

5. App Store Connect: place, order, and recheck each set.

Under Product Page Information, open App Previews and Screenshots, select the device tab, and upload the matching images. Use View All Sizes in Media Manager to inspect placements for other sizes. Apple's current workflow distinguishes uploading assets into Asset Library from placing them on a product page. Check the page you intend to ship. Apple's asset management guide

For each localization:

• [ ] Confirm the intended images occupy the correct device slots.
• [ ] Remove obsolete placements and check the final sequence.
• [ ] Resolve upload or processing errors before moving on.
• [ ] Save, navigate away, and reopen the localization to confirm the saved result.

Repeat for every supported device category that needs assets. Keep the release note open and mark each language only after reopening it.

6. Google Play Console: add languages and upload their graphics.

Open Grow users → Store presence → Main store listing. Use Manage translations → Select languages, choose the required languages, then apply and save. Select each language and complete its listing information.

Upload that language's screenshots in the appropriate device section under Graphics. Google's asset upload guide identifies the main listing and device-specific screenshot sections.

Google explicitly says that adding translated text without localized graphic assets leaves the default-language graphics showing. A translated description is therefore an incomplete check. Inspect the images themselves. Google's localization guide

For each language, check the screenshot sequence, remove obsolete images, save, and reopen the listing. Upload phone assets to the phone section; prepare other supported device assets separately.

7. Worked example: ship four languages without crossing the files.

Imagine Dayboard, a fictional planning app. This is an example release, with no customer or performance claims.

The release targets US English, German, Japanese, and Brazilian Portuguese. Each platform has three captures in the intended order: today's plan, a focus session, and the weekly review. Approved headline and subtitle copy already exists for each language.

Use this mapping when selecting folders and console languages:

ScreenParcel normalizes ja-JP to ja; its Japanese export folder is ja. Google lists Japanese as ja-JP in its supported listing languages. Keep this mapping in the release note.

For the example, use one approved headline/subtitle pair per language across its three captures. Export each language separately with its localized iOS sources and selected Apple sizes. Repeat with its Android sources and the google-phone target, which the current code renders at 1080 × 1920.

That is eight export passes: four languages for each platform. Keep their extracted outputs separately labeled by platform.

With the Spotlight template, the first Japanese Play image is ja/google-phone/01-device.png. Open it, confirm the Japanese Android capture, then upload it under Japanese in Play Console. Repeat for positions two and three.

In App Store Connect, select Japanese and upload the Apple outputs from the iOS pass. Reopen both saved pages before marking Japanese complete. Follow the same sequence for the remaining languages.

8. Final verification: separate saved, submitted, and live.

Before submission, compare every saved listing against your release note. Confirm the app, platform, language, first screenshot, total sequence, and supported device coverage.

In Play Console, open Publishing overview and inspect the pending changes. Changes requiring review must be sent for review. With managed publishing enabled, approved changes wait for publication; without it, approved changes generally publish automatically. Check the setting before coordinating your release. Google's publishing controls

In App Store Connect, confirm the intended version and its submission status. Keep a record of which localized sets you submitted.

After publication, open the public listings in the intended language and inspect the actual screenshot sequence on a relevant device. Record the language and device used. If the page differs, compare the live result with the saved console placement and approved files.

Keep “saved,” “submitted,” and “live verified” as separate checkboxes. The release is complete when the intended images are visible where your audience will see them.

ScreenParcel offers two locales free with a watermark, a $9 Release Pack, and a $19 30-day Pass.

Prepare your next localized screenshot release with ScreenParcel