Play Store Image Generator

Direct answer: A Play Store image generator turns real Android screens into listing graphics with device frames, backgrounds, and optional captions. It helps with composition and export, but your published screenshots must still show the actual, current app.

Keep the three asset types separate: screenshots show app UI, the feature graphic is a listing banner, and the app icon is the launcher asset. Each has different requirements.

Google Play image requirements

Verify the current rules in Google Play Console Help before publishing because platform requirements can change.

Asset	Baseline requirement	Checklist
App icon	32-bit PNG with alpha, 512 × 512 px, maximum 1,024 KB	Keep the mark legible at small sizes.
Feature graphic	JPEG or 24-bit PNG without alpha, 1,024 × 500 px	Use a simple focal point and safe margins.
Screenshots	JPEG or 24-bit PNG without alpha; each dimension 320–3,840 px; maximum dimension no more than twice the minimum	Use the correct portrait or landscape canvas for each device type.

You can upload up to eight screenshots for each supported device type. Google also describes a higher threshold for eligibility for some recommendation formats: at least four screenshots at 1,080 px minimum resolution (portrait 1,080 × 1,920 or landscape 1,920 × 1,080). That is recommendation guidance, not the baseline publishing rule. Google recommends putting the UI and core value in the first three images and showing the real app experience.

A reliable generator workflow

1. Capture real screens. Build the release candidate, seed representative data, and capture first-run, core-action, and result states. With a connected device or emulator, adb exec-out screencap -p > screen-01.png writes a PNG.
2. Choose device families. Decide whether you need phone, tablet, Chromebook, Android TV, Wear OS, or another supported type. Keep a separate canvas and sequence for each.
3. Compose for readability. Add a device frame only when the UI remains large enough to read. Use one short benefit statement if needed. Do not cover controls or imply unsupported features.
4. Export correctly. Flatten layers, remove alpha from feature graphics and screenshots, use sRGB, and check dimensions and file size.
5. Review at listing scale. Inspect thumbnails and phone-sized previews. The first three screenshots should explain the app without tiny text.
6. Reuse assets. Play Console’s Asset Library helps manage and reuse screenshots, icons, and feature graphics across the main listing, custom listings, experiments, and events.

Runnable Python generator

Install Pillow with python -m pip install pillow. Save this as make_play_image.py, then run python make_play_image.py screen-01.png play-01.png.

from PIL import Image, ImageDraw, ImageFont
import sys

src_path, out_path = sys.argv[1], sys.argv[2]
W, H = 1080, 1920
src = Image.open(src_path).convert('RGB')
max_w, max_h = 900, 1420
scale = min(max_w / src.width, max_h / src.height)
shot = src.resize((round(src.width * scale), round(src.height * scale)), Image.Resampling.LANCZOS)
canvas = Image.new('RGB', (W, H), '#F3F5F9')
draw = ImageDraw.Draw(canvas)
try:
    font = ImageFont.truetype('DejaVuSans-Bold.ttf', 58)
except OSError:
    font = ImageFont.load_default()
draw.text((70, 70), 'Your core action, in seconds', fill='#111827', font=font)
left = (W - shot.width) // 2
top = 300
frame = 24
draw.rounded_rectangle((left-frame, top-frame, left+shot.width+frame, top+shot.height+frame), radius=34, fill='#111827')
canvas.paste(shot, (left, top))
canvas.save(out_path, format='PNG', optimize=True)
print(f'wrote {out_path}: {W}x{H}')

For production, replace fixed captions with localized strings, load a licensed font explicitly, and generate one file per device type. Never stretch a screenshot; crop only after confirming that the UI remains honest and usable.

Design decisions that affect approval

• Sequence: lead with the problem and core action, then show the result, differentiators, and secondary features.
• Text: use short claims visible on a phone. Do not promise features or outcomes the build does not provide.
• Frames: frames clarify device context but consume space. Remove them when the interface becomes unreadable.
• Localization: reserve room for longer translations and generate localized sets instead of shrinking type.
• Accessibility: maintain contrast, avoid color-only meaning, and keep controls recognizable.

Official and third-party workflow options

Google’s Device art generator places screenshots into device artwork. Play Console’s Asset Library handles reuse and organization. Canva’s marketplace listing for App Screenshot Gen describes templates with device frames, backgrounds, and marketing text for Android and iOS; treat that as the listing’s description rather than independent quality testing. Compare tools on supported device types, current Play dimensions, export formats, reusable layouts, batch work, and whether the real UI stays legible.

Validation checklist

• Every screenshot shows the current release build and real data states.
• At least two screenshots are present for applicable device types.
• Dimensions, format, alpha, and file size match current Play rules.
• The first three images communicate the core experience on a small screen.
• No frame, caption, or decoration hides interactive UI.
• Portrait and landscape sets are not mixed accidentally.
• Localized images have been reviewed by a native reader.

Troubleshooting

Symptom	Cause	Fix
Upload rejects the file	Wrong format, alpha, dimensions, or size	Flatten to JPEG or 24-bit PNG, inspect metadata, and export within the requirements.
Screenshot is blurry	Small source was upscaled or JPEG was recompressed	Capture at target resolution, resize once with a high-quality filter, and keep a lossless source.
Text is unreadable	Frame or caption consumes too much canvas	Increase screenshot area, shorten copy, or remove the frame.
Listing shows an unsupported feature	Composition uses an old build	Recapture from the release candidate and audit every claim.
Tablet listing feels stretched	Phone capture was scaled instead of recaptured	Capture the tablet layout and create a tablet-specific composition.
Some locales do not fit	English-length text was baked into the design	Use locale-specific copy and flexible text boxes.

Performance, reliability, and cost

Capture once per release candidate, keep source screenshots and layout templates under version control, and render exports with a repeatable script. This makes experiments and custom listings reproducible. The main cost is design and review time; Google’s guidance does not establish a conversion or ranking benefit for any generator.

Or skip the browser setup

ScreenshotNeo is a website screenshot API, useful for a Play listing’s web companion page, documentation, or marketing landing page. It does not replace capturing native Android UI. One GET request returns PNG, JPEG, WebP, or PDF. See the ScreenshotNeo API docs.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

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)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

Before capture, ScreenshotNeo accepts cookie or consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and the response identifies the result with X-Page-Verdict and X-Billed headers. An MCP server exposes take_screenshot, get_page_info, and capture_pdf to Claude, Cursor, and other MCP clients. The Free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots. Create a free ScreenshotNeo account.

FAQ

Does a generator create app screenshots automatically?

It can compose and export assets, but you still need current captures from the app or emulator.

Can one image set serve every device?

Use device-specific captures when layouts differ. A phone image may not demonstrate tablet or Chromebook experiences.

Are four 1,080 px screenshots mandatory?

No. That is eligibility guidance for some recommendation formats. Baseline publishing rules are listed separately above.

Where should assets be stored?

Keep editable templates, source captures, and final exports together, then use Play Console’s Asset Library for reuse.