Reading a report

Finding it

Every report lands under Recordings, newest first. If you run several projects you can narrow it down to one site at a time.

Open one and you get, top to bottom:

• The screenshot or video, with the reporter's annotations already drawn on. Videos play right there — no download.
• Full page at time of report, if the reporter ticked that box — the whole screen they snipped from, folded away until you want it. It's off unless they ask for it, so most reports won't have one.
• Their note, and their voice note if they recorded one.
• The basics — when it happened, how long the video is, and the exact page URL. The URL is a link, so you can go straight there.
• Technical context — the errors, failed requests and click trail from their browser. See What gets captured.

Sending it to a developer

The person who has to fix the bug usually isn't you, and making them create a BugClip account first is a good way to make sure they never look at it. So every report can be turned into a link that anyone can open.

Open the report, find the Share link box, and hit Create share link. Copy the URL and send it to whoever needs it — Slack, email, a Jira ticket, wherever.

They see the same thing you do: the capture, the note, and the technical context. No account, no login, no BugClip.

Nobody can guess their way to one, though. The link ends in a random 32-character token — 128 bits of randomness, the same strength as a good encryption key. A computer trying a trillion links every second would still be working through the possibilities long after the sun burned out. Search engines are told not to index shared reports either, so they never turn up in results.

Changed your mind? Hit Revoke link and it stops working immediately, for everyone, including copies already pasted elsewhere. Sharing again creates a fresh link — the old one stays dead.

Reports are private until you share them. Shared ones are unlisted too: they aren't indexed by search engines and there's no way to browse to one without the link.

Deleting a report

Delete report sits at the top of the report, behind a confirmation. It removes the record and the stored screenshot, video and audio.

Deleting a whole project takes its reports with it — that lives on the Projects page. Deleting your account, on Account, removes everything.

Getting reports without checking the dashboard

Waiting for someone to notice a new report is how bugs go stale. Slack delivery posts each one into a channel as it arrives, with a View report button. One channel per project, so a client's bugs land where that client's work already happens.

Dark mode

The dashboard follows your system theme, and there's a toggle in the header if you'd rather pick. Reports look the same either way.

A note on report size

A report can be up to 4 MB in total — capture, full-page image and voice note together. That's generous for screenshots and page recordings, but a long screen recording can hit it. If a reporter ever tells you sending failed because the report was too big, Troubleshooting has the three ways to shrink it.

The This page recording, which is the default, is stored as an event log — a list of what changed on the page and when, rather than video frames. It's then gzipped, the same compression a .zip file uses, which shrinks it by roughly 10x because a list of small text changes repeats itself a lot. That's why it runs far longer before it gets anywhere near the limit.

If you're curious what's actually being stored: page recordings are .json.gz, screen recordings are .webm video, and screenshots are .jpg, with the full-page image kept alongside as its own file.