VPN App Screenshots That Survive App Store Review

A reviewer is a tired human with a checklist and a device. They open the listing. If the first three screenshots look like a different product than the binary, you have already spent goodwill. VPN is a sensitive category. You inherit the industry's junk: fake cleaners, 'unlimited speed' banners, maps that lie.

Your job is to look like a tunnel app. Connect button. Location list you actually have. Settings that exist. A privacy screen that matches what you tick in App Privacy. Boring wins.

PowerCert's explainer is useful for non-engineers who still think a VPN is a pirate hat. It will not design your 6.7-inch iPhone set. Apple's Packet Tunnel Provider docs will not either. They will remind you the product is a packet tunnel, not a lifestyle magazine.

Shoot the build you will submit. Not last month's staging. Not Figma. If kill switch is behind a paywall, do not lead with it as if it is free. If you have three locations in the picker, do not show a globe with pins on every continent.

Order them like a user story: what it is, connect, pick a place, settings that matter (protocol, kill switch if it exists), account without real PII. Five to eight images. More is not more if image four is a testimonial wall of five-star PNGs you invented.

Device size sets are a tax. iPhone 6.7, 6.5, iPad 13, iPad 12.9 — App Store Connect will tell you what is required this month. Do not crop a phone shot into an iPad slot and hope. It looks like a lie because it is one.

Apple's App Privacy labels are a form. Screenshots are a second form you did not mean to file. If the glass says 'we collect nothing' in a custom badge, and the App Privacy form lists crash logs and email, you handed the reviewer a contradiction.

Do not draw a fake nutrition label. It collides with system UI and looks like you are impersonating Apple. If you want a privacy screenshot, capture the real in-app disclosure — the one Guideline 5.4 wants before purchase or use — with readable type.

Play Data safety is the same trap. Feature graphic that says 'zero data' next to a form that lists account info is how you earn a policy letter.

I have a low opinion of VPN speed screenshots. They are usually a speed-test site on fast Wi-Fi with the VPN off, or on a nearby exit with a caption that implies every city is like that. Users will test the far exit on hotel Wi-Fi and one-star you. Reviewers may not run iperf. They can still smell a 940 Mbps overlay on a product that never shows a speed graph in-app.

If your app does not include a speed test, do not screenshot a third-party test as if it were a feature. If it does include one, show it without a marketing ribbon that claims you beat a named competitor. 2.3.7 does not want you using the listing to punch other apps.

I linked a big consumer VPN's marketing site as an example of the theater culture. Do not clone it. Their ads are not your review notes. Rel is sponsored on purpose: that is their promo, not our endorsement.

Designers love huge white text on a blurred phone: '$2.83/mo', '7-day money-back', '5 devices'. Those facts are real for Klox consumer. They still do not belong as screenshot chrome. Apple's rule is that screenshots should not include prices, terms, or descriptions that are not specific to the metadata type. Put price in the IAP or the website. Put devices in the description if you must. Keep screenshots as UI.

Competitor names in overlays are a tell. So are 'No. 1 in [country]' medals. Unverifiable claims are how 2.3.7 and 2.3.10 get involved. I would rather a listing look quiet than look like a landing page stuffed into a PNG.

If you localize the listing, localize the screenshots or admit they are English. A German description over English UI is common and a little sad. A German description over English screenshots with English overlays is worse. Reviewers in that storefront live there.

Do not run the UI through a cheap translator and shoot it. 'Kill switch' becoming something that sounds like violence in another language is a support problem and a rating problem. Use a translator who has seen a VPN app.

If you only have budget for English, stay in English. A smaller honest footprint beats ten locales of nonsense. You can add locales when the binary strings are actually translated.

App previews are optional until marketing insists. If you shoot one, show the real connect flow, including the system VPN permission dialog. That dialog is the product. Do not hide the permission to make the preview look slick. Users will see it anyway.

Do not dub fake speed numbers. Do not show a map animation of cities you cannot serve. Fifteen seconds of a thumb hitting connect and a status flipping to on is enough. I would rather a quiet preview than a trailer with whooshes.

Play's feature graphic is 1024×500 of temptation. Padlocks, globes, anonymous hoodies. You look like 200 other listings. Shoot the product. Icon should not clone a competitor's mark. That is trademark and 2.3 uniqueness.

Guideline 2.3.8: metadata should be appropriate for all audiences at 4+ even if the app rating is higher. No gore, no sexy 'spy' art. VPN brands drift into trench-coat noir. Skip it.

You are responsible for rights to every pixel. That includes fonts, illustrations, and the fake map tiles. If a contractor grabbed Unsplash and a font they did not license, you own the takedown.

Device farm or a current iPhone and Pixel. Production-bound build. Fake account with a password in 1Password for review. Clean status bar.

Shots: (1) home disconnected, (2) system permission if you can capture it legally in a preview, (3) connected, (4) location list that is true, (5) protocol picker if you have WireGuard, OpenVPN, OpenConnect, and Shadowsocks toggles, (6) kill switch if it exists, (7) in-app privacy disclosure, (8) help or settings without debug. Stop.

Export at the exact pixel sizes App Store Connect and Play Console demand this quarter. I will not freeze a pixel chart here; the consoles change. Look it up the day you export.

Then sit with the person who filled App Privacy and Data safety. Flip through the PNGs. Any contradiction dies now, not in review.

If you only have one device, shoot that device well. A sharp Pixel set plus a missing iPad set is a known submit blocker, not a style choice. Borrow hardware. Do not upscale. Reviewers have seen upscaled UI; it looks like oil on water. If a contractor delivers 'iPad' screenshots that are phone UI with fake bezels, send them back. You will still be the developer of record when Apple shrugs.

Pick a freeze day. Binary locked. Strings locked. Then recapture. I do not trust screenshots from two sprints ago. A connect button that moved 12 pixels is enough for a reviewer to feel baited. Export every required size the same afternoon. Name files like `ios-67-01-home.png` so a tired person can upload without guessing.

Sit with App Privacy and Data safety open. Flip the set. If image two implies 'nothing collected' and the form lists email plus crash logs, kill the overlay. If a German listing is going live, check that you did not upload the English set to that locale by habit. Console UIs make that mistake easy.

Then watch the preview video on a phone speaker, muted, then with captions. If the system VPN dialog is cropped, recut. If a notification from your bank floats in the status bar, recut. I have failed my own QA on that. It is cheap to fix at the desk and expensive in review.

Budget two hours, not 'the designer will handle it.' Designers optimize for conversion. Reviewers optimize for consistency. You need both in the room, or you need one person who is allowed to veto a speed graph.

Confirm who exports screenshots. If the platform gives you a default set, treat it as a draft. Replace city counts you cannot defend. Replace their name. Replace any speed theater they included for 'conversion.'

You still submit. You still own 2.3. A vendor link in review notes does not excuse a lying PNG.

If you do not want this job, resell Klox and send people to our listings. That is a valid motion. It is not a lesser motion. It is how you skip the shot list.