Official source · current
Google Play preview asset requirements ↗
Source verified 2026-08-14. Reviewed on the recorded date. Confirm the active notice for your exact application. View source register.
Destination validator · browser local
Audit Google Play images as a set.
Use a current feature-graphic, icon, or screenshot profile to see the measurable differences in a selected local asset set before you export corrected files.
What this workspace does
A measured store-asset report and a route into the existing Google Play pack builder.
Use it accurately
Google Play requirements can change. Use the current Play Console help documentation as the final authority.
Private browser processing
Selected files are processed in the current browser session. Aftermath has no account, cloud file storage, or server-side file-processing job.
How to check your file
Audit Google Play image assets locally against the measurable rules you enter from the current official guidance. The result reports file and canvas comparisons with warnings, not a submission approval or a claim of store acceptance. Check the current Google Play documentation, the actual asset content, and the target listing before delivery.
What to choose and what you get
What to choose
- Google Play preview assets and the active device rules
Result
- a measured Google Play asset comparison with warnings
Supported formats
- Accepted formats: JPG, PNG, WebP.
- Output formats: HTML report.
Browser support and permissions
- Modern browser with JavaScript, a supported image decoder, and enough memory for the selected set.
- No camera, microphone, or screen permission is needed.
Worked example
A Google Play icon, feature graphic and screenshot set needs local measurement against the active asset rules.
Starting facts
- Each asset has a different role and canvas requirement.
- Current Google Play documentation remains authoritative.
- Synthetic measurement example: a 512 × 512 test icon has the expected square pixel canvas for the bundled Google Play icon preset.
Observed operation: Choose the asset category and compare decoded pixels, bytes and format with the corresponding active rule.
Review the result: Matching pixel dimensions alone is insufficient: inspect the measured format and bytes, then review artwork and current destination rules. Open the icon resizer if the canvas differs.
Boundary: The validator cannot guarantee Play review, listing quality, device authenticity, policy compliance or future rule stability.
Check your result
- Google Play requirements can change. Use the current Play Console help documentation as the final authority.
Things to know
- External requirements can change; compare the result with the current official source before submitting it.
Privacy boundary
Selected image bytes and entered rule values stay in the current browser session and are not sent to an Aftermath processing service. How local processing is verified.
What this tool verifies
Checks the displayed limits and reports or creates a measured Google Play asset comparison with warnings from Google Play preview assets and the active device rules.
Check before sharing
A measured pass checks the entered file rules; it does not guarantee acceptance by the external destination.
Result checks
Method and observed boundary
Read the worked example and result review
Checks represented by this receipt
- local file boundary: verified
- image measurement: verified
- validator transparency: verified
Limitation: The validator cannot guarantee Play review, listing quality, device authenticity, policy compliance or future rule stability.
Tested 2026-09-01. Deterministic release regression; cross-browser compatibility is not asserted.