Home / ASO guides / App screenshot mockups: device frames or not?

App screenshot mockups: device frames or not?

Quick answer: An app screenshot mockup places your UI inside a device frame. Frames look polished but shrink the UI, which is the part users want to see. For most apps a frameless or partial-frame layout with a big caption reads better in search. Use outdated device frames and you'll look old.

How to make a screenshot mockup

Follow these steps in order. Each one is something we do on client work.

  1. Capture clean screens. Demo data, full battery, clean status bar.
  2. Choose framed or frameless. Frames date quickly; frameless is simpler.
  3. Add a caption. Five words or fewer.
  4. Place the capture. Same position on every screen.
  5. Export at store sizes. Check pixels.
  6. Review on a phone. Look at it small.

App screenshot mockup: key rules and context

Frame vs frameless. Frames add context but take 15–25% of the canvas. Frameless shows bigger UI with a caption above. Partial frames (top of device cropped) are a middle ground.

Rules. Apple requires screenshots to show the app in use (2.3.3). Google forbids misleading device imagery. Don't show a device of the wrong platform: no iPhone on Google Play.

Where to get frames. Apple publishes product bezels for marketing. Many generators include frames: screenshot generator.

Test it. Frames vs frameless is a good first screenshot A/B test.

Worked example (hypothetical)

This example is illustrative. The app is made up, and so are any numbers in it.

Say Flowly puts screenshots inside an old phone frame. The frame looks dated. We'd go frameless with a rounded capture and a soft shadow.

Mockup tools compared

ToolBest for
FigmaFull control
CanvaQuick drafts
Our generatorFast exports at store sizes

Common mistakes

  • Old device frames. Dated quickly.
  • Messy status bars. Distracting.
  • Placeholder data. Looks unfinished.
  • Wrong export size. Upload fails.

For more on this topic, our ASO guides hub collects the rest of this series.

Screenshot specs we design to

Both stores publish exact requirements. These are the ones that matter most for a phone-first app.

Store / deviceSize or ruleCount
App Store, iPhone 6.9-inch1320 × 2868, 1290 × 2796 or 1260 × 2736 px (portrait)1–10 per device size
App Store, iPad 13-inch2064 × 2752 or 2048 × 2732 px (portrait)1–10 per device size
App Store, format.jpeg,.jpg or.png—
Google Play, phoneJPEG or 24-bit PNG, 320–3,840 px, long side no more than 2× the short sideMinimum 2 to publish, up to 8 per device type
Google Play, Chromebook / tablet1,080–7,680 px, 16:9 or 9:16Minimum 4 recommended

How we measure the result

For app screenshot mockup, success is measured on conversion, not looks. Screenshots mainly change conversion: the share of people who see your page or search result and then install. App Analytics reports product page views and conversion rate, and product page optimization tests show estimated lift per treatment.

Checklist

Copy this list into your release notes or ticket and tick each item off before you ship.

  • Clean captures
  • Frame choice
  • Captions
  • Consistent placement
  • Correct sizes
  • Reviewed on phone
FAQ

Questions

Do mockups increase installs?

No fixed answer; test it.

Can I use iPhone frames on Play?

No.

Are angled 3D mockups OK?

Yes, if UI stays readable.

Where are official frames?

Apple Design Resources.

Do you make mockups?

Yes, inside Screenshots A/B.

Should screenshots include a device frame?

It's optional. Frameless designs avoid looking dated when new devices launch.

Ready when you are

Fix your listing this week.

One fixed price, delivered as copy and files you paste yourself. No calls, no account access.

$99 one-timeDelivered in 2–3 business days2 revisionsNo login needed
Questions? Email us
Rank higher. More installs.Want your app ranked and more installs?
Get HireASO