Google Play app icon size: check a 512 × 512 PNG

Choose the store listing icon, not a launcher asset

Google’s listing-icon specification is separate from Android adaptive launcher icons. Keep distinct destinations in your export record so a similarly named source file does not become the wrong upload. Apple has its own workflow: add icons through Icon Composer or an Xcode asset catalog, then upload the build. A Google Play export is not a universal mobile app icon package. This guide checks the ordinary Play listing asset; watch-face requirements need their own reference.

For an indie team, a small asset record can prevent a late handoff mistake. Give the record five fields: destination, source design, exported filename, observed dimensions and reviewer. A fictional recipe app might keep mealnote-play-listing.png next to its launcher source, with each destination written in the record. Use a new filename when testing a new draft, while preserving the previous version. A filename helps trace the export but does not establish its encoded format.

Keep alpha and file-size checks separate from appearance

The checker reads encoded PNG metadata. An 8-bit RGBA PNG has a 32-bit pixel format even when every visible pixel looks opaque. For the listing icon, alpha is expected rather than the screenshot warning. A JPEG renamed with a .png suffix remains a JPEG. The local report also compares the encoded byte count with 1,048,576 bytes, its stated interpretation of the listed 1024 KB limit. The store console remains the final validator.

Example export review: your designer sends a 512 × 512 image that opens correctly, but the tool reports a JPEG. Return to the source editor and export the required PNG format; do not rename the existing file. For a second draft, the PNG has the correct dimensions but the report identifies an RGB header rather than RGBA. Review the editor’s color and alpha export options, then check the new file. The report should record what was inspected, rather than promising submission success.

Review the small icon as a separate design decision

Google applies the listing display mask and surrounding shadow, so its guide calls for a square source without baked outer corners or an outer drop shadow. It also rules out misleading rank or deal messaging. These are artwork decisions that the header checker cannot evaluate. Inspect the intended background and small presentation in your design tool; the checker does not decode the pixels or verify sRGB. A clean technical result still leaves a visual review to complete.

Try an original comprehension exercise before changing a live listing. Show two fictional notebook icons at a small size without their app names, and ask a person which task each suggests. Record their words before explaining the intended meaning. If both look like chat apps, the problem may be the symbol rather than the export dimensions. This exercise supplies observations about comprehension, not an estimate of install lift. Keep any eventual store experiment’s audience and measurement separate from this informal comparison.

Preserve an export decision you can revisit

A useful handoff says what changed and what evidence was checked. Instead of icon fixed, write: re-exported the square source at 512 × 512; local report detected 8-bit RGBA PNG; encoded file size was within the checker’s limit; color profile and artwork were reviewed in the editor. Add the review date and the exact file. Leave any unanswered question in the record so the next person can finish it rather than assuming every requirement was tested.

If the console still rejects the file, preserve its exact error and the rejected export. Compare those observations with the source settings before trying another variation. A console error can refer to a requirement the local header tool does not inspect, or to a damaged image payload. Re-export from the editable source instead of repeatedly converting a file of uncertain origin. If you change the design too, keep that as a separate draft so a format repair and an ASO experiment do not become one unexplained change.

Your next steps

• Record Google Play listing icon as the intended destination.
• Inspect the actual exported 512 × 512 PNG, not just the source canvas.
• Check RGBA metadata and encoded bytes with the local file tool.
• Review sRGB, masking, artwork and console feedback separately.