Figma App Store Screenshot Template: 3 Free Picks + Setup Guide (2026)

TL;DR. A free Figma App Store screenshot template (Max Rudberg, Harsh Shah, or Median.co's 500+ pack) gets you the right device frames in 30 seconds. But per AppLaunchpad's published numbers, the realistic floor for a first-language Figma build is 3 to 4 hours, plus 30 to 40 minutes per added language. The hidden trap is sizes: design at 6.9" 1290×2796 (or 1320×2868 for iPhone 17 Pro Max) and let Apple auto-scale, because Apple's current spec page treats 6.5" as fallback-only and several popular community templates still ship deprecated frames labelled "current." If you ship one language and want full editability, Figma wins. If you ship five or more languages, the export-and-localize math tips toward URL-to-designs tools.

Last updated: 2026-06-08.

Disclosure. ScreenFast is the article's author and appears in the comparison table near the end. We position ScreenFast by intent (URL-to-designs, $9.99), not by ranking. The Figma walkthrough below is unaffected by that fact and is the honest fastest path through the Figma route.

What a Figma App Store screenshot template actually gives you (and what it doesn't)

A Figma template solves the boring half of the job: the right device frame at the right pixel size, the right layer structure, and usually a few pre-built variables for text color, background, and theme. That is genuinely useful, and it is why "figma app store screenshot template" is a top-3 search for indie iOS devs every quarter.

What it does not give you: the copy, the brand styling, the per-language exports, the iPad variants if your app is Universal, or any guarantee the export will pass App Store Connect. The "30 minutes" promise you see in some tutorials is real only if you already have the copy written, the brand colors set, and the source screenshots cleaned. From a cold start with raw simulator captures, AppLaunchpad's own breakdown quotes 3 to 4 hours for the first language and 30 to 40 minutes per added language. We are taking their numbers at face value because they have no incentive to make the Figma path look worse than it is. They sell against it.

The honest reframing: a Figma template saves you from re-creating the wheel. It does not save you from designing.

Three free Figma templates worth starting from (verified)

We verified every template URL below by checking Google's index and the creator's own pages. Figma blocks anonymous fetches with an AWS WAF challenge, so we cannot quote per-template duplicate counts unless they appeared in a public SERP snippet. Where a number is not visible, we say so rather than invent one.

iOS / iPadOS / visionOS App Store Template by Max Rudberg

File 1288121980561553565. The broadest device-class coverage in a single free file we found: iPhone 15 Pro frames, iPad in portrait and landscape, the legacy Home-Button frames Apple still accepts, plus a visionOS App Store mockup. Public Google index shows 444 duplicates and 23.4k users in the SERP snippet, which is the only template in our shortlist with engagement numbers visible outside Figma's login wall.

Best for: apps shipping on iPhone + iPad + Vision Pro from one file.

App Store Screenshot Template by Harsh Shah

File 1198162612398400646. The simplest first-touch template in the set. Free, focused, low cognitive load for an indie who has never opened a screenshot template before. Third-party freebie aggregator figmafreebie.com records 9,459 views and 1,418 downloads (source). Those are third-party stats, not Figma's own duplicate count, and we flag them as such.

Best for: first time using a Figma template, single iPhone tier, one or two languages.

500+ App Store screenshot templates (Android and iOS) by Median.co

File 1471925742378558731. Explicitly covers iPhone, iPad, Android smartphone, and Android tablet device frames in one file, compatible with both Apple App Store and Google Play Store listings. The right pick if you ship the same app to both stores and do not want to maintain two parallel template trees.

Best for: cross-platform indie shipping iOS and Android in the same release cycle.

For coverage of the rest of the App Store screenshot tool category, see the 2026 generator roundup.

Apple's 2026 screenshot specs you must hit (cited)

Every claim below is from Apple's App Store Connect screenshot specifications page, confirmed across two fetches. Apple's page is JS-rendered with collapsible tables, so values are quoted as they appear in the rendered text.

Three things the page says verbatim that get re-quoted wrong elsewhere:

1. Accepted formats: .jpeg, .jpg, .png. No other formats listed.
2. Count: "You must upload one to ten screenshots." The widely-cited "minimum 3" figure is a UI guideline, not Apple's spec.
3. Auto-scaling is explicit. If you only upload the largest tier per platform (6.9" for iPhone, 13" for iPad), Apple scales down to the smaller tiers automatically.

Three things the page does NOT say (do not fabricate them):

• No color-space requirement. sRGB versus Display P3 is not on the spec page. Treat any color-space "rule" as a convention, not a documented spec.
• No per-file MB cap. The page documents pixel dimensions, formats, and counts. No file size limit is published.
• No standalone 6.7" tier. Apple consolidated the old 6.7" Pro Max (1290×2796) under the new 6.9" tier and kept 1284×2778 under 6.5". If your Figma template is still labelled "6.7"," relabel before handing it to someone else.

For the sibling deep-dive on sizes, see the full App Store screenshot sizes reference.

Step-by-step: from raw simulator screenshot to a placed Figma frame

This is the workflow that survives the export step. Five moves.

1. Capture in simulator at native resolution. Use Xcode Simulator. Cmd+S saves the PNG to your Desktop at the simulator device's native pixel size. Do this on the device tier that matches your largest target slot (iPhone 16 Pro Max if you have it set up, otherwise iPhone 15 Pro Max).

2. Transfer via Photos app or USB, not AirDrop. AirDrop converts iOS source assets to JPEG/sRGB before they leave the device, silently downgrading from Display P3 wide gamut. If you want the OLED-vibrant colors to survive, use Image Capture, the Photos app sync, or USB transfer. This is documented in Max Burnside's Figma-quality breakdown.

3. Create the frame at 1290×2796 (or 1320×2868). In Figma, the frame IS the deliverable. Do not author at a smaller size and rely on @2x export. Type the dimensions into the Frame panel directly. Confirm the frame X/Y is at integer coordinates (more on this in the export checklist).

4. Apply the screenshot as an Image fill, not drag-and-drop. This is the single most missed step in beginner tutorials. If you drag a raw PNG onto the canvas, Figma rasterizes the image at its displayed size and caps the resolution forever. Instead: select the inner rectangle, open Fill, click the image picker, and choose your source PNG. Figma keeps the full-resolution source in the background and only downsamples at export time.

5. Crop via "Clip content" on a frame, never Figma's Crop tool. Figma's built-in Crop mode downsamples then upscales the cropped region by about 0.5× then 2×, producing a visibly blurry result on export. This is a confirmed Figma forum bug. The workaround: place the image inside a frame, enable "Clip content" on the frame, and resize the frame to crop. Never touch the Crop tool for assets bound for the App Store.

If you want a video walkthrough of essentially this flow, How to Create App Store Screenshots - Fast & Easy using Figma by Samik Choudhury (December 2025) covers the template-fill, logo upload, and corner radius steps in roughly the order above.

Export checklist that survives App Store Connect

Five non-negotiables before you upload.

1. Integer coordinates. Select every frame and child. Round all X, Y, W, H to integers. The "Snap to pixels" setting alone does not retroactively fix decimals already placed. A frame at X=130.02 exports the artboard at 1291×2797 instead of 1290×2796, and App Store Connect rejects it with "Screenshot dimensions are not valid for this device type." This is the sub-pixel export bug Figma's own forum confirmed.

2. Export at 1x scale. In Figma's Export panel, set PNG or JPG to 1x. Not @2x, not @3x. The frame is already authored at native pixel dimensions. Exporting @2x produces a 2580×5592 file, which is instantly rejected.

3. No alpha channel. Figma's default PNG export is 32-bit RGBA with an alpha channel. Apple's Transporter and App Store Connect reject these with error ITMS-90647: "Invalid Image Asset. The image asset can't be transparent or contain an alpha channel." Visually the image looks fully opaque, which is why nobody notices until upload fails. Figma has no native "export PNG without alpha" toggle. Three fixes that work: (a) export as JPG instead, (b) re-save the PNG through macOS Preview with the Alpha checkbox unchecked, or (c) install the "Export Opaque PNG" community plugin.

4. Display P3 color profile (optional but worth setting). In Figma's export settings, set Color Profile to Display P3 so your screenshots match the native iOS capture color space. Default is sRGB, which renders duller on iPhone OLED than P3-correct competitors. Apple does not publish a P3 requirement, but matching the source space is the conservative choice.

5. Versioned filenames to dodge the IMAGE_TOOL_FAILURE cache trap. Apple's ingestion caches by filename. If you upload hero-1.png, get rejected, fix it, and re-upload hero-1.png, you can hit IMAGE_TOOL_FAILURE even though the bytes are different. Rename to hero-1-v2.png and upload one screenshot at a time with a small pause between. Apple Developer Forums has documented this bug for over a year without a platform-side fix.

Five Figma anti-patterns that get your screenshots rejected

The five mistakes from the field that account for most "I followed the tutorial and Apple still rejected me" threads.

Anti-pattern 1: Default Figma RGBA PNG export. Triggers ITMS-90647. Fix above.

Anti-pattern 2: Sub-pixel coordinates from old templates. Triggers "dimensions not valid for this device type." Many free Figma community templates ship with one or two child elements sitting at fractional X/Y left over from an older device redesign. Round everything before export.

Anti-pattern 3: Designing on deprecated 5.5" 1242×2208 (iPhone 8 Plus) frames. Several Figma community templates still bundle 5.5" labelled as a 2026 size. As of 2024 and later, Apple no longer requires this tier. Localizing 10 languages × the dead size wastes a half day. Skip the 5.5" frames unless your app targets pre-iOS 13 devices, which essentially nothing does.

Anti-pattern 4: 6.5" 1284×2778 as your only iPhone slot. The 6.5" tier is now fallback-only on Apple's spec page. The 6.9" tier (1290×2796 or 1320×2868) is the slot Apple anchors auto-scaling to. If you upload only 6.5", the smaller-tier devices will look fine, but the 6.9" preview will be visibly upscaled.

Anti-pattern 5: "One or more screenshots are in the wrong format." Triggered by 72 vs 144 DPI metadata mismatch, or by a double extension in the filename (screen.jpg.png). The fix per Apple Developer Forums is to re-export at native pixel dimensions at 144 ppi explicitly, or convert PNG to JPG through Preview's Export As dialog.

Figma template vs drag-drop tools vs ScreenFast: honest comparison

This is the disclosure section. ScreenFast is the article's author. We show the comparison by intent (which tool fits which workflow), not by ranking. Numbers for the Figma column come from AppLaunchpad's published 3-to-4-hour floor and 30-to-40-minutes-per-language figure, which is the most credible third-party measure we found because they have no incentive to make Figma look slower than it is.

How to read this table:

• If you ship one language and want full editability, Figma wins. The 3-to-4-hour cost is real but recoverable; the file is yours forever.
• If you ship two to four languages and value the comparison shopping in the design phase, a drag-and-drop tool like AppMockup splits the difference: faster than Figma, more flexible than ScreenFast.
• If you ship five or more languages, the per-language Figma re-export pass becomes punishing, and the AI-generation tools (including us) win on time even at $9.99.
• If you are the kind of developer who is going to redraw the brand from scratch anyway, a drag-and-drop tool's locked layout will frustrate you. Stay in Figma.

For the head-to-head ScreenFast comparison of a similar free tool, see our Hotpot.ai screenshot review. For the multi-language depth, see localizing App Store screenshots to 16+ languages.

FAQ: the questions you Google after your first failed upload

Does Apple still require a 6.5-inch screenshot, or just 6.9-inch?

Per Apple's current screenshot specifications page, the 6.9" tier (1320×2868, 1290×2796, 1260×2736) is the primary slot and Apple auto-scales it down to smaller tiers. The 6.5" tier (1284×2778) is still listed but is fallback-only. If you only upload one tier, make it 6.9".

Why does App Store Connect reject my Figma PNG even though it looks fine?

Almost certainly one of two things: the RGBA alpha channel (error ITMS-90647) or a +1 pixel sub-pixel export. For alpha: re-save through macOS Preview with Alpha unchecked, or export as JPG instead. For sub-pixel: round every frame and child to integer X/Y before export.

What's the minimum number of screenshots Apple requires?

Apple's spec page says verbatim "you must upload one to ten screenshots." Minimum is 1. The "minimum 3" rule you see elsewhere is a UI guideline from third-party ASO guides, not an Apple spec.

Is a free Figma community template actually faster than a paid AI tool?

Per AppLaunchpad's own published breakdown, the floor for first-language template setup is 3 to 4 hours, with each additional language adding 30 to 40 minutes. URL-to-designs tools quote under 2 minutes for the first language. Whether that gap is worth around $10 depends on how many languages you ship and how much you value full editability.

Which Figma community template should I actually start from?

For coverage breadth across iPhone + iPad + visionOS, Max Rudberg's iOS/iPadOS/visionOS template (file 1288121980561553565). For the simplest first-time use, Harsh Shah's App Store Screenshot Template (file 1198162612398400646). For cross-platform iOS + Android in one file, Median.co's 500+ pack (file 1471925742378558731). All three are free with verified Figma Community URLs.

Can I just upload 6.9-inch screenshots and skip iPad?

Only if your app does not support iPad. If the app runs on iPad, Apple requires iPad screenshots separately. The iPad Pro 13" slot (2064×2752) is canonical and gets auto-scaled to smaller iPads. Skipping iPad on a Universal app means the iPad listing shows no screenshots at all, which kills installs.

Will Figma export at the right color profile for iPhone OLED?

By default no. Figma exports sRGB and silently strips Display P3 unless you set Color Profile to Display P3 in the export panel. iOS screenshots are captured in P3, so untreated Figma output looks duller than competitors who preserved P3. Also: transfer source screenshots from iPhone via the Photos app or USB rather than AirDrop, which downgrades to JPEG/sRGB before the file ever reaches Figma.

Why does Apple reject my screenshot with "IMAGE_TOOL_FAILURE" on re-upload?

Apple's ingestion caches by filename. If you upload hero-1.png, get rejected, fix the issue, and re-upload hero-1.png, the cache can fail with IMAGE_TOOL_FAILURE even though the bytes are different. Rename to hero-1-v2.png and upload one screenshot at a time with a small gap. Apple Developer Forums has documented this for over a year.

How we tested and who we are

Sources verified live: Apple's App Store Connect screenshot specifications page was fetched twice across two passes to cross-check the 6.9", 6.5", and iPad tiers. Each of the three recommended Figma templates was verified via Google's index because Figma blocks anonymous direct fetches with an AWS WAF challenge. Engagement numbers (Max Rudberg's 444 duplicates and 23.4k users, Harsh Shah's 9,459 views and 1,418 downloads via figmafreebie.com) are quoted from SERP snippets or third-party aggregators with the source named. We did not invent any duplicate, like, or download count we could not see.

Anti-pattern claims are cited to: Figma's official forum (for the sub-pixel and Crop bugs), AppsOnAir's ITMS-90647 writeup, Max Burnside's resolution-quality breakdown, and Apple Developer Forums threads for the IMAGE_TOOL_FAILURE and wrong-format errors. Reddit-thread quotes were intentionally omitted because the search round did not surface qualifying date-bearing snippets, and we will not fabricate them.

ScreenFast is the article's author. ScreenFast generates 10 App Store screenshot designs in 4 styles from your App Store URL or your own raw screenshots, starting at $9.99 per project. The comparison table positions ScreenFast by intent (URL-to-designs, paid, bakes localization), not by ranking. If you want the full landscape, the 2026 generator roundup covers nine tools side by side. If you want the broader screenshot context, the pillar guide on creating App Store screenshots is the starting point.