What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
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, then check the downloaded file before uploading it to Google Play Console. These dimensions are practical high-resolution starting points, not the only sizes Google Play accepts.
Choose the correct Figma frame size first
For most phone store listings, create one of these frames:
| Asset | Figma frame | Aspect ratio | Use |
|---|---|---|---|
| Phone portrait | 1080 × 1920 px | 9:16 | Recommended starting frame for vertical phone creatives |
| Phone landscape | 1920 × 1080 px | 16:9 | Recommended starting frame for horizontal phone creatives |
| Tablet or Chromebook portrait | 1080 × 1920 px, or another size in the large-screen range | 9:16 | Dedicated large-screen portrait asset |
| Tablet or Chromebook landscape | 1920 × 1080 px, or another size in the large-screen range | 16:9 | Dedicated large-screen landscape asset |
Google Play’s general screenshot rule allows JPEG or 24-bit PNG files, requires each dimension to be at least 320 px, limits each dimension to 3840 px, and does not allow the longest dimension to be more than twice the shortest. For recommendation placements, Google recommends at least four screenshots at 1080 px or higher, using 1920 × 1080 landscape or 1080 × 1920 portrait proportions.
The 1080 × 1920 and 1920 × 1080 frames already satisfy the general pixel and aspect-ratio rules. They also give you enough resolution for text and interface details without creating unnecessarily large exports.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute#1 Best Overall
Set an exact frame in Figma
- Open the Figma file that contains your store creative, or create a new design file.
- Press F or choose the Frame tool from the toolbar.
- Draw any frame on the canvas. Select it so the frame properties appear in the right sidebar.
- Enter 1080 in W and 1920 in H for portrait, or enter 1920 in W and 1080 in H for landscape.
- Confirm that the units are pixels. Figma supports custom dimensions as well as device and asset presets; a preset is optional when you know the required values.
- Rename the frame so its purpose is obvious, such as
GP-Phone-Portrait-1080x1920orGP-Phone-Landscape-1920x1080.
Figma frames are containers for other layers. Keep every background, device mockup, headline, screenshot, and decorative element inside the frame bounds. Anything outside the frame will not be included in the export.
Plan the content inside the frame
Use the first three screenshots to explain the app’s core experience. Google Play says screenshots should demonstrate the actual in-app or in-game experience, with emphasis on core features and content. A marketing-only illustration that does not show the product can fail that expectation even when its dimensions are correct.
- Use real, current screens from the app rather than invented interface artwork.
- Keep text large enough to read on a phone-sized listing preview.
- Maintain safe margins so headings and controls are not crowded against the frame edge.
- Use one frame per screenshot. Duplicate the frame when creating alternate messages so every export keeps the same dimensions.
Export the frame at the required pixel size
- Select the finished frame in the Layers panel or on the canvas.
- In the right sidebar, scroll to Export and add an export setting.
- Choose PNG or JPG.
- Set the scale to 1×. Because the frame itself is already 1080 × 1920 or 1920 × 1080 pixels, a 1× export produces the intended file dimensions.
- Click Export and save the file.
Figma also offers custom scale and fixed width/height export settings. Those are useful when you intentionally create a source frame at another size, but changing the export scale can produce a file that no longer matches the dimensions you planned. For a frame already set to the Play target, 1× is the least error-prone choice.
Validate the downloaded file before Play Console
Do not rely only on the number shown in Figma. Inspect the actual downloaded file, because export settings, an accidental selection, or an image conversion can change the result.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- Pixel dimensions: confirm the width and height are the intended values, such as 1080 × 1920.
- Format: confirm the file is JPEG or PNG.
- PNG color and alpha: use a 24-bit PNG without an alpha channel. Do not depend on transparent pixels for the store artwork.
- Aspect ratio: verify that the longest side is no more than twice the shortest side.
- File contents: open the image and check that no layer is clipped, missing, blurry, or outside the frame.
- File size: check that the file is practical to upload and that compression has not made text unreadable.
For a 1080 × 1920 export, the shortest dimension is 1080 and the longest is 1920, so it is within the 2:1 limit. A 1920 × 1080 export has the same relationship in landscape.
How many screenshots can you upload?
Google Play allows up to eight screenshots for each supported device type. Treat each device category separately: phone assets belong in the phone section, while tablet and Chromebook assets belong in their large-screen sections. If your listing targets tablets or Chromebooks, prepare dedicated frames instead of simply stretching a phone composition.
Large-screen guidance uses 16:9 landscape or 9:16 portrait proportions and lists uploads in the 1080–7680 px range. A 1080 × 1920 or 1920 × 1080 frame is a valid starting point within that guidance, but you can choose another size in the stated range when your production workflow or source material requires it.
Phone versus tablet and Chromebook files
Phone listing
Start with the 1080 × 1920 portrait frame when your app is normally used vertically. Use 1920 × 1080 when the important interaction is horizontal, such as a game or media interface. Keep a consistent visual system across the sequence, but let each screenshot show a distinct feature.
Tablet and Chromebook listing
Create a separate large-screen frame and redesign the composition for the wider or larger presentation area. Do not assume that a phone screenshot with extra empty space communicates tablet functionality. Check the matching device section in Play Console before uploading.
Other device categories
Wear OS, TV, Automotive, and XR listings have their own device contexts. If your app targets one of those categories, supply the appropriate category-specific assets rather than reusing a phone frame without checking the console requirements.
Rank #3
Common Figma and Play Console problems
The export is twice as large as expected
Cause: the export scale is set to 2× or a fixed width/height overrides the frame. Fix: select the frame, remove the extra export setting, and export at 1×. Recheck the downloaded dimensions.
The image fails because of transparency
Cause: the PNG contains an alpha channel or transparent background. Fix: add an opaque background layer inside the frame and export a 24-bit PNG without alpha, or export a JPEG. Inspect the file rather than assuming the visible canvas is opaque.
Free tools Windows power users keep installed
One-click scans. No signup required.
The aspect ratio is rejected
Cause: the frame was resized after the artwork was created, or width and height were entered in the wrong fields. Fix: set the frame back to 1080 × 1920 or 1920 × 1080 and confirm that the longest dimension is no more than twice the shortest.
The screenshot looks cropped
Cause: artwork extends beyond the frame, or an image fill uses an unintended crop mode. Fix: select the frame, inspect its child layers, and use the frame boundary as the final crop. Preview the exported file at 100 percent before uploading.
Text is unreadable in the listing
Cause: too much copy, low-contrast text, or a source screenshot scaled down inside a large composition. Fix: shorten the message, increase contrast and type size, and show one core feature per frame. The pixel dimensions alone cannot make tiny text legible.
The design shows a feature that is not in the app
Cause: a promotional mockup replaced the actual interface. Fix: capture the current in-app experience and use that as the primary visual. Keep claims and screens aligned with the version users will install.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsWorkflow and reliability tips
- Use a frame matrix: maintain named phone portrait, phone landscape, tablet portrait, and tablet landscape frames in one file.
- Lock shared elements: lock backgrounds and guides so they are not moved while updating screenshots.
- Duplicate before editing: make a copy for each store position, then update the feature-specific content.
- Export in batches: select several completed frames and give them consistent PNG or JPG settings, while still checking each resulting file.
- Keep source and export names clear: include device, orientation, and pixel size in the frame and file name.
- Test the upload section: select the correct phone, tablet, or Chromebook area in Play Console before choosing files.
These practices prevent a common failure mode: a visually correct design exported at the wrong scale or uploaded to the wrong device category.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Or skip the browser setup
If you need screenshots of a web page for documentation, QA, or an app-listing workflow, ScreenshotNeo can return an image or PDF from one API request. It is separate from Figma: you still design your store creative in the correctly sized frame, but you can automate capture of the source web experience instead of configuring a browser.
Its capture process accepts cookie and consent banners before taking the shot, then removes more than 60 known consent platforms, newsletter popups, and chat widgets. Each cleanup step can be turned off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the page verdict and billing status in X-Page-Verdict and X-Billed headers.
The API supports PNG, JPEG, WebP, and PDF output, including full-page captures, lazy-image loading, CSS-selector element capture, dark mode, device presets, custom viewports, retina scale, PDF paper settings, custom CSS and JavaScript, clicks, selector or network-idle waits, request and resource blocking, headers, cookies, user agents, authorization, timezone, geolocation, transparent backgrounds, resizing, configurable caching TTLs, signed image links, asynchronous jobs with signed webhooks, bulk capture of up to 100 URLs per call, and a usage API. An MCP server provides take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →cURL
See the ScreenshotNeo API documentation for parameter details. This request saves a WebP screenshot:
Best Value
- Used Book in Good Condition
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython
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(`HTTP ${res.status}`);
const fs = await import('node:fs/promises');
await fs.writeFile('shot.webp', Buffer.from(await res.arrayBuffer()));ScreenshotNeo has a free allowance of 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 shots; every feature is on every plan, and yearly billing gives two months free. Sign up for the free ScreenshotNeo plan.
FAQ
Is 1080 × 1920 always mandatory?
No. It is the recommended high-resolution portrait starting frame. Google Play also accepts other files that meet its minimum, maximum, format, and aspect-ratio rules.
Should I export JPG or PNG?
Either is accepted. Use a 24-bit PNG without alpha when you need crisp interface text; use JPEG when a smaller photographic export is more useful.
Can one screenshot serve phones and tablets?
You can reuse an image only when it genuinely fits both contexts and the relevant console rules. Separate large-screen frames usually produce a clearer tablet or Chromebook presentation.
Why does a 1× export matter?
A 1× export preserves the frame’s existing pixel dimensions. A 2× setting doubles both dimensions and can create a file different from the size you intended.
Frequently Asked Questions
Can I upload a Figma file directly to Play Console?
No. Export the selected frame as a JPEG or 24-bit PNG, validate the downloaded file, and upload that image.
How should I name Figma screenshot frames?
Include device, orientation, and dimensions, for example GP-Phone-Portrait-1080×1920.
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.
