You found three problems on a staging build, your client is on the phone in ninety minutes, and the developer wants something written down. Do you spin up a BugHerd project, invite the client as a guest, walk them through the sidebar, and hope they pin the right element? Or do you open a tab, capture the screens, talk through what's wrong, and paste a link into Slack?
Both tools solve real problems. They solve different ones.
What BugHerd is actually good at
BugHerd anchors feedback to the live DOM. A reviewer installs the extension or loads the JavaScript snippet on the site, clicks an element, and the comment sticks to that element with the selector, browser, OS, and screen size attached. Those tickets land on a kanban board with statuses, assignees, and a backlog. For an agency running a six-month build with weekly client reviews, that is genuinely useful. Bugs accumulate, get triaged, get assigned, and get closed without anyone retyping them into Jira.
The board is the point. If you are managing twenty open issues across three reviewers and need to know which ones the developer has touched this week, BugHerd earns its keep. The same is true if you bill clients for tracked bug counts or need an audit trail of who reported what and when.
Where the project overhead gets in the way
The overhead has three parts: setup, reviewer onboarding, and the board itself.
Setup means adding the snippet to the site or asking the client to install the extension. On a production site you control, fine. On a staging URL behind basic auth, on a Figma prototype, on a competitor's site you want to critique, on a PDF, on a desktop app screen, the snippet model breaks down. The reviewer needs to install a browser extension, which is exactly what locked-down corporate laptops refuse to allow. We wrote about screen feedback when IT blocks browser extensions because this is a daily reality, not an edge case.
Reviewer onboarding means the client needs an account, a project invite, and a quick lesson on pinning. For a long engagement that is a one-time cost. For a single round of feedback from a stakeholder who reviews two designs a year, it is the whole job.
The board itself assumes you want a board. Sometimes you do not. Sometimes you want to send fifteen comments to a contractor, get them fixed, and never look at the list again.
What a no-login review link does instead
A no-login review link skips the project layer. You open Cobalt Capture in a browser tab, click Capture screen, share the window or tab the browser prompts for, crop the frame, and add a comment by typing or dictating. Repeat for each issue. Click Publish. You get a public URL at /r/<slug> that anyone can read, plus a PDF, a Word doc, and a markdown version at /r/<slug>/markdown. No install, no extension, no signup. The reviewer never makes an account; the receiver never makes an account.
What you give up: persistent status tracking across many reviews, assignees, a backlog view. What you gain: the work is done in the time it would take to invite someone to a BugHerd project. Receivers with the link can comment on individual items, and you can mark each comment resolved. That covers most of what people actually use a board's status column for on a single round.
If you typically run one-off reviews rather than long-running issue queues, the no-login alternative to BugHerd page lays out the workflow in detail.
Side by side on the decisions that matter
| Dimension | BugHerd | No-login review link |
|---|---|---|
| Setup on the site under review | Snippet or extension required | None; captures any screen |
| Reviewer account | Required (guest invite) | Not required |
| Anchored to live DOM element | Yes | No; cropped still with numbered pins |
| Persistent kanban with statuses | Yes | No; per-item comments with a resolved flag |
| Works on Figma, PDFs, desktop apps, competitors' sites | Limited | Yes; anything on screen |
| Output for a developer or agent | Ticket export | Public link, PDF, Word, clean markdown |
| Time to first sent feedback | Project setup plus invite | Tab open to published link in minutes |
| Price | Per-project plans | Free; account optional |
Which one fits which reader
Pick BugHerd if you run multi-month builds where the same site gets reviewed weekly, you need a backlog the whole team works from, and your clients are willing to log in. The board pays for itself across dozens of tickets.
Pick a no-login link if any of these describe you: the reviewer is a client who will not install anything, the surface is not a live web page you control, you only need one round of feedback, or the receiver is a contractor or AI coding agent who just needs a clear list of what to fix. The client feedback workflow and the staging site review page show this in context.
Plenty of teams use both. BugHerd for the long client project, a quick link when a stakeholder shows up with three comments on a marketing page. The choice is not religious. It is about whether you need a board this week or a list someone can read.
If you want to try the no-login path against your next round of feedback, start a review and send the link before your next call.