Record the tab, the console and what you did — in one report that never leaves your browser.
Users
8
+4 in 30 days
Rating
0.0 / 5
unchanged in 30 days
Ratings
0
0 in 30 days
Store rank
#213K
#178K among extensions
Version
0.7.0
updated 20 Sep 2026
Users
monthly, 2 months
Latest, 16 Oct 2026:8 usersMove the mouse over the chart for any month
Ratings count
monthly, 2 months
Latest, 16 Oct 2026:0 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About Snag Capture
Snag Capture records what actually happened, so a bug report does not depend on somebody remembering it right.
Start a run on the tab you are testing. Snag records the screen, the console output, uncaught exceptions and the steps you took, and turns all of it into a single report — the video and the log lined up against the same timeline, with the exception name where you can read it.
WHAT IT CAPTURES
• Tab video — the screen at the moment it broke
• Console — log, warn, error, and whatever the page printed
• Exceptions — uncaught errors and rejected promises, with the exception name
• Your steps — clicks, navigation and form actions on the timeline
• Screenshots — the exact area you pick, kept in the report at the second you took it
• Network — every fetch and XMLHttpRequest the page makes, with status and timing; the body of a request only when it failed
• Environment — browser, platform, window size, pixel ratio, theme and connection at the moment recording started
• Page clones — the markup, the stylesheets, the fonts and the animations of any page, turned into a prompt
TWO MODES
• Bug mode, for reporting: what you type runs through the secret filter before it reaches the report
• Test mode, for checking a fix: steps keep their real values so the run can replay itself on the page, and a consent notice appears before recording starts
SCREENSHOTS OF EXACTLY WHAT YOU MEAN
Drag to choose the area — one panel, one error message, not the whole tab. Take one while recording and it lands in the report next to the video, at the second it was taken. Arrows, boxes, numbered notes and a pixelate tool are there whenever you want them, and the original capture is kept, so an annotation is never the end of the road.
CLONE A PAGE INTO A PROMPT
Building something and want a page's layout and motion as a starting point? Clone it. Snag reloads the page, scrolls it end to end and collects what an assistant would need to rebuild it: the markup, every stylesheet, the fonts, and the animations — including the ones written by scripts, read as they run rather than guessed from a file. You get a single prompt to paste wherever you like, plus the page as a standalone HTML file. What you do with it is your call; Snag sends it nowhere.
SECRETS STAY OUT OF THE REPORT
Console output and the bodies of failed requests are filtered for well-known credential formats — JSON Web Tokens, API keys, GitHub and AWS tokens, bearer tokens — along with fields and headers named like password, token, authorization or cookie, plus common personal data such as e-mail addresses and card numbers. Request headers are never captured at all. Treat the filter as a safety net and still review a report before sharing it.
NOTHING YOU CAPTURE LEAVES YOUR BROWSER
There is no server, no account and no telemetry. Nothing you record or clone is uploaded anywhere — open your browser's Network panel while you record and watch nothing leave. Recordings and clones live in IndexedDB in your own Chrome profile and stay there until you delete them; removing the extension removes what it stored, and files you exported stay where you saved them. Sharing is always a deliberate act: you export the report or copy the prompt and decide where it goes. If you hand an export to an AI assistant, what it reads goes to that assistant's provider — video frames included, which no filter touches.
The one exception is worth stating plainly. Cloning a page needs the CSS the page applied, and a stylesheet served from another origin cannot be read from the page itself. So the extension fetches it from the same address the page already loaded it from, without cookies or credentials — and the same for images and fonts if you ask for them to be packaged. Those requests go to the servers the site already uses, never to a server of ours, and carry nothing about you.
WHY IT ASKS FOR ACCESS TO ALL SITES
A bug can happen on any page, and a page worth cloning can be any page, so the extension cannot know in advance which site you will need. The access is used only on the tab you acted on, during a run or a clone you started, and it is what lets a clone fetch the stylesheets the page had already loaded. It is not used to read your history or browse in the background.
Beta. Free, and staying free.