Feature
A screenshot of the problem, attached by the person who saw it.
“Can you send a screenshot?” is the most expensive sentence in support. It costs a round trip, and what comes back is often a photo of a monitor. The screenshot bug report the widget sends is taken in the browser, from the page they were actually on, in the moment they decided something was wrong.
Start freeNo credit card required.
How it works
- They press the button and describe the problem.
- They choose to attach a screenshot.
- The widget captures the visible page and shows it back.
- They send it, or discard the image and send the text alone.
No extension
Nothing to install, on either side
Every screenshot tool in this category asks somebody to install something — a Chrome extension for your testers, an SDK for your developers, or both. The widget is already on the page, so the capture is one tap for a person who has never heard of your bug tracker.
- Captured in the browser
- From the visible part of the page, at the size and zoom they were actually using — not a server-side render of the same URL.
- Shown before it is sent
- They see exactly what you will see. If a customer name is on screen and they would rather not send it, they discard the image and the report still goes.
- Never taken without asking
- There is no silent capture, no session recording and no replay. The widget takes one picture, when somebody presses the button that takes it.
- Deleted after 90 days
- Images expire on their own. The report and its technical detail stay; the screenshot does not linger in storage for years.
What it is not
One picture, not a session recording
Session replay answers a different question and carries a much heavier privacy bill: it records everything, from everyone, before anyone has decided there is a problem. This takes a single frame, only when a person asks for it, and only of the page they are looking at. Everything the widget sends is listed on the widget data page, written so you can cite it in your own privacy policy.
With the rest of the report
A screenshot is the least of what arrives
The image tells you what it looked like. Underneath it sits the JavaScript error and its stack frames and the last fifty things the person did. That combination is the difference between a picture of a broken page and a bug you can reproduce on the first try.
FAQ
Questions
- Does the reporter need a browser extension?
- No. The screenshot is taken by the widget already on your page, so there is nothing to install and nothing to grant permission to. That matters because the people most likely to hit a bug are the least likely to install anything to report it.
- Is a screenshot taken automatically?
- Never. The widget only captures when the person asks for one, shows them the result before anything is sent, and lets them discard it. A tool that screenshots without asking is a tool your legal team will eventually ask you to remove.
- How long are screenshots kept?
- Ninety days, after which they are deleted from storage. The report itself stays in your inbox with the description, the browser details and the steps — only the image expires.
- Can users annotate or draw on the screenshot?
- Not today. The widget captures the visible viewport and shows it back for approval, but there is no drawing layer. If arrows on a screenshot are central to how your team works, tools like Marker.io and BugHerd do that better.
Take a screenshot of this page.
Open the widget in the corner, attach a capture and send it. You will see exactly what your users would send you.