For teams that design for every screen
See a page at phone, tablet and desktop size in one request
One capture returns the page at phone, tablet and desktop size, ready to review side by side.
The problem
A layout that works at 1280 pixels breaks at 375, and the first person to see it is a customer on a phone. Checking every size by hand in the browser's device tools is slow enough that it stops happening.
How domscout handles it
Set captureMode: grid and one request returns three images: a phone at 375 by 812 and a tablet at 768 by 1024, both at double pixel density with a mobile user agent, and a desktop at 1280 by 800. The page loads once and is resized between shots, so a layout that only decides its size when the page first loads can look different from a fresh load at that size. Markdown, if you ask for it, comes from the desktop view.
Where it shows up
- A review step that attaches all three sizes to a pull request preview.
- A before-and-after record when a design system changes.
- Spot checks of landing pages across screen sizes.
The request
POST /screenshot. Available on every plan. A grid capture costs 3 credits and the images come back as mobileBase64, tabletBase64 and desktopBase64. It takes longer than a single capture, and if the three images are too large to return inline, the response is a 202 with a job to poll.
Go further
More in Testing and QA: Visual regression testing · JavaScript error checks · Signup and checkout flow checks · Hover, focus and dark mode screenshots · Localization screenshots · Unlabelled control checks · A screenshot of every step · Embedded widget checks · Screenshots for support tickets · Ad landing page checks · Before and after hydration · Selectors for test automation · Print layout checks · All use cases
Give your product a browser.
Get clean web content and visual proof into your workflow in minutes.