Responsive test — your site on 50+ devices

Latest flagships (iPhone 17 Pro Max / 17 Pro / 16 series / 16e, Galaxy S25 Ultra / S25+ / S25, Pixel 10 Pro XL / 10 / 9 series, OnePlus 13, Xiaomi 15), the previous generation for regression comparison (iPhone 15 series / SE, Galaxy S24, Pixel 8), foldables (Galaxy Z Fold 6 unfolded and folded, Z Flip 6, Pixel 9 Pro Fold), rotated landscape variants of the key devices, tablets (iPad Pro M4 13/11, iPad Air M3, iPad Mini A17 Pro, Galaxy Tab S10 Ultra/+), laptops (MacBook Air 13, MacBook Pro 14/16) and desktops (Full HD 1080p, QHD 1440p, 4K UHD, iMac 5K, ultrawide 21:9 and super-ultrawide 32:9). The picker groups presets by phone, tablet and desktop.

Phone and tablet viewports render with device-scale-factor 2 (Retina), touch input and a mobile user agent; desktop viewports render at 1x with a desktop user agent. The matching user agent is set automatically per viewport and cannot be overridden. Very tall mobile captures can therefore bind several hundred MB of memory per shot — which is why rendering runs in parallel by design rather than one at a time.

Own resolutions anytime: enter width (240–4000 px) × height (320–4000 px) plus an optional label. Up to 20 custom sizes can be combined with the presets per scan — handy for kiosk screens, embedded displays or a specific UI-QA resolution. The device class (phone below 600 px width, otherwise desktop) is derived automatically so custom sizes also get the right render profile.

Even pages that don't belong to your account — pull-request previews, customer staging, competitor comparison. Enter URL, pick devices, run the scan. Before each scan the target URL is resolved to a validated public IP and exactly that IP is pinned to the browser; targets in the private, loopback or link-local range are rejected (protection against SSRF and DNS rebinding). If the page follows a redirect, the history additionally shows the final URL that was actually captured.

Each shot is captured in headless Chromium. The page is loaded until networkidle, allowed to settle briefly and then scrolled through completely to trigger lazy-loaded content — afterwards it snaps back to the top and is captured as a full-page screenshot over the entire scroll height. In the history you see the measured scroll height and the file size per shot.

Both color schemes are captured in parallel by default — prefers-color-scheme is emulated per render at page level. You can also pick just one of the two. The total number of screenshots is viewports × themes; the app shows this calculation live before you start.

Multiple viewports are rendered simultaneously (default: 4 Chromium contexts in the same browser process, shared cache). This noticeably lowers wall-clock time versus sequential processing; the total duration depends on page size and the number of viewports and is shown per snapshot in the history.

The crawls automatically block tracking scripts and analytics beacons so no screenshot triggers foreign measurement requests and the image is not skewed by injected third-party overlays. Animations are disabled for the capture and the text caret is hidden, keeping the captures reproducible.

Each scan produces a snapshot whose screenshots appear side by side in a grid — so you can tell at a glance whether the hero image sits cleanly on iPad Mini while still working on the 4K monitor. Each tile shows the device label, pixel size, scroll height and file size; a click opens the lightbox at full resolution.

Snapshots stay in your history until you delete them. The account-wide overview shows the most recent 50 scans (website-bound and free URL scans together); the per-website view shows that site's most recent 30. Deleting removes both the database entries and the stored PNG files.