Plan panoramic App Store screenshots that still work one at a time

Choose between a connected story and a seamless image

A connected story can use repeated colors, aligned headings and related app screens without matching the pixels at every edge. A seamless image needs a shared coordinate system so that a background or object continues at exactly the same position on the next panel. These are different design requirements.

The existing Travel Planning catalog example above connects flight, destination and booking screens with diagonal purple and cream shapes. It is not presented as a verified seamless panorama. Its original five-board design and preview are reused without creating a new template.

Write the first three messages before adjusting the artwork

1. Pick the real app screen that best explains the main job. Give the first image a complete headline and enough product detail to stand alone.
2. Use the second image to show how that job is accomplished. For a collection app, this could be a saved collection; use a different screen if your product has a different workflow.
3. Use the third image to answer a distinct question, such as how something is found again. Remove repeated promises and unsupported ratings, awards or testimonials from sample content.
4. Plan later images around additional useful actions. On Skir Free, only the first three boards are editable and exportable; plan the review around the access you actually have.

Use one coordinate system for artwork that must cross a seam

For N equal panels of width W and height H, the continuous working area is N × W pixels wide and H pixels high. Panel i starts at x = i × W, counting i from zero. An object at global x = X has local x = X − i × W in that panel. Keep the same scale, y position and rotation for every piece of that shared object.

For three 1290 × 2796 panels, the conceptual working area is 3870 × 2796, with boundaries at x = 1290 and x = 2580. This describes the design geometry, not a new upload size. The delivered files remain separate images in a supported screenshot size.

If your design tool has a shared panoramic canvas, use its frame or slice boundaries to export the individual images. If you work in separate boards, use the same measured crop for each relevant board. Do not drag two similar-looking copies independently and assume they will meet. Skir's documented workflow on this page is template editing and per-board export; a shared-canvas splitter is not demonstrated here.

Adapt an existing template in Skir

1. Open the linked library template and choose the intended App Store or Google Play target in the template dialog. The sample library target is iPhone portrait at 1290 × 2796; the Android choice changes the canvas and requires a fresh layout review.
2. Replace sample app images with captures from your release build. Keep the internal app artwork together. Edit the surrounding headlines and decoration to support the actual feature shown.
3. Keep essential copy and controls inside their own board. Use any crossing decoration as a secondary connection so that losing the next panel does not lose the message.
4. Save, reopen and export the eligible boards as PNG or JPEG. Use the downloaded files in the local review below. Inspect the full-resolution files separately for text, clipping and image quality.

Inspect zero gap, visible gap and a different order

At zero gap, inspect the boundary for a jump in background color, vertical position, phone angle or image scale. A matching seam is a visual check; this tool does not calculate or certify it. At a visible gap, ask whether the headline and app screen still make sense without the neighboring image.

Use the Earlier and Later buttons to review alternative reading orders. They only change the local preview. Record your chosen file order and apply it in the actual store listing; the tool does not save changes to your project or App Store Connect.

A fixed desktop mockup cannot establish the exact presentation on every device or store surface. Open the real listing preview for the target device and language. App previews can precede screenshots, so a design that relies on the first two visual slots being adjacent needs a separate check when a video is present.

Export separate files and verify the listing

Apple accepts one to ten screenshots in PNG or JPEG formats and documents the supported dimensions by device. Upload the individual screenshot files for the intended device and language. Do not upload the conceptual wide working area in place of those files.

Use the screenshot size checker for format, dimensions and transparency, then inspect the actual uploaded sequence. File validation, visual continuity and review approval are separate checks. A visually connected design is not evidence of an install increase; compare a specific hypothesis through a properly run store experiment.