- 100% in browser
- No upload
- No signup
- No watermark
- Free forever
Feature Graphic Maker — Free Google Play 1024×500 Banner Designer
A Google Play feature graphic is 1024 × 500 px, a 24-bit PNG or JPEG, with no transparency and under 15 MB.
- 1024 × 500 px
- 24-bit PNG / JPEG
- No alpha channel
- ≤ 15 MB
- Safe area 824 × 400
Design that banner here, plus your Play Store and App Store screenshots, app icon and social covers. Frame screenshots in accurate iPhone, iPad, Pixel, Galaxy and OnePlus mockups, add headline text and vector shapes, and export a pixel-exact PNG. Nothing is uploaded — the whole editor and the export run in your browser, so an unreleased app's UI never leaves your machine.
· Free forever · No registration
A feature graphic is the 1024×500 px banner Google Play shows at the top of your app listing, in search results and in editorial collections. It must be a 24-bit PNG or JPEG with no alpha transparency, under 15 MB. Resizo's free feature graphic maker gives you that exact canvas, a layer-based editor for text, shapes and screenshots, and a client-side PNG export that matches the preview pixel for pixel — no account, no watermark, no upload.
Keyboard: arrows nudge (Shift = 10 px) · Ctrl+Z undo · Ctrl+D duplicate · Del delete · Esc deselect. Work is autosaved in this browser only.
Tap a layer to select it, then drag to move, pull the corner to resize or the ○ above it to rotate. Work is autosaved in this browser only.
Feature graphic templates that re-flow to any canvas
The template shelf in the left rail is not a folder of 1024 × 500 images. Each template is a layout described in fractions of the canvas — a headline at 6% from the left and 19% down, sized at 18.5% of the canvas height — so the shelf itself changes when you change the canvas. Pick Hero left on the feature graphic and you get a landscape banner; switch the canvas to a 1080 × 1920 Play screenshot and the same layout re-solves into a portrait one, keeping your text and your screenshots where they belong instead of stretching them.
Built-in layouts cover the shapes that actually get used: hero with the headline left and a shape bleeding off the right, centred title with a pill badge, device split with a phone mockup against a headline, heavy outline type, and an icon lockup. Select a device frame and the shelf swaps to screenshot layouts matched to that hardware.
Your own layouts work the same way. Save current as template normalises whatever is on the canvas against the size it was made on and stores it in this browser, so it rescales onto every other preset exactly like the built-in ones. Saving again under the same name updates it. Photos are deliberately not stored — only the geometry — which keeps the entry small and means applying a template re-uses the images already on your canvas rather than dragging stale ones back in.
App store & banner size reference
| Asset | Size | Format rules |
|---|---|---|
| Google Play feature graphic | 1024×500 | 24-bit PNG or JPEG, no alpha, ≤15 MB |
| Google Play app icon | 512×512 | 32-bit PNG, ≤1 MB |
| Google Play phone screenshot | 1080×1920 | PNG or JPEG, 16:9 or 9:16, 2–8 required |
| App Store iPhone 6.7" | 1290×2796 | PNG or JPEG, no transparency |
| Social share / Open Graph | 1200×630 | 1.91:1, PNG or JPEG |
| YouTube thumbnail | 1280×720 | 16:9, ≤2 MB |
| X / Twitter header | 1500×500 | 3:1, ≤5 MB |
| LinkedIn page banner | 1584×396 | 4:1, PNG preferred |
This page is for designing a graphic from scratch. Already have the artwork and only need it at the right size? Use the image resizer or batch resize to hit these numbers exactly.
Play Store banner maker — every listing asset from one canvas
A Google Play submission needs more than the banner. The Console asks for a 1024 × 500 feature graphic, a 512 × 512 icon, and between two and eight phone screenshots, with a separate set if you support tablets or Chromebooks. Most tools make you leave and come back for each one. Here the canvas picker holds all of them, so the same headline, palette and logo carry across the whole listing without being rebuilt.
Feature graphic — 1024 × 500
Required. Heads the store listing, and becomes the cover frame for your promo video if you attach one.
App icon — 512 × 512
Required, 32-bit PNG under 1 MB. Build it from a shape layer with a letter or a logo image on top.
Phone screenshots — 1080 × 1920
Two minimum, eight maximum. Between 320 and 3840 px per side, and never more than 2:1 either way.
Tablet screenshots — 1920 × 1080
Needed to be considered for tablet and Chromebook surfacing. Four or more is what Google asks for.
The same canvas list also carries the Apple sizes — iPhone 6.7-inch at 1290 × 2796 and iPad 12.9-inch at 2048 × 2732 — so a cross-platform launch is one editor rather than two. And because the export is a real canvas render at 1× or 2×, a 1024 × 500 download is 1024 × 500, not a screenshot of a preview that Play will then reject on dimensions.
Designing a feature graphic that survives Google Play's crops
Keep the message inside the safe area
Google Play does not always show your 1024×500 graphic intact. On the store listing it may be letterboxed; in editorial collections and some carousels it is cropped tighter, and when a promo video is attached a large circular play button is composited over the centre. The practical consequence is that anything within roughly 100 px of an edge, and anything sitting dead centre, is at risk. Turn on Show safe area in this editor to draw the inner 824×400 rectangle, then keep your logo and headline inside it while pushing decorative gradients and shapes to the bleed. Designs that ignore this rule are the single most common reason a feature graphic looks broken in one surface while previewing fine in another.
Three or four words, set large
At the sizes Play renders a feature graphic on a phone, the graphic is often barely 360 px wide — a third of its native resolution. Body copy disappears entirely. Treat the graphic as a poster: one short value proposition at 48–90 px on the 1024×500 canvas, a logo, and one supporting visual. Avoid duplicating your app name if it already appears in the listing text beneath, and avoid screenshots-inside-the-banner at small scale, because nested UI turns to mud. If you must show the product, crop into a single recognisable element rather than shrinking a whole screen.
Contrast beats decoration
Store surfaces sit on both light and dark backgrounds and are surrounded by competing thumbnails. A graphic with a strong figure-to-ground relationship — light type on a saturated field, or dark type on a pale one — reads at thumbnail size; a graphic built from mid-tone gradients does not. Aim for a contrast ratio of at least 4.5:1 between your headline and whatever sits directly behind it, and check the result by zooming the preview here down to 25%. If the headline stops being legible at that zoom, it will not survive the store. Text outline and drop shadow, both available in the text panel, are the fastest fixes when a headline crosses a busy photo.
The transparency trap that gets feature graphics rejected
If the Play Console refused your upload, the odds are it was an alpha channel. Google Play accepts a 24-bit PNG or a JPEG and nothing else, and a PNG saved out of Figma, Illustrator, Photoshop or Canva keeps its alpha channel even when every pixel in it happens to be opaque. The file looks perfect on your desktop and is rejected on upload. Here is the full list of causes, and what each one actually needs.
| Rejection cause | The fix |
|---|---|
| PNG carries an alpha channel | Flatten onto an opaque background, or export 24-bit. Every export from this page is already flat. |
| Wrong dimensions | Exactly 1024 × 500 px. Not 1024 × 512, not 2048 × 1000 — Play does not downscale it for you. |
| File over 15 MB | Switch the export format to JPG, or run the PNG through PNG compression. |
| Store badges in the artwork | Remove any "Get it on Google Play" badge, App Store badge or Editors' Choice mark — Google reserves those. |
| Review stars, ratings or download counts | Metadata policy bans them in listing artwork, even when the numbers are real. |
| Text cut off by the crop | Not a hard rejection, but it fails review on quality. Turn on Show safe area and keep type inside 824 × 400. |
Resizo removes the first cause structurally rather than by reminding you about it. The editor paints a background layer — solid, gradient or photo — beneath every other layer before it draws anything, and the export renders that same stack onto an opaque canvas. There is no path through this tool that produces a transparent PNG, so a straight download is a file Google Play accepts. That is also why the background panel has no "none" option: it would be a way to fail.
Device frames for Android and iOS
Pick a device and the frame takes that hardware's real screen resolution, corner radius, bezel width and camera cutout — Dynamic Island, notch, punch-hole or a physical home button. The frame's height is always solved from its width, so a mockup can never be stretched out of aspect no matter how you drag it. Choosing a device also offers to set the canvas to that screen's exact resolution, which is what the stores want you to upload.
Apple
- iPhone 16 Pro Max — 1320×2868 · Dynamic Island
- iPhone 16 Pro — 1206×2622 · Dynamic Island
- iPhone 16 Plus — 1290×2796 · Dynamic Island
- iPhone 16 · iPhone 15 / 14 — 1179×2556
- iPhone 13 / 12 — 1170×2532 · notch
- iPhone SE (3rd gen) — 750×1334 · home button
- iPad Pro 13" — 2064×2752
- iPad Air 11" — 1640×2360
- iPad mini — 1488×2266
Android
- Pixel 9 Pro XL — 1344×2992 · punch-hole
- Pixel 9 Pro — 1280×2856 · punch-hole
- Pixel 9 — 1080×2424 · Pixel 8a — 1080×2400
- Galaxy S24 Ultra — 1440×3120
- Galaxy S24 / A55 — 1080×2340
- Galaxy Z Fold 6 (open) — 1856×2160
- OnePlus 12 — 1440×3168
- Xiaomi 14 — 1200×2670
- Nothing Phone (2) — 1080×2412
- Android phone 16:9 — 1080×1920 · tablet — 1600×2560
Set the canvas to any of these resolutions and the template shelf switches to device frames automatically. Built a layout you want to reuse? Save current as template stores it in this browser, normalised against its canvas, so it rescales cleanly onto every other size — the same way the built-in templates do.
What people build with it
Play Store launches
Indie developers who need a 1024×500 banner and a 512×512 icon before submitting a build, without opening Figma or paying for a design subscription.
Annotated screenshots
Drop a screenshot into a real iPhone 16 Pro or Pixel 9 frame, add a caption above it, and export the store screenshot set — same layout, different caption, four times over.
Social & OG images
1200×630 link previews, YouTube thumbnails and LinkedIn banners from the same layer model — switch the canvas preset and reposition, no re-export pipeline.
Related Resizo tools
FAQ
What size is a Google Play feature graphic?
1024 × 500 pixels, as a 24-bit PNG or JPEG with no alpha transparency, under 15 MB. Google Play crops and scales it for different surfaces, so keep important text inside the middle 824 × 400 area.
Is my image uploaded to a server?
No. The editor and the export both run entirely in your browser with the HTML5 Canvas API. Images you add never leave your device, and there is no server to send them to.
Does the export match what I see on screen?
Yes. The canvas is laid out at true pixel size and only visually scaled to fit your screen. Export draws the same layer model onto a real canvas, using the same line-breaking and gradient geometry, so wrapping, rotation and gradients come out identical at 1× or 2×.
Can I put text on my feature graphic?
Yes, but keep it to three or four words set large. Play composites a play button over the centre when a promo video is attached, and crops the edges on some surfaces, so keep type inside the safe area.
Which other sizes are supported?
Google Play screenshots and the 512×512 icon, App Store 6.7-inch and iPad screenshots, 1200×630 social sharing images, YouTube thumbnails and channel art, X and LinkedIn headers, Facebook covers, Instagram posts and stories — plus any custom width and height up to 8000 px.
Will my work be saved if I close the tab?
The layout is autosaved to this browser's local storage and restored on your next visit. Nothing is sent anywhere. Very large embedded photos may be dropped from the autosave when they exceed the browser's storage quota — the layout still returns, the photo may not.
Which device frames are included?
22 frames: iPhone 16 Pro Max, 16 Pro, 16 Plus, 16, 15/14, 13/12 and SE (3rd gen); iPad Pro 13", iPad Air 11" and iPad mini; Pixel 9 Pro XL, 9 Pro, 9 and 8a; Galaxy S24 Ultra, S24/A55 and Z Fold 6; OnePlus 12; Xiaomi 14; Nothing Phone (2); plus generic 16:9 Android phone and Android tablet. Each carries its real screen resolution, corner radius, bezel width and camera cutout.
Can I save my own template?
Yes. Save current as template stores the layout in this browser, normalised against the canvas it was made on, so it rescales onto other sizes exactly like the built-in templates. Saving again under the same name updates that template. Photos are not stored — only the layout — so the entry stays small, and applying it re-injects whatever images are already on your canvas.
Why did Google Play reject my feature graphic?
Most often an alpha channel. Play requires a 24-bit PNG or JPEG with no transparency, and design tools keep the alpha channel even when every pixel is opaque. The other frequent causes are wrong dimensions — it must be exactly 1024 × 500 — a file over 15 MB, and policy issues such as store badges, review stars or download counts in the artwork. Every export from this page is opaque by construction, which removes the first cause entirely.
Is a feature graphic required to publish on Google Play?
Yes. It is a required asset in the Play Console main store listing and the submission will not go through without it. It doubles as the cover frame for your promo video, so if you attach a video Play composites a large play button over the centre of the graphic — one more reason to keep the middle clear.
Is this feature graphic maker really free?
Yes — no account, no trial limit, no export credits, no watermark, and no paid tier to upgrade to. There is no server cost to recover, because the editor and the export both run on your own device.