Use a 1080 × 1920 px Figma frame for a portrait phone screenshot or 1920 × 1080 px for landscape. Design inside that frame, export it at 1× as a JPEG or 24-bit PNG without transparency, and inspect the downloaded file before uploading to the matching Google Play Console section. These dimensions are practical high-resolution starting points; Play also checks minimum and maximum pixels, aspect ratio, format and whether the image represents the real app experience.
Which Figma dimensions should you use?
For phone listing creatives, start with one of these frames:
| Asset | Figma frame | Aspect ratio | Use |
|---|---|---|---|
| Phone portrait | 1080 × 1920 px | 9:16 | Primary portrait listing screenshots |
| Phone landscape | 1920 × 1080 px | 16:9 | Landscape app experiences or alternate listing art |
| Tablet/Chromebook portrait | 1080 × 1920 px, or another 9:16 size in the large-screen range | 9:16 | Dedicated large-screen creative |
| Tablet/Chromebook landscape | 1920 × 1080 px, or another 16:9 size in the large-screen range | 16:9 | Dedicated large-screen creative |
Google recommends at least four screenshots at 1080 px or higher for recommendation placements, using 1920 × 1080 landscape or 1080 × 1920 portrait proportions. You can upload up to eight screenshots for each supported device type.
Google Play rules to translate into your design
Pixel limits and ratio
- Accepted formats are JPEG or 24-bit PNG.
- Do not rely on an alpha channel or transparent background.
- Under the general screenshot rule, each dimension must be at least 320 px and no dimension may exceed 3840 px.
- The longest dimension cannot be more than twice the shortest. A 1080 × 1920 frame is safely within that 2:1 limit.
Show the actual product
Google Play Help says screenshots must demonstrate the actual in-app or in-game experience, focusing on core features and content. Build promotional labels around genuine screens rather than replacing the interface with a marketing-only illustration. Keep text and controls legible at the size users will see in the store.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problems#1 Best Overall
Plan separate large-screen assets
Tablet and Chromebook listings have their own large-screen section, with 16:9 landscape or 9:16 portrait guidance and uploads listed from 1080 to 7680 px. Treat these as separate frames: a phone composition scaled up can leave excessive empty space or unreadable controls. Upload each file to the device category it was designed for.
Create the frame in Figma
- Open the Frame tool. Press F, or choose the Frame tool from Figma’s toolbar.
- Set exact dimensions. With the frame selected, enter
1080in the right-sidebar W field and1920in H for portrait. For landscape, enter1920by1080. Figma presets are optional; custom dimensions are equally valid. - Name the frame. Useful names include
GP-Phone-Portrait-1080x1920,GP-Phone-Landscape-1920x1080andGP-Tablet-Portrait-1080x1920. Clear names prevent exporting the wrong device variant. - Keep all artwork inside the bounds. Place the real app screen, device chrome, annotations and background within the frame. Check that no important content is clipped at the top, bottom or sides.
- Duplicate for a screenshot set. Build the first three frames around the app’s core experience, then add frames for distinct features. Do not create near-duplicates simply to fill the allowance.
Designing a readable Play screenshot
Start with the app screen
Place the current, production-like app view as the dominant element. If you add a headline or callout, make sure it does not cover navigation, data or controls that a user needs to understand the feature.
Respect portrait and landscape differences
Do not rotate a portrait composition and assume it is a landscape design. Reflow the screen, headline and supporting graphics so the 16:9 version remains balanced and the app content is still identifiable.
Keep device variants independent
Use dedicated tablet or Chromebook frames when those categories matter. Large-screen screenshots should show layouts that actually work at large-screen presentation sizes, not a phone interface floating in an oversized canvas.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #2
Export the frame at the required size
- Select the finished frame in the Layers panel or canvas.
- In the right sidebar, find Export and add an export configuration.
- Choose PNG or JPG. Use 1× when the frame itself is already 1080 × 1920 or 1920 × 1080 px.
- Export and save the downloaded file with a device-and-order name such as
01-onboarding-phone-portrait.png. - If your source frame is a different size, use Figma’s fixed width/height or scale controls deliberately, then verify the resulting pixels. Scaling a small design up can make text and UI soft.
PNG preserves crisp interface edges; JPG can be smaller but may introduce compression around text. Whichever you choose, ensure it is a 24-bit image without transparency and that the final pixels match the intended Play section.
Validate before uploading
Validation catches most rejected or misplaced assets before Play Console does. Check every exported file:
- Dimensions: confirm width and height in an image viewer or your operating system’s file details.
- Format and color: confirm JPEG or 24-bit PNG; remove an alpha channel rather than depending on transparency.
- Ratio: verify the longest side is no more than twice the shortest under the general rule.
- Content: confirm the screen is the real current app experience and demonstrates a core feature.
- Device destination: match phone files to phone sections and large-screen files to tablet or Chromebook sections.
- File integrity: open the file after downloading it, check that it is not corrupt, and review text at 100% zoom.
Upload the validated files to the corresponding phone, tablet or Chromebook area in Play Console. Keep the exported originals so you can reproduce a listing update later.
Common problems and fixes
The upload is rejected for size or ratio
Recheck both numbers, not just the larger one. A file must meet the 320 px minimum, stay within the applicable maximum, and remain inside the 2:1 longest-to-shortest ratio. Return to the Figma frame’s W and H fields, correct the dimensions, export again at 1×, and validate the new file.
Rank #3
The PNG has transparency
Some Figma artwork or export settings can leave an alpha channel. Add an opaque background layer, place it behind the artwork, and export a 24-bit PNG or JPG. Inspect the file properties after export.
The screenshot looks blurry
This usually means the source frame was smaller than the required output and enlarged during export, or that a JPG was compressed heavily. Create the frame at the final pixel dimensions and export at 1×; if text remains soft, prefer PNG.
Important UI is cut off
Check the frame boundary and any masks or auto-layout constraints. Move the app screen and annotations inward, then inspect the entire frame before exporting. Do not depend on content extending beyond the frame.
Phone art is being used for a tablet listing
Duplicate the design into a clearly named large-screen frame and recompose the layout for 16:9 or 9:16. Upload it to the large-screen device section rather than reusing the phone file blindly.
The screenshot does not communicate a feature
Replace decorative copy with a real app state that proves the feature. Google Play’s requirement is about demonstrating actual in-app or in-game experience, so make the interface—not an abstract illustration—the evidence.
A repeatable production checklist
- Choose portrait or landscape for the phone experience.
- Create a 1080 × 1920 or 1920 × 1080 frame.
- Build the composition from a real app screen.
- Duplicate and recompose for additional features and large-screen devices.
- Export selected frames as PNG or JPG at 1×.
- Inspect dimensions, format, alpha, ratio, readability and file integrity.
- Upload each file to its matching Play Console device section, with no more than eight per supported device type.
Or skip the browser setup
If you need clean captures of a hosted app or web flow to place into Figma, ScreenshotNeo returns a screenshot from one GET request. It accepts the cookie or consent banner like a visitor, then removes more than 60 known consent platforms, newsletter popups and chat widgets before capture; each step can be disabled. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info and capture_pdf tools for Claude, Cursor and other MCP clients.
See the parameter details in the ScreenshotNeo documentation. A direct capture looks like this:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
Python:
import requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)
Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
The service supports PNG, JPEG, WebP and PDF; full-page and element capture, device presets or custom viewports, retina scale, dark mode, custom CSS and JavaScript, clicks, waits, request blocking, headers, cookies, user agents, authorization, timezone, geolocation, resizing, TTL caching, signed links, async webhooks, bulk capture of 100 URLs per call and a usage API. Every feature is on every plan: 1,000 screenshots a month are free with no card, and paid plans start at $5 for 3,000. Create a free ScreenshotNeo account.
Frequently Asked Questions
Is 1080 × 1920 the only valid phone size?
No. It is the recommended high-resolution portrait starting frame. Your file still has to satisfy Play’s pixel, format and aspect-ratio rules.
Best Value
- Used Book in Good Condition
Can I upload more than eight screenshots for one device type?
Google Play allows up to eight screenshots for each supported device type.
Should tablet screenshots be the same as phone screenshots?
No. Plan separate large-screen frames and upload them to the tablet or Chromebook section when those devices are targeted.
Should I export at 2× for sharper results?
Not when the frame is already 1080 × 1920 or 1920 × 1080. Export at 1× so the downloaded pixel dimensions remain the intended Play asset size.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




