Usersnap vs BugHerd vs Marker.io: which one fits your team
Three visual feedback tools that look identical on a feature grid, and the two questions that actually separate them.
These three are the established names in visual website feedback, and their marketing pages are close to interchangeable: a widget, a screenshot, an annotation layer, an integration with your issue tracker. The differences that matter are structural, and they are not on the feature grid.
Two questions that decide it
Who is reporting? If it is your clients and stakeholders reviewing work, you want annotation and a review workflow. If it is your own users hitting bugs in production, you want technical context and a flow that does not require an account.
What does the price scale with? Seats, projects, or volume. On a fifteen-person agency this single axis outweighs every feature difference between the three.
Everything below follows from those two.
BugHerd
Built for the agency review cycle, and it is the most opinionated of the three about it. The pin-a-comment-to-an-element model is the product, not a feature of it, and the kanban board behind it is designed for the back-and-forth of client sign-off.
Priced per seat, from around $50 a month. That is the tell: it assumes a defined internal team, and it charges for the people managing the feedback rather than the people giving it.
Pick it if clients marking up a staging site is your core workflow.
Marker.io
The most developer-adjacent of the three. Its centre of gravity is the handoff into Jira, Linear, GitHub or Trello — a report becomes a properly formed issue in the system your engineers already live in, with technical metadata attached.
Priced per project, from around $39 a month, which suits a team with a small number of long-lived products better than an agency with twenty concurrent client sites.
Pick it if the important thing is that the issue lands in your tracker, correctly formatted, without anybody retyping it.
Usersnap
The broadest of the three and the most enterprise-shaped. It covers bug reporting but also surveys, NPS and general product feedback, with the workflow and permission machinery that implies.
From around $69 a month, tiered by volume. It is priced and built for organisations that want one feedback platform rather than a bug tool.
Pick it if you need feedback collection across a company, not just bug reports on a site.
Where all three are the same
They share a premise: feedback comes from a known, invited reviewer marking up a page. That premise is correct for agency work and staging reviews, and it quietly excludes the largest group of people who could tell you something — the actual users of your live product.
They also share a shape: the value is in getting the comment out of a chat thread and into a tracker. If your problem is that you cannot reproduce what your users report, none of the three solves it directly, because a screenshot with an arrow on it is not a stack trace.
Where UserWants sits
Different premise, and worth stating plainly: no annotation layer, no integrations with Jira or Linear, no session replay. If you need any of those, one of the three above is a better tool and you should use it.
What it does instead is assume the reporter is a stranger. No account, no invitation, nothing to install — and the report arrives carrying the browser, the viewport, up to ten JavaScript errors with stack frames, and the last fifty things the person did. Plus an MCP endpoint, so a coding agent can read the report without you pasting it.
A short decision rule
- Clients marking up staging → BugHerd
- Issues landing cleanly in Jira or Linear → Marker.io
- Company-wide feedback, surveys included → Usersnap
- Anonymous production users, with the technical context → UserWants
Detailed one-to-one comparisons, including where each of them beats us, are on the alternatives pages.