How do I get client approval on App Store screenshots before submitting?

Share the screenshots in a format that lets the client mark specific spots, not just react to the whole set. A shared review link where they click the exact element and pin a note produces actionable feedback ('change the CTA copy on screenshot 3 to Book a demo') instead of vague impressions ('the third one feels a bit busy'). Get explicit sign-off on copy, device frames, and color before you upload to App Store Connect — Apple's review process can take days, and a rejected screenshot set resets the clock.

What file format should I share App Store screenshots in for client review?

PNG at the target submission size (6.9″ for iPhone, 13″ for iPad as of Apple's current requirements) is the most faithful format for review — it's what the client will approve and what the store will render. If you need all panels reviewed together, export as a PDF and number each frame. For link-based review tools, a PNG upload or a Figma embed both work; the tool renders the image at a comfortable size for browser viewing regardless of the original pixel dimensions.

Can a client comment on a Figma frame without a Figma account?

Not natively — Figma requires a free account login to submit comments, even on a view-only link. The standard workaround is to export the frames as PNGs or a PDF and share via a third-party review tool that allows guest commenting. The client sees the exported image (not the design file) and can pin notes without any account. The tradeoff: they're reviewing a flat export, not the live Figma frame — so this isn't right when they need to inspect spacing or toggle component states. For screenshot approval, a flat export is the correct artifact anyway.

How do I collect feedback from multiple stakeholders on the same set of screenshots?

Send everyone the same link rather than separate file attachments. A shared review link keeps all comments in one place — each reviewer's notes are visible to the others, and you're not reconciling three annotated PDFs with different names. If stakeholders need to leave independent feedback before influencing each other, share the link sequentially (person A first, then B) rather than simultaneously.

What's the most common mistake when sharing App Store screenshots for review?

Sharing at the wrong resolution or in a format that compresses the image. App Store screenshot reviewers need to read small headline copy and evaluate device frame crispness — a compressed JPEG or a small-scale PNG in an iMessage preview obscures exactly what they're approving. Export at full submission resolution (at least 1× the required App Store dimensions) and share via a link that renders the image at readable size, not as a compressed thumbnail.

How do I make sure the client approves the final version, not an earlier draft?

Keep all rounds on the same link rather than sending new files. When you revise the screenshots and push a new version, it replaces the draft on the same URL — the client is always looking at the current version, not an old file sitting in their email. Mark the approval explicitly in the thread ('v3 approved — submitting to App Store Connect today') so there's a clear record if a question comes up after the review.

drafty

How to get feedback on an App Store screenshot

Quick answer

To get feedback on an App Store screenshot, share the image file directly in a message (fast but produces vague feedback), export and annotate it before sending (more structured), or drop it into a review link your client opens in a browser and clicks on the exact spot they mean — no account, no back-and-forth describing which panel they're talking about. The third method is the only one that pins their note to the actual element, which matters when 'the headline feels off' could mean the copy, the font size, or the device frame color.

Step 1

Send the PNG directly for quick, informal sign-off

Export each screenshot as a PNG at 2× (or 3× for App Store submission) and share the files in Slack, email, or iMessage. This is the fastest option and works when you need a quick thumbs-up from a client you've worked with long enough that they communicate in one-liners. The weakness is specificity: a screenshot of five panels sent in an iMessage produces feedback like 'the second one looks slightly off' — which panel? the copy, the background, the device frame? You spend a follow-up call clarifying what they meant before you touch anything. For straightforward approvals on a simple, single-image set, this is fine. For a six-screenshot carousel with a client who tends to revise, it generates more round-trips than it saves.

Step 2

Export as a numbered PDF and ask specific questions

If you have multiple screenshots to review, export them as a single PDF (Figma: File → Export as PDF, or select all frames → Export → PDF), number each panel in the filename or a header note, and send structured questions alongside it: 'On panel 3, does the headline copy match your latest positioning?' Clients annotate using Preview on Mac (markup toolbar → sticky note) or Adobe Reader's Comment panel. The numbered structure reduces 'the third one, or is it the fourth?' confusion. What it doesn't solve: every round of revisions means re-exporting and re-sending, and two clients annotating separate copies of the PDF produce two sets of feedback you manually reconcile. By the third iteration you're comparing 'screenshot-v5-FINAL-JD-comments.pdf' against 'screenshot-v5-FINAL-revised-APPROVED-KC.pdf'. Works well for one reviewer; degrades fast with two or more.

Step 3

Share a review link they click to pin notes on the image

Export the screenshots (PNG or group them in a PDF), drop the file into a review tool that supports guest commenting, and send the resulting link. Your client opens it in their browser — on their phone or desktop, no account — clicks the exact panel or element they mean, and types a note pinned right there. Every comment is anchored to the spot: 'this CTA text' pinned to the button, not 'the text somewhere on the third panel' in a message. You see all notes in one thread, reply to confirm, and mark each one resolved when you revise. For App Store screenshots specifically this is the method that pays off: the image is the final deliverable, not a step toward something else. Getting precise pinned feedback before you hit Submit on App Store Connect is worth the extra minute to share a link rather than a file. Tools that support no-account guest commenting on image uploads include Drafty, Markup.io, and Ruttl.

The faster way

If your client's feedback is landing in two iMessage threads and a Google Doc, drop your screenshot export into Drafty and send the link instead. They click the exact panel they mean — the headline on screenshot 2, the background on screenshot 5 — and pin a note right there. No account. Every comment lives on one link, you resolve each one when you fix it, and the approved version replaces the draft on the same URL. One link from first draft to App Store submission.

Open a live demo

Questions

How do I get client approval on App Store screenshots before submitting?: Share the screenshots in a format that lets the client mark specific spots, not just react to the whole set. A shared review link where they click the exact element and pin a note produces actionable feedback ('change the CTA copy on screenshot 3 to Book a demo') instead of vague impressions ('the third one feels a bit busy'). Get explicit sign-off on copy, device frames, and color before you upload to App Store Connect — Apple's review process can take days, and a rejected screenshot set resets the clock.
What file format should I share App Store screenshots in for client review?: PNG at the target submission size (6.9″ for iPhone, 13″ for iPad as of Apple's current requirements) is the most faithful format for review — it's what the client will approve and what the store will render. If you need all panels reviewed together, export as a PDF and number each frame. For link-based review tools, a PNG upload or a Figma embed both work; the tool renders the image at a comfortable size for browser viewing regardless of the original pixel dimensions.
Can a client comment on a Figma frame without a Figma account?: Not natively — Figma requires a free account login to submit comments, even on a view-only link. The standard workaround is to export the frames as PNGs or a PDF and share via a third-party review tool that allows guest commenting. The client sees the exported image (not the design file) and can pin notes without any account. The tradeoff: they're reviewing a flat export, not the live Figma frame — so this isn't right when they need to inspect spacing or toggle component states. For screenshot approval, a flat export is the correct artifact anyway.
How do I collect feedback from multiple stakeholders on the same set of screenshots?: Send everyone the same link rather than separate file attachments. A shared review link keeps all comments in one place — each reviewer's notes are visible to the others, and you're not reconciling three annotated PDFs with different names. If stakeholders need to leave independent feedback before influencing each other, share the link sequentially (person A first, then B) rather than simultaneously.
What's the most common mistake when sharing App Store screenshots for review?: Sharing at the wrong resolution or in a format that compresses the image. App Store screenshot reviewers need to read small headline copy and evaluate device frame crispness — a compressed JPEG or a small-scale PNG in an iMessage preview obscures exactly what they're approving. Export at full submission resolution (at least 1× the required App Store dimensions) and share via a link that renders the image at readable size, not as a compressed thumbnail.
How do I make sure the client approves the final version, not an earlier draft?: Keep all rounds on the same link rather than sending new files. When you revise the screenshots and push a new version, it replaces the draft on the same URL — the client is always looking at the current version, not an old file sitting in their email. Mark the approval explicitly in the thread ('v3 approved — submitting to App Store Connect today') so there's a clear record if a question comes up after the review.

Keep exploring

How to get feedback on a mockup How to get feedback on a Figma design How to get feedback on a UI design Design feedback tool

Stop emailing files back and forth.

Share one link. They comment on the exact spot — no account, always the current version.

Open a live demo