How to Set Google Play Store Screenshot Sizes in Figma

Use a 1080 × 1920 px Figma frame for a portrait phone screenshot or a 1920 × 1080 px frame for landscape. Design inside that frame, export the frame at 1× as JPEG or 24-bit PNG without transparency, then verify the downloaded file before uploading it to Google Play Console.

These dimensions are practical high-resolution starting points. Google Play also checks file format, minimum and maximum dimensions, aspect ratio, and device category.

Google Play screenshot requirements to translate into Figma

Requirement	What to do in Figma
Accepted formats	Export JPEG or 24-bit PNG without an alpha channel.
General minimum	Keep both dimensions at least 320 px.
General maximum	Keep the longest dimension at or below 3840 px.
Aspect ratio	The longest dimension cannot be more than twice the shortest.
Recommendation placements	Prepare at least four screenshots at 1080 px or higher when eligible.
Per-device limit	Up to eight screenshots can be uploaded for each supported device type.
Large screens	Use separate 16:9 landscape or 9:16 portrait assets for tablets and Chromebooks; large-screen uploads are listed as 1080–7680 px.

Google Play says screenshots should demonstrate the actual in-app or in-game experience, with emphasis on core features and content. Treat promotional framing as secondary to showing the real product.

Recommended Figma frame sizes

Asset use	Frame size	Ratio	Notes
Phone portrait	1080 × 1920 px	9:16	Use for tall phone creatives and most portrait listing sequences.
Phone landscape	1920 × 1080 px	16:9	Use when the app experience is primarily horizontal.
Tablet or Chromebook portrait	1080 × 1920 px or another 9:16 size in the stated range	9:16	Keep this in a dedicated large-screen frame.
Tablet or Chromebook landscape	1920 × 1080 px or another 16:9 size in the stated range	16:9	Design for larger presentation sizes and verify readability.

Separate frames make it easier to maintain correct dimensions, typography, and composition for each device section. Do not resize a phone frame and assume it is an appropriate tablet creative.

Step-by-step: create the frame in Figma

Open the Frame tool. Press F or select Frame from the toolbar.
Create a custom frame. Draw any frame, then enter the exact values in the right sidebar’s W and H fields.
Name the frame clearly. Examples: GP-Phone-Portrait-1080x1920, GP-Phone-Landscape-1920x1080, and GP-Tablet-Portrait-1080x1920.
Keep all artwork inside the frame. Check clipping, device mockups, captions, and backgrounds at the frame edges.
Show the product. Use the first three screenshots to communicate the app’s core experience, then cover supporting workflows.
Duplicate for the sequence. Create one frame per screenshot so every export has an independent, predictable canvas.

Set exact dimensions

Portrait phone:   W 1080   H 1920
Landscape phone:  W 1920   H 1080

Figma presets are optional. A custom frame with exact pixel values is sufficient. Frames act as containers for the layers inside them, so placing artwork within the frame keeps export boundaries explicit.

Designing screenshots that meet the listing requirement

Show the actual current app experience instead of a marketing-only illustration.
Keep the main feature visible at the intended listing size.
Use a consistent visual system across the sequence, while making each screenshot communicate a distinct feature or task.
Check that device mockups, decorative borders, and overlays do not hide the app content.
Plan portrait and landscape compositions independently; simply rotating a layout often creates unreadable text or awkward spacing.
For tablets and Chromebooks, make a separate large-screen variant when those device categories apply.

Export the Figma frame correctly

Select the frame.
In the right sidebar, add an export configuration.
Choose PNG or JPG.
Set scale to 1× when the frame already has the required pixel dimensions.
Export and save the file with a name that includes device, orientation, and dimensions.

GP-Phone-Portrait-1080x1920.png
GP-Phone-Landscape-1920x1080.jpg

Figma also supports custom scale and fixed width or height export settings. Use those only when you intentionally need a different output size; otherwise, 1× preserves the frame’s exact pixel dimensions.

Validate the downloaded file before uploading

Do not rely only on the dimensions shown in the Figma file. Inspect the exported file itself.

Confirm width and height match the intended frame.
Confirm the file is JPEG or 24-bit PNG.
Confirm the PNG has no alpha channel or transparent areas.
Confirm both dimensions are at least 320 px.
Confirm the longest dimension is no more than 3840 px under the general rule.
Confirm the aspect ratio does not exceed 2:1.
Open the file in an image viewer and check for clipping, missing fonts, unexpected compression, or unreadable text.
Upload it to the matching phone, tablet, or Chromebook section in Play Console.

Common mistakes and fixes

Problem	Likely cause	Fix
Play Console rejects the file format	The export is an unsupported format or an indexed PNG.	Export JPEG or 24-bit PNG and inspect the downloaded file.
Transparency causes a validation error	The PNG contains an alpha channel.	Flatten the background and export a non-transparent 24-bit PNG or JPEG.
Dimensions are wrong after export	The frame was exported at a scale other than 1×, or fixed width/height settings were enabled.	Set the frame to the target pixels and export at 1×.
Aspect-ratio error	One dimension is more than twice the other.	Use 1080 × 1920, 1920 × 1080, or another size within the 2:1 limit.
Screenshot is below the minimum	A small frame or downscaled export was used.	Set both dimensions to at least 320 px; use the 1080-based recommendations for high-resolution assets.
Tablet listing looks like a stretched phone screen	The phone creative was reused without a large-screen layout.	Create a dedicated tablet or Chromebook frame and adjust spacing and typography.
Core feature is unclear	The screenshot is mostly decorative marketing art.	Show the real in-app experience and make the primary workflow obvious.
Text is clipped at the edge	Content extends outside the frame or is hidden by a mockup.	Keep artwork inside the frame and inspect the exported pixels, not just the canvas.

Performance, reliability, and cost considerations

Figma export is usually lightweight, but large raster backgrounds, multiple effects, and oversized frames can make files slower to preview and transfer. Keep source files organized with shared components, then export only the final frames needed for each device section.

Reliability comes from validating every downloaded asset. A correctly sized Figma frame can still produce a file with transparency, an unexpected color mode, or the wrong scale if export settings are changed. Record the intended dimensions in the frame name and in your release checklist.

Google Play’s screenshot limits are upload constraints, not a requirement to make every asset as large as possible. Use 1080 × 1920 or 1920 × 1080 when you want a clear, high-resolution starting point, then keep the final file within the platform’s limits.

Or skip the browser setup

If you need screenshots of web pages for documentation, listing research, or asset preparation, ScreenshotNeo returns a PNG, JPEG, WebP, or PDF from one GET request. Read the ScreenshotNeo API documentation for all options.

cURL

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,
)
r.raise_for_status()
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}`);
if (!res.ok) throw new Error(`Screenshot failed: ${res.status}`);
const data = Buffer.from(await res.arrayBuffer());
await import('node:fs/promises').then(fs => fs.writeFile('shot.webp', data));

ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture. Bot checks, blank pages, failed loads, timeouts, and cache hits are not billed; response headers identify the page verdict and whether the shot was billed. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients. The free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.

FAQ

Is 1080 × 1920 the correct Google Play screenshot size?

It is the recommended high-resolution portrait starting frame for phone creatives. Use 1920 × 1080 for landscape.

Should I export at 1× or 2× in Figma?

Export at 1× when the frame already has the required pixel dimensions. A 2× export doubles both dimensions and may exceed the intended size.

Can I use one screenshot set for phones and tablets?

Create separate device-type frames when tablets or Chromebooks are targeted. Large-screen assets have their own 16:9 or 9:16 guidance.

How many screenshots can I upload?

Google Play allows up to eight screenshots for each supported device type.

Can a Google Play screenshot be transparent?

Use a JPEG or a 24-bit PNG without alpha. Flatten transparent artwork onto a background before export.