Destination asset integrity
Store asset preflight: technical image checks versus authentic product evidence
A correctly sized screenshot is not necessarily an authentic screenshot. Technical preflight can catch canvas, bytes, format, and sequence issues, but it cannot prove that an asset truthfully represents the product or meets a platform’s changing review policy.
On this page
Treat a preset as a technical starting point
A destination-oriented preset can make measurable dimensions and format choices visible. It is valuable because it removes avoidable file errors and points to the relevant source—not because it controls the platform’s final decision.
Before relying on any stored setting, open the active official notice. Platform asset rules can change, and a specific product may have additional requirements.
Authenticity cannot be added by padding or scaling
A mobile capture padded into a tablet canvas may meet pixels while misrepresenting the product. A blurred backdrop or crop can be a deliberate visual treatment, but it does not make the source an authentic device capture.
Use a tool to normalize a source that already represents the right product and device context. Keep a record of what was changed after capture.
| A local preflight can check | A human/platform review still decides |
|---|---|
| Canvas dimensions, file bytes, MIME type, alpha, and aspect ratio | Whether the asset accurately represents the product |
| Output order and clearly named files | Rights, branding, localization, and editorial suitability |
| Measured warnings about crop and enlargement | Whether the active platform policy permits the asset |
Build a reviewable asset pack
Keep original captures, selected destination variants, and the result receipts together until submission is complete. A named ZIP can make the handoff clearer, but it should never obscure which source or device group produced a specific result.
Review each crop at the actual target size. A technically valid source can still hide text, a consent screen, an unfinished state, or another detail that makes the asset misleading.
Make claims that match the evidence
The appropriate promise is that the tool checks selected technical output properties locally. It must not promise store approval, platform affiliation, or a result that it cannot observe.
Primary workflow evidence
Reproducible check behind this guide
Select the device family and compare each local image's decoded pixels, bytes and format with the active rule set.
Expected review: The synthetic fixture matches the selected width and height; format and byte checks must also pass. For a real submission, review genuine UI content, localization, and the current destination rules.
Boundary: The validator cannot certify store review, device authenticity, localization quality, rights or future Apple requirements.
Tested 2026-09-01. Deterministic release regression; cross-browser compatibility is not asserted.Use a local tool