I Wasted 3 Days Building App Store Screenshots in Figma. Then I Found a Faster Way.
Building App Store screenshots in Figma ate days of my week. Here's where the time goes — and the faster way I rebuild a full localized set in minutes.
It was a Tuesday when I realized I'd spent three full days making ten images.
Not designing them — that part took an afternoon. The other two-and-a-half days went to the machinery around the design: resizing for every device, re-flowing text that overflowed the 6.9" frame, exporting the right dimensions, then doing it all again for three languages. I love Figma. But somewhere in there I stopped being a founder shipping an app and became a human export script.
If you've ever tried to create App Store screenshots in Figma, you already know the feeling. Here's exactly where the time goes — and the faster way I rebuild a full set now.
How do you make App Store screenshots in Figma?
The honest version of the workflow looks like this:
- Set up a frame at the right pixel size for each device class.
- Drop in a device mockup, place your screen capture, add a headline and background.
- Duplicate the frame for every other size and nudge everything back into place.
- Re-flow any headline that no longer fits the new aspect ratio.
- Export each frame at the exact dimensions the App Store demands.
- Repeat 1–5 for every language you localize into.
None of those steps is hard. That's the trap. Each one is easy and slow, and there are dozens of them. Figma is a brilliant design tool — but App Store screenshot production isn't really a design problem, it's a logistics problem wearing a design tool's interface.
What size should App Store screenshots be in Figma?
This is where most of my "wait, why isn't this approved?" time went. Apple expects exact dimensions per device, and they change as new phones ship. Getting a single number wrong means a rejected build and another round trip.
I stopped hand-managing this entirely. Now I keep the spec in one place and let a tool handle the exports — our free Screenshot Size Converter takes one master and produces every required size, so "what size should this be?" is no longer a question I answer manually. (If you only need the chart, that tool page lists the current 2026 dimensions.)
How long does it actually take?
For a polished, localized set the honest number was 2–3 days of elapsed time when you count the export-and-fix loop and the waiting in between. The design was hours; the production was days. That ratio is the whole problem. You're spending your most expensive time on your least creative work.
Is there a faster way than Figma for App Store screenshots?
Yes — and the unlock was not starting from a blank Figma frame. Most of the work I was doing by hand already existed in my live listing.
I paste my App Store URL into Reverze's AI Screenshot Rebuild. It reads my current screenshots — the layout, the visual hierarchy, the messaging — and rebuilds the whole set into an editable campaign. From there I adjust the directions I like, and every device size and language comes out at once instead of frame-by-frame. The two-and-a-half days of machinery collapse into an afternoon I actually control.
The pieces that were genuinely useful in Figma — placing a clean device frame, getting sizes right — are now just tools I reach for when I need them: the Device Mockup Generator for a quick frame, the Size Converter for exports. I didn't lose the capability. I lost the busywork.
Should you stop using Figma?
No — and I want to be honest here, because the "Figma is dead" takes are nonsense. Figma is still where I'd go to invent a brand-new visual concept from scratch, or to do pixel-level craft on a hero frame. What changed is that I stopped using it as a production line for resizing, re-exporting, and localizing the same layout over and over. That part was never a good use of a design tool, or of my week.
If you want the deeper version of this — what happens when you hand the entire production layer to AI, and what you gain and lose — I wrote about that in how I replaced my designer with AI.
Try it on your own listing
The fastest way to feel the difference is to run your own app through it. Paste your App Store URL into Reverze's AI Screenshot Rebuild and watch your current screenshots come back as an editable, every-size, every-language set in minutes — then go spend those three days on your actual product.
Reverze turns App Store creative production from a multi-day workflow into minutes — paste a URL, rebuild your screenshots, generate new directions, and export production-ready assets. Explore the free tools or start in the app.