App Store Screenshot Design for Indie Developers: Specs, Structure, Copy and Testing

Have you ever considered that users spend only 3 to 6 seconds on average looking at your store page before deciding whether to download?

Yes, just 3 to 6 seconds. In that time they glance at your icon and title, and then (here's the key part) they quickly swipe through your screenshots.

Industry figures commonly cited say that over 70% of users decide whether to download based on screenshots. Your screenshots are a silent salesperson, one that works 24/7 and never has a bad day.

But what's the reality? What do most indie developers' screenshots look like?

Grabbed from the simulator at the last minute, a few words slapped on, possibly not even in the right format. Then published. And then the developer wonders: my app is rated 4.8, has more features than competitors and decent retention, so why won't downloads grow?

The answer is very likely hiding in those 10 screenshots.

In this article I'll cover App Store screenshots for indie developers from the underlying logic to the practical details. You don't need to be a designer or spend a lot of money; just follow my framework and you can produce a competitive set in 1–2 days.

---

1. Hard requirements first

Let's start with the non-negotiables, because no matter how good your design is, the wrong format gets rejected.

General specs

Requirement	Spec
File format	PNG or JPEG
Color space	RGB (not CMYK)
Resolution	72 DPI
Transparency	Not allowed; use a solid background
File size	Keep it reasonable; 15–20MB per image is more than enough
Number of screenshots	1–10 per display size

iPhone sizes

Display size	Pixels (portrait)	Notes
6.3-inch (required)	1206 × 2622 or 1179 × 2556	iPhone with Dynamic Island (medium display), e.g. iPhone 17, 16 Pro
6.9-inch (optional)	1320 × 2868, 1290 × 2796 or 1260 × 2736	Large Dynamic Island phones, e.g. Pro Max, Plus, Air
6.5-inch (optional)	1242 × 2688	Face ID large display, e.g. 11 Pro Max, XS Max

Good news: Apple has greatly simplified things. Under the current screenshot specifications, the only required iPhone size is the 6.3-inch Dynamic Island display; if your UI is consistent across devices, App Store Connect scales your screenshots for other iPhone sizes. Uploading a 6.9-inch set as well makes your page sharper on large phones. For a step-by-step workflow, see the 6.9-inch screenshot tutorial.

iPad sizes

Display size	Pixels (portrait)	Notes
13-inch (required if you support iPad)	2064 × 2752	iPad Pro M4/M5, iPad Air
12.9-inch (optional)	2048 × 2732	Older iPad Pro
11-inch (optional)	1668 × 2388	iPad Pro 11-inch

App preview video specs

If you make an App Preview video, the specs for large iPhones are:

Item	Portrait	Landscape
Resolution	886 × 1920 px	1920 × 886 px
Length	15–30 seconds	15–30 seconds
Frame rate	30fps	30fps
Format	H.264 .mov/.m4v/.mp4	Same

---

2. The first three screenshots decide everything

This is the most important principle in the whole article, so repeat it three times:

Your first 3 screenshots are make-or-break

Why? Because in App Store search results and on the product page, the first 3 are what users see without scrolling. Studies suggest more than 80% of users decide after seeing only the first three.

So your screenshots aren't a random lineup of features; they're a carefully designed "elevator pitch".

The three-screenshot structure

Screenshot 1: core value proposition (Hook)

This is the only screenshot that truly matters.

Users don't know who you are or what your app does yet. This image must answer two questions within 1 second:

1. What kind of app is this?
2. What will it do for me?

❌ Wrong: a splash screen, login screen or empty dashboard ✅ Right: show the moment users succeed with your app

For example:

• Habit tracker → the "30-day streak" achievement screen
• Budgeting app → a chart showing "You spent $50 less than last month"
• Notes app → search results showing "Find any note in 3 seconds"

Screenshot 2: core feature (What)

Explain further what your app does, showing the features users use most and that best show its value.

Key points:

• Show the real app UI, not concept art
• Use specific data rather than vague descriptions
• You can deliberately enlarge key UI elements

Screenshot 3: differentiator (Why)

Why you rather than a competitor? Show your unique competitive advantage here.

It could be:

• A feature only you have
• A better experience than competitors
• Strong proof points ("Chosen by 5 million users", if true)

Screenshots 4–10

If your app deserves more screenshots, continue with this structure:

#	Type	Example content
4	Feature detail	A secondary but important feature
5	Scenario	The app in a real-life situation
6	Collaboration / sharing	Multi-user interaction, social proof
7	Data security / privacy	Build trust
8	User reviews / press	Social proof
9	Cross-platform / sync	Address user concerns
10	Closing CTA	Reinforce the reason to download

---

3. Five design rules

Now that you know what to show, here's how to design it. Even if you're a pure coder, following these 5 rules will put you ahead of most competitors.

Rule 1: one message per screenshot

Each screenshot conveys one core message. Don't try to cram several selling points into one frame.

❌ Wrong: "Powerful task management + cloud sync + team collaboration + AI reminders + multi-platform support"

✅ Right: each screenshot focuses on one thing

Rule 2: less text

Your text guides the eye; it's not a product manual.

In practice:

• Headline: 3–7 words, large enough to read in a small thumbnail
• Use phrases, not full sentences
• White space is design too; too much text is as good as none

Rule 3: lead with verbs and outcomes

The brain responds to "action". Messages that start with a verb or outcome are easier to remember and share.

Compare:

• ❌ "Powerful data analysis"

• ✅ "Understand your spending in 3 seconds"

• ❌ "Offline support"

• ✅ "Works without internet"

• ❌ "Smart reminder settings"

• ✅ "Never forget a meeting again"

Rule 4: avoid photo backgrounds

Problems with photo backgrounds:

1. They easily hurt text readability
2. They look ugly when stretched
3. They bloat file size

Recommended instead:

• Solid backgrounds: in the same color family as your app icon
• Gradients: from your main color to a lighter or complementary color
• Abstract geometric backgrounds: simple shapes for depth

Rule 5: use current device frames

Don't draw phone frames yourself; use Apple's official device templates:

• Apple provides device templates for Sketch, Photoshop and Figma
• Or use an online tool such as AppShot Maker to apply frames automatically
• Make sure the frame shows a current iPhone that matches the display size slot you upload to (see device frame rules)

---

4. Copywriting

However good the design, bad copy sinks it. Screenshot copy is your first sentence to users; it must be precise, strong and persuasive.

Headlines

Format:

• 6–10 Chinese characters (or a few English words)
• Verb + core feature / benefit
• Conversational, like a person talking

What makes a good headline:

• It tells users what they get, not what the app is
• Specific numbers beat vague descriptions many times over
• It has an emotional hook

Templates:

• "[Verb] + [specific result]": Sync in 3 seconds, Clean up in 1 tap, Automatic backup
• "[Time/money] + [verb]": Save 2 hours a week, Never waste a cent
• "[User type] + [verb]": Built for busy workers, Students' top pick

Bad examples:

• ❌ "The best task management app"
• ❌ "Next-generation smart assistant"
• ❌ "Next-generation AI-powered productivity tool"

These are empty; users read them and learn nothing.

Subtitles

Subtitles add supporting detail, giving the headline credibility or specifics.

✅ Format: "Headline · subtitle"

• "Sync in 3 seconds · 50 file formats supported"
• "Clean up in 1 tap · Free up 10GB of storage"

Copy to avoid

Avoid	Why
"Best", "most powerful"	Unverifiable; sounds like bragging
"No. 1"	No source to back it up
"Free"	Breaks trust if the app has in-app purchases
Full sentences	Users don't read them
Jargon	Your target users may not understand it
Pricing	Apple's guidelines say metadata shouldn't include prices

Test your copy

You don't have to get it right first time. Prepare 2–3 copy versions and test them with Apple's Product Page Optimization.

Metrics for judging copy:

1. Conversion from "product page view" to "Get"
2. Whether users keep swiping after the first screenshot

---

5. Color and layout

Color doesn't need artistic talent, just logic. Here's a repeatable method.

Take colors from your icon

The simplest, safest color scheme: pull colors from your app icon.

Steps:

1. Use an eyedropper to pick 2–3 main colors from your icon
2. Use the main color for the background or headline text
3. Use lighter variants for background gradients
4. Use a contrasting color for CTAs or highlighted text

Contrast

This is the most overlooked detail with the biggest impact.

On a phone, text is shrunk a lot. Without enough contrast, it can't be read.

Standard:

• Light background + dark text (black on white, or dark blue/green on white)
• Dark background + light text (white on dark blue)
• If the background has a pattern or texture, add a text shadow or a semi-transparent box behind the text

Quick test: shrink the screenshot to about 100×200 pixels. If you can still read the text, it passes.

Layout hierarchy

A standard screenshot should have these layers from top to bottom:

┌─────────────────────────┐
│  [Top margin – ~8%]      │  Avoid system UI overlap
├─────────────────────────┤
│                         │
│  Headline                │  Largest size, core selling point
│  (48–60pt)              │
│                         │
├─────────────────────────┤
│                         │
│                         │
│     App screenshot       │  Real feature UI
│     (60–70% of height)   │
│                         │
│                         │
├─────────────────────────┤
│                         │
│  Subtitle / caption      │  Supporting info, smaller size
│  (24–30pt)               │
│                         │
├─────────────────────────┤
│  [Bottom margin – ~8%]   │  Safe area
└─────────────────────────┘

Color tools

You don't need color theory; these tools do the work:

Tool	Use	Cost
Coolors	Smart palette generation	Free
Material Design Palette	Google's color system	Free
Tint	Extract palettes from images	Free basic plan
Figma / Sketch	Use directly while designing	Figma has a free plan

---

6. Tools and workflow

Now you know what to make and how. Next: which tools. Here are recommended combinations by workflow stage.

Step 1: get high-quality source screenshots

1. Device screenshots
   • Capture on a real device at its native resolution
2. Xcode Simulator screenshots
   • Simulator screenshots are at the simulated device's native pixel size, so they're perfectly usable; use the latest Xcode
   • Pick the device that matches your target size (e.g. a 6.3-inch or 6.9-inch model)
   • Clean up the status bar first (see the status bar cleanup guide)
3. Set up the content
   • Use realistic data with no private information
   • Get the app into its "best state" before capturing
   • You can prepare several screenshot templates

Step 2: online screenshot generators

Tools such as AppShot Maker and AppLaunchpad all work in much the same way:

1. Upload your source screenshots
2. Choose a template / frame style
3. Add headline text
4. Export all sizes in one go

Step 3: design tools for more control

If you want more customization:

Tool	Best for	Cost	Learning curve
Figma	Full design workflow	Free (basic)	Medium
Canva	Quick templates	Free / paid	Low
Photoshop	High-end custom work	Subscription	High

Advice for indie developers: start with an online generator to ship quickly, then learn Figma for finer designs when you have time.

Official device templates

Apple's developer site provides device templates:

• Design Resources – Apple Developer
• Includes the latest iPhone/iPad device frames for Sketch, Photoshop and Figma

---

7. App Preview videos

App Previews are optional, but they can work even better than screenshots.

Pros and cons

Pros:

• Show a complete usage flow in 3–5 seconds
• Motion grabs attention more than static screenshots
• Previews autoplay (muted) in search results and on the product page
• Commonly cited studies say apps with video convert 20–30% better on average

Cons:

• Higher production cost (time/money)
• More technically demanding than screenshots
• Done badly, it backfires (makes the app look rough)

Should you make one?

App type	Recommendation
Complex interaction (design, notes, editing)	Strongly recommended
Games	Strongly recommended (gameplay sells; not required by Apple)
Utilities (cleaning, backup, translation)	Recommended
Pure content (reading, news, music)	Optional
Social	Strongly recommended

Three ways to make one

Method 1: screen recording + editing

1. Record the screen with QuickTime or CapCut
2. Edit down to 15–30 seconds
3. Add simple captions and background music

Method 2: Keynote/PowerPoint animation export

1. Build a sliding demo in Keynote
2. Use Keynote's video export
3. Add music

Method 3: dedicated tools

• Screen Studio (Mac) can automatically generate polished app demo animations

For details, see the App Store preview video guide.

The first 3 seconds

Users decide within the first 3 seconds whether to keep watching.

Show in the first 3 seconds:

• The app's core value
• The most exciting feature moment
• No build-up or loading screens

Suggested structure (30-second example):

• 0–3s: core selling point (hook)
• 3–12s: main feature demo
• 12–20s: secondary features / highlights
• 20–25s: user reviews / proof points
• 25–30s: brand logo + call to action

---

8. Localization

If your target market isn't just one country, localization matters.

Style preferences by market

Market	Preferred style	Notes
US / English markets	Clean, big text, high contrast	Like one direct line stating the benefit
Japan	Information-dense, cute elements	Can carry more selling points, but needs high-quality Japanese
Korea	Vivid colors, design-forward	Screenshots should be polished, with a K-style feel
Germany	Rigorous, professional, feature-focused	Emphasize technical details and quality
Southeast Asia	Value-focused	Emphasize free / affordable
China	Down-to-earth, conversational	Memes and stickers work, but avoid sensitive content

Localize, don't just translate

Localization isn't translation; it's re-creation.

For the same feature, Chinese and Western users care about different things:

• Chinese users: emphasize "saves time", "costs nothing", "convenient"
• Western users: emphasize "privacy and security", "data backup", "efficiency"

So don't just run copy through a translation tool:

• ❌ A literal rendering of 一键清理垃圾文件 ("one-key clean rubbish files")
• ✅ "Clear junk files in one tap"
• ✅ "Say goodbye to storage stress"

Minimum localization for indie developers

As an indie developer, aim for at least these three versions:

1. Chinese: Simplified for mainland China (Traditional is a separate localization for Taiwan and Hong Kong)
2. English: the US, UK, Australia and other English-speaking countries
3. Japanese: Japan (high ARPU)

In practice:

• Use translation tools to help, but have a native speaker polish the text
• On no budget, localizing just the first 3 screenshots is enough to start

---

9. A/B testing with Product Page Optimization

Once your design is done, how do you know it's actually good?

There's only one answer: test it.

Setting up a test

App Store Connect has an official A/B testing feature called Product Page Optimization (PPO).

How to set up a test:

1. Sign in to App Store Connect
2. Select your app → Product Page Optimization in the sidebar
3. Create a new test (up to 3 treatments)
4. Upload your treatment assets (your new design)
5. Choose the traffic proportion shown to treatments

What you can test:

• Screenshot design / layout
• App icon (alternate icons must be included in your app binary)
• App preview videos

(App name, subtitle and promotional text can't be tested with PPO.)

Test ideas

Goal	Example variables
Copy style	A: "Clean up in 3 seconds" vs B: "Your phone, fast as new"
Visual style	A: solid background vs B: gradient background
Screenshot order	A: features first vs B: social proof first
Device frames	A: with frames vs B: plain screenshots

How long to run it

Minimum	Recommended	Notes
7 days	14–30 days	You need enough traffic for statistical significance

Rules of thumb for significance:

• Your app should get at least 500–1,000 impressions a day
• Run the test for at least 14 days
• Apple recommends waiting until a treatment reaches at least 90% confidence before applying it

Reading results

1. Look at confidence intervals: don't just look at the point estimate; check whether intervals overlap
2. Focus on the core metric: not taps, but "view → download" conversion
3. Segment: results can differ by market, device and traffic source
4. Don't over-test: change only 1–2 variables at a time, or you won't know which one worked

---

10. Common mistakes

Finally, the mistakes I see most, with the worst consequences.

Mistake 1: showing prices in screenshots

• Apple may reject it
• Users dislike feeling "sold to"
• Prices change, which adds maintenance

Mistake 2: low-quality or outdated frames

• Insufficient resolution
• Poor-looking frames
• Signals to discerning users that you didn't take it seriously

Mistake 3: leaking private information

• No phone numbers, real names or bank card numbers in screenshots
• Even if it's your own account, use fake data

Mistake 4: ignoring iPad

• iPad users often have higher spending and retention
• If your app supports iPad, dedicated iPad screenshots can noticeably lift conversion

Mistake 5: leading with a feature list

• In 3 seconds users need "why download", not "what features"
• Feature lists belong in screenshots 4–8

Mistake 6: inconsistent style

• Keep visuals consistent
• Use the same background colors, fonts (see our free Hei sans-serif fonts) and color scheme
• Make users feel they're watching consecutive frames of one story

Mistake 7: vague headlines

• "Next-generation smart assistant" → users don't know what it does
• "Find any note in 3 seconds" → users instantly see the value

Mistake 8: never updating

• Whenever your app has a major UI redesign, update your screenshots too
• Outdated screenshots make an app look abandoned

---

11. Checklist

I know this article is a lot to take in. Here's a checklist you can act on directly.

Before submitting

• Correct sizes: 6.3-inch iPhone set (1206×2622 or 1179×2556); 6.9-inch (1320×2868) optional
• Compliant format: PNG/JPEG, RGB, no transparency
• Core value in the first 3: not a login page, not a feature list
• Headlines ≤7 words: conversational, verb-first
• Readable text: legible even as a small thumbnail
• Consistent backgrounds: solid or gradient
• Current device frames: matching the display size slot
• No private information: no real user data in screenshots
• No pricing: avoid rejection

To check your files against store specs, use the screenshot compliance check.

Localization

• Chinese screenshots
• English screenshots
• Japanese screenshots (optional but recommended)

Optimization

• Set up an A/B test
• Collect 2 weeks of data
• Iterate based on the data

---

Conclusion

App Store screenshots are the growth lever indie developers most often overlook, yet they offer the best return on effort.

A week spent building a new feature might lift conversion by 5%. But there are plenty of cases where 1–2 days spent improving screenshots lifted conversion by 20–50%.

This isn't about gaming the system; it's about taking seriously the touchpoints that really shape users' decisions.

Your users deserve to see the best of you.

---

Resources:

• Apple screenshot specifications: developer.apple.com/help/app-store-connect/reference/app-information/screenshot-specifications
• Apple design resources: developer.apple.com/design/resources
• App Store Connect (A/B testing): appstoreconnect.apple.com

---

If this article helped, feel free to share it with other indie developers.