Check your feature graphic dimensions
Have the exported file? Open the local PNG/JPEG checker and choose “Google Play · feature graphic” to inspect its encoded dimensions and transparency metadata.
| Export | What needs attention | Next action |
|---|---|---|
| 1024 × 500 RGB PNG | Dimensions and RGB format can match; image content still needs review. | Inspect the actual file, readability and current console validation. |
| 500 × 1024 | Portrait dimensions do not match the landscape target. | Recompose on a 1024 × 500 canvas; avoid stretching a portrait screen. |
| 2048 × 1000 | The shape matches, but the required pixel dimensions do not. | Export the correct final size from the source artwork. |
| 1024 × 500 PNG with alpha | The canvas fits, but the file contains transparency metadata. | Export a 24-bit RGB PNG without alpha, or an appropriate JPEG. |
Check the final export, not the editor canvas
Keep the source artwork and exported file separate in your review. A design canvas can be 1024 × 500 while an export multiplier produces 2048 × 1000. Inspect the exact file you intend to submit. The inline form compares numbers you enter; the file checker reads encoded dimensions and PNG color/transparency metadata in your browser. Neither route resizes or repairs the image.
For a PNG that looks fully opaque, check the metadata anyway. A file can contain an alpha channel even when every visible pixel appears solid. Export without alpha instead of merely adding a background layer and assuming the file format changed. Renaming a WebP to PNG also leaves the encoded format unchanged. Keep the original so you can return to the actual export settings.
Build a landscape composition around the app's useful task
Decide which product idea the graphic should communicate before moving artwork into a wider canvas. A fictional recipe notebook might show a recognizable saved-recipe scene. Repeating its square icon at a larger size leaves little information about that task. Use artwork you have rights to use, and check that any visible product interface represents the release and language you are promoting.
Google recommends keeping important content toward the center and avoiding cutoff zones. Its official preview guide includes a composition illustration; use that reference and inspect the console preview for your asset. The dimension diagram in this guide is a canvas reference, not a guaranteed safe area. Review small presentations and crop contexts rather than assuming every placement shows the entire export.
Resolve the specific upload or presentation problem
If the dimensions do not match, fix the source export dimensions first. If the dimensions match but the file check flags alpha or a non-RGB PNG, inspect the format settings. If the file cannot be read, open it in an image editor and export a fresh file. Do not diagnose every rejection as a size error: preserve the exact console message and identify which requirement it describes.
For a visually cramped result, reduce the competing messages before shrinking the text. Keep an app name, task scene and supporting caption from fighting for the same space. Ask a fresh reader what the graphic suggests the app does. If they infer a feature the current build lacks, adjust the composition or wording. Header checks cannot make that content decision for you.
Keep a review record for each locale
Save the intended listing, language, app build, source file and final export together. Review translated text in the actual artwork rather than approving a string in isolation. A longer translation can change line wrapping and obscure the main scene. Ask a suitable reviewer to inspect the meaning and presentation, then test the promised product action with safe sample data.
Record the console outcome separately from later traffic observations. A successful upload proves that step for that file and context; it does not show that Google featured the app or that the artwork improved conversion. Preserve the earlier graphic and concurrent listing or campaign changes. If you later run an eligible store experiment, use its report and decision settings rather than treating a casual before-and-after difference as proof.
Working example
Fictional export review: Family Recipe Notes uses a 1024 × 500 source canvas but exports at double size. The owner checks 2048 × 1000 in the form and receives a dimension mismatch. A new export uses the correct size, but the local file report detects PNG alpha. The owner exports RGB without alpha, inspects the image in an editor and asks a reader to identify the saved-recipe task. The record keeps all three exports and their separate findings. This is an export troubleshooting example, not a published customer result or evidence of ranking or conversion improvement.
Your next steps
- Inspect the exact final export at 1024 × 500 landscape pixels.
- Review encoded format and alpha separately from entered dimensions.
- Check the composition, locale and promised task against the release.
- Keep console validation and later performance measurements as separate evidence.
Questions about this guide
What size is a Google Play feature graphic?
Google documents a 1024 × 500 pixel landscape asset, in JPEG or 24-bit PNG without alpha. Confirm the current requirements in the linked official preview guide.
Can a feature graphic be 2048 × 1000?
That has the same proportions but does not match the documented 1024 × 500 target. Inspect your final export dimensions, including any editor export multiplier.
Does a white background remove PNG alpha?
Not necessarily. An opaque-looking image can retain an alpha channel. Inspect the actual file metadata and export without alpha rather than relying on appearance.
Are my image files uploaded to RateMyApp?
The linked file checker inspects selected files locally in your browser. The inline form submits entered dimensions only and cannot establish the actual file format, alpha or integrity.
Official sources
Sources checked October 5, 2026. Review the current provider documentation before acting on requirements.
Turn the next test into something useful.
Publish a focused brief on RateMyApp. Credits fund approved private reports; public store reviews are voluntary and unrewarded.
List your app for feedback