Screen recorder for bug reports
Record the bug. The rest attaches itself.
One script tag on your client's site. You hit record, or they do — it lands in your Slack, ready to fix.
For agencies and freelancers · Free for your first project · No card required
“The Place order button just spins forever.”
Reported today at 9:41 AM · acmestore.com
Checkout
- Anglepoise desk lamp$189.00
- Express shipping$12.00
- Promo CART10 ✓−$20.10
⨯ TypeError: Cannot read properties of undefined
The bug exactly as it happened. The red dot on the timeline marks the moment it broke.
- Duration
- 0:41
- First error
- 0:34
- Captured
- Today, 9:41 AM
- Clip size
- 2.1 MB
One button, pressed once. The clip — and everything on the other tabs — came with it.
How it works
Three steps. Then you never ask “what browser?” again.
- 1
Paste one line
One script tag per client site. No installs, no extensions, no plugin to keep updated.
- 2
Hit the button
Record the screen or grab a screenshot, say what broke, send. Thirty seconds — you or the client.
- 3
You get the whole story
Video, console errors, failed requests, click trail. In Slack, tagged by site.
Everything a bug report leaves out, attached automatically.
One script tag
Copy. Paste. Done.
Nothing to install, nothing for their dev to review. One line of HTML and anyone on that site can file a real bug report.
<!-- that's it --> <script src="https://bugclip.dev/widget.js" data-project-key="pk_xxxx"></script>
Slack delivery
Ten client sites, one channel
Every report drops into your Slack the moment it's sent, tagged with the site it came from. No inbox to check, no portal to log into.
BugClipApp9:41 AM
New bug report from acmestore.com
“The Place order button just spins forever.”
View full report →
Make it yours
Your widget, your client's brand
Color, wording and corner, set per project from your dashboard. Nobody has to touch the client's site again.
Grab the controls — the button in the bottom right of this page is live
Privacy by default
All the context, none of the creepy parts
BugClip is not an always-on camera pointed at your client's users. Nothing is captured until someone hits record. Their data stays theirs.
- No request bodies, no response bodies, no headers
- Nothing typed into a form. Ever.
- Capture starts on their click — never before
Pricing
One price, all your client sites
Ten client sites cost the same as two.
Free
$0/mo
Try it on one site. Record a few bugs and see.
- 1 project
- Screenshot & video reports
- Reports dashboard
Pro
$39/mo
For every client site you run — with the reports landing in Slack.
- Unlimited projects
- Slack delivery, per client site
- Console errors, failed requests & click trail
- Everything in Free
FAQ
The questions you're about to ask
BugClip (bugclip.dev) is a bug reporting tool for agencies and freelancers. You add one script tag to a client's site, and anyone on that site can send you a screen recording of a bug — with the console errors, failed network requests, click trail and device details attached automatically. Reports land in your dashboard and, on Pro, in your Slack.
No. The widget works for anyone visiting the site — they click the button, record their screen or grab a screenshot, type what went wrong and hit send. No sign-up, no install, nothing for you to walk them through.
No. It's one small script that loads after the page is done, and it stays out of the way until someone actually opens the widget. From the moment it loads it keeps a short rolling list of console errors and failed requests in memory — that costs nothing you'd notice, and it's what lets a report show what broke in the moments beforehand. No recording happens, and nothing leaves the browser, until your client sends a report.
The screen recording or screenshot, the console errors with stack traces, the failed network requests, the click trail leading up to the bug, and the device & browser details — viewport, screen size, timezone, platform. Everything you'd normally have to ask for in a follow-up email.
No. Nothing is recorded and nobody is watched — recording only ever starts when someone clicks the button. The widget does keep a short rolling list of console errors and failed requests in the browser's own memory, so that when a report is sent it can show what broke in the moments leading up to it. That list holds only the most recent entries, none of it leaves the visitor's browser unless they choose to send a report, and it's gone the moment they close the tab. Nothing typed into a form is ever captured, and request bodies and headers are never collected. Their data stays theirs.
On Free, one project — enough to run BugClip on a single client site indefinitely. Pro is one flat price for unlimited projects, so ten client sites cost the same as two. Every new account also starts with 7 days of Slack delivery and full technical context switched on — still one project, but every report arrives with everything Pro sends — and that clock only starts when your first bug report actually arrives, not when you sign up, so you can take your time getting installed.
On Pro, you connect a Slack channel and every report is posted there as it arrives, tagged with which client site it came from. One channel, all your clients, no extra inboxes.
Something else on your mind? The docs cover the rest.