When does Snags start recording?

Only when you start an audit on a website, and then only on that website’s pages. Before that it reads nothing from the site.

Is the replay a video?

No. It’s a recording of what changed on the page, covering the last 30 to 60 seconds, and up to 90 seconds back when you moved between pages of the site.

Does anything leave the browser while I comment?

The text of each comment syncs as a draft. Screenshots, replays and errors stay in your browser until you publish the audit.

What about request bodies?

For a request that failed, Snags keeps its headers and bodies so the comment shows the actual error. Credential headers are redacted, bodies are swept for secrets and cut short, and uploads are never kept.

Capture the evidence once. Every comment shows what broke.

While an audit runs, Snags keeps a short record of the page in your browser. When you comment, the screenshot, the replay, your steps, the console errors and failed requests from the moments before go with it.

Add to Chrome Read the docs

app.snags.com/a/Qvq6Rpq0

Checkout reviewacme.com4 commentsShare

1Nothing happens when I tap PayCheckout · Open
2The heading should say “Checkout”Checkout · Fixed
3Footer links are too small to tapCheckout · Open
4Coupon field loses focus on typeBasket · Open

1Nothing happens when I tap Payacme.com/checkout

Steps before it

Opened /checkout−9.0s

Clicked “Apply coupon”−3.1s

POST /api/coupon 500−2.8s

TypeError total is undefined−2.7s

Clicked “Pay now”−0.4s

Captured with it

BrowserChrome 141

SystemmacOS 15.1

Screen1440 × 900

Elementbutton.pay

Most feedback is a sentence and a guess. Snags attaches what actually happened, from the steps you took to the request that failed, so nobody has to ask.

What comes with a comment. Without asking anyone.

You write one sentence. Snags attaches the technical side, in order, so the first person to open the link can start.

Point at it, say what’s wrong. The screenshot, replay and errors attach themselves.

The errors behind it, console errors and failed requests from the moments before.

Where it happened, with the browser, system, screen and page on every comment.

Works withLinearGitHubJiraand any MCP client

See integrations

How it works. Three steps, nothing to install on the site.

01Start an audit
Open the website in Chrome, click Snags in the toolbar and start an audit on that site.
02Point at it
Click the element that’s wrong and say what’s wrong in a sentence. Then the next one.
03It comes with what happened
Each comment carries the screenshot, replay, steps, errors and browser, ready to share.

Plans from $5 a month, with links that never expire.

See pricing

Questions, answered.

The page and the element you clicked, a screenshot cropped to it with a Full view of the whole viewport, a replay of the moments before, your steps, and the console errors and failed requests from about 30 seconds before it.

More of the platform. The other parts of Snags.

Triage. Open, fixed or won’t fix, with replies, assignees and a check on the live site.

Privacy. Recorded only while you audit, and masked before it leaves your browser.

Sharing. One link anyone opens, with every comment, screenshot and replay.

Your next round of feedback, in one link.

Add to Chrome What gets captured docs