Compare an approved mobile frame with a connected-device capture or uploaded screenshot while accounting for screen size, density, safe areas, and system UI.
Use the approved Figma frame for the same platform, theme, content, and interaction state as the implementation. A compact phone and a large phone should be treated as separate acceptance conditions rather than scaled versions of one reference.
Pixel Perfect UI provides controls for cropping or excluding system regions so those pixels do not hide meaningful interface differences.
Start with clipped actions, content under system bars, keyboard collisions, unsafe-area overlap, unreadable hierarchy, and missing assets. Decorative offsets matter, but they should not outrank defects that prevent someone from completing a task.
Attach the design reference, app capture, device configuration, and useful comparison view to the release record. Repeat the comparison after corrections and keep accepted captures available for later baseline checks.
Repeat visual checks across controlled device conditions.
Locate safe-area, density, and responsive drift.
Validate shipped screens against platform-specific intent.
Keep visual approval evidence with the release.
Yes. Capture or upload the platform-specific screen and compare it with the corresponding Figma frame or exported design.
Configuration options help crop or exclude top and bottom system regions so the design and app capture can be aligned accurately.
No. Continue testing interaction, accessibility, performance, permissions, networking, and platform behavior separately.
Configure the source, capture, viewport, and comparison views in one visual QA workflow.
Try Pixel Perfect UI