For support and QA teams
See what the customer sees, errors and all
Capture the reported page at the customer's screen size, with its console errors and failed requests drawn on the image.
The problem
"The checkout page is broken on my phone." The support agent opens it on a desktop and it works. Engineering asks for a screenshot and the console output, which the customer cannot provide, and the ticket waits.
How domscout handles it
Capture the URL from the ticket at a phone's viewport with isMobile and hasTouch, so the page serves its mobile layout and touch behaviour. debugOverlay draws the page's console errors, uncaught exceptions, failed requests and oversized assets onto the image itself, so the screenshot attached to the ticket carries the evidence an engineer would have opened the developer tools for. A problem that depends on the customer's own account or session still needs their details, which this capture does not have.
Where it shows up
- A support macro that attaches a phone and a desktop capture to new tickets.
- Triage of bug reports before they reach engineering.
- A record of what the page looked like when the report came in.
The request
POST /screenshot. Available on every plan, including the free Hobby plan, at 1 credit. For the same findings as JSON, diagnostics starts at Pro.
Go further
More in Testing and QA: Responsive layout checks · 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 · 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.