The fastest way to make App Store screenshots

You ship tomorrow. You need screenshots. This post is not going to talk you into a considered design process.

Here is what each route actually costs in wall-clock time, honestly, including ours — which is not the fastest and we are not going to pretend it is.

The clock

Route	Time to files	Time if you have done it before
Raw captures, uploaded as-is	20 min	10 min
Captures + a template tool	45–90 min	25 min
Fastlane (already set up)	10 min	5 min
Fastlane (from scratch)	half a day	—
Canva or Figma by hand	3–6 hours	90 min
Generated art direction	30–60 min	20 min
A designer	days to weeks	—

The interesting rows are the first and last of the middle block: Fastlane is the fastest thing on the list if you already run it, and a catastrophic choice if you are installing it tonight.

If you need files in the next hour

Do this, in this order, and skip anything else:

1. Seed your app with real-looking data. Ten minutes. This is not optional even under time pressure — an empty app screenshotted beautifully still sells nothing, and it is the single biggest difference between a rushed set that works and one that does not.
2. Lock the status bar. One command: xcrun simctl status_bar booted override --time "9:41" --batteryState charged --batteryLevel 100 --wifiBars 3 --cellularBars 4.
3. Capture three screens, not eight. The first two carry nearly all the weight. A tight set of three beats a rushed set of eight, and it is under half the work.
4. Decide what panel one says before you design anything. One sentence, the outcome, in the user's words. This costs two minutes and is worth more than everything below it.
5. Add captions and export at exact sizes. Whatever tool is nearest.

That is genuinely a good listing. Not a great one — a good one, in an hour.

What to skip when you are in a hurry

• Every display class. Ship 6.9-inch iPhone. Apple derives the rest. Add iPad only if your app supports it.
• Localization. English first, translate when the listing has earned it.
• Landscape. Unless your app is genuinely used that way.
• Panels four through eight. Nobody is swiping that far on day one.
• The feature graphic — unless you are on Play, where it is required to publish.

What never to skip

If you hit the dimensions error anyway, the fix is here and takes about two minutes.

Where the time actually goes

Watch someone do this and the clock is almost never spent where they expected:

• Capture and cleanup: 60%. Permissions, first-run overlays, empty states, recapturing because a dialog appeared in frame four.
• Deciding what to say: 25%. Staring at a blank caption field is the real bottleneck, and no tool removes it.
• Actual design: 15%.

Which means tool choice affects the smallest slice. If you want to be faster next time, the leverage is in making capture repeatable — a launch-argument hook that drives your app to a named screen turns a forty-minute capture session into a script you run in ninety seconds.

Being fast the second time

The first set is always slow. What matters is whether the second one is.

That is really the difference between the routes above: raw captures and template tools are fast once and just as slow again. A pipeline — Fastlane, or ours — is slower the first time and close to free afterwards, because changing a caption means re-rendering rather than re-doing.

If you are going to test your first screenshot, and you should, that second-time cost is the only number that ends up mattering.