Usersnap vs BugHerd

Usersnap vs BugHerd: which one fits your team?

The short answer: BugHerd if the people giving feedback are clients and stakeholders reviewing a website, because pinning a comment to an element and watching it become a card on a board is the whole product and it is very good at it. Usersnap if you want bug reports and product research — surveys, NPS, feature requests — out of one tool, and if EU hosting matters to you.

They are less alike than the category suggests, and the differences that decide it are deployment, what gets captured, and where the data ends up. This page is published by BugBundler, which competes with both; there is a section near the end saying where we fit, and the rest is written to be useful whichever of the two you pick.

At a glance

Capability Usersnap BugHerd
The core idea A feedback and research platform: bug reports plus surveys, NPS and feature requests. Pin feedback to the element it is about; every pin becomes a card on a kanban board.
Who files reports Testers, support agents and end users. Clients and non-technical reviewers.
Deployment A code snippet on the site, plus Chrome and Firefox extensions and a mobile SDK. Browser extension — no snippet required on the site.
Console output Yes — browser info, user attributes, URL and JavaScript console errors attach automatically. Not advertised. Their features page lists browser, OS, screen resolution and the pinned element.
Surveys, NPS, CSAT Yes — CSAT, NPS, polls and conditional questions. No.
Task board built in No — it pushes into your tracker instead. Yes, and it is the centre of the product.
Entry price Free for your first 20 feedback items with no time limit; paid tiers by seat count, prices not published. $50/month for 5 members; $80 for 10; $150 for 25. Annual billing gives two months free.
Report data location AWS eu-central-1 (Frankfurt) May transfer to and from any country, including Australia, the UK and the US, per their privacy policy.
Named integrations Jira, Azure DevOps, Zendesk, Slack, GitHub, and 100+ overall. Asana, ClickUp, Monday.com, Trello, Jira, Linear, GitHub, Slack, MS Teams, WordPress, Zapier and more.

The difference that actually decides it

Both tools collect visual feedback from a browser, which is why they end up on the same shortlist. But they were built for different people, and the mismatch shows up in week two rather than during the trial.

BugHerd is a review tool. Its model is that a non-technical person looks at a page, clicks the thing that is wrong, and types a sentence. That pin is attached to the element, so nobody has to write "the heading above the pricing table, on mobile". The pin lands on a kanban board that the agency or in-house team then works through. If your inbound feedback is mostly copy changes, layout complaints and client sign-off, this shape fits, and its long list of project-management integrations — Asana, ClickUp, Monday.com, Trello — tells you who it is for.

Usersnap is a feedback platform. Bug capture is one of several things it does; the others are CSAT and NPS surveys, polls, and structured feature-request collection, with conditional questions. It attaches technical context automatically, including JavaScript console errors, browser details and the URL. If you want one tool that serves QA and product research, that breadth is the reason to pick it. If you only want bug reports, you are paying for surface area you will not use.

Deployment: a snippet or an extension

This one is worth checking before you start a trial, because it can settle the decision on its own.

Usersnap wants a code snippet placed in your HTML once, or its WordPress plugin, and offers Chrome and Firefox extensions plus a mobile SDK alongside. The snippet is what makes end-user feedback and in-product surveys possible — you cannot survey your users through an extension only your team has installed.

BugHerd deploys as a browser extension with no code setup, which is a real advantage when the site belongs to a client whose developers you do not control, or when getting a script through someone else's release process would take three weeks. The trade-off is the same one in reverse: an extension only collects feedback from people who install it.

If your test target is a site you do not own, or a production environment where adding third-party JavaScript needs security review, weight this heavily. It is also the reason some teams end up ruling out both.

Pricing compared

BugHerd publishes its numbers: Standard at $50/month for five members, Studio at $80/month for ten, Premium at $150/month for twenty-five, and a custom tier above that. Paying annually gives two months free, which works out to roughly $42, $67 and $125 per month. Members are seats, so growth is stepwise rather than per person.

Usersnap does not publish prices on its pricing page at the time of writing. The tiers are defined by seats — Starter at five, Growth at ten, Professional at twenty, Premium at fifty and Enterprise unlimited — so budget for a sales conversation. What it does offer is the better evaluation path: the free tier covers your first 20 feedback items with no time limit and no credit card, so you can run it against a real project rather than racing a 14-day clock.

Practical note: compare at the seat count you will have in a year, not today. Both products price in blocks, so crossing from five members to six can cost more than the six months before it.

Where the data goes

Both are hosted products, so in both cases your captures — screenshots of whatever was on screen, which in a test environment is often real or realistic customer data — are stored by the vendor for the life of your subscription. The difference is where.

Usersnap hosts report data on AWS in eu-central-1 (Frankfurt). For a European team, that is a straightforward answer to give a procurement reviewer.

BugHerd's privacy policy reserves the right to transfer data “to and from any country, including Australia, the United Kingdom and the United States of America”, and notes that information may be maintained on computers outside your jurisdiction “where the privacy laws may not be as protective”. For EU residents it relies on consent and on the European Commission's model contractual clauses. That is a lawful basis and plenty of companies accept it — but if your own customers audit your subprocessor list, it is a longer conversation than Frankfurt.

If data residency is the reason you are comparing these two at all, the question to put to either vendor is concrete: after a capture, which of your systems holds a copy of it, in which country, and for how long?

Choose BugHerd if

  • Your reviewers are clients or non-technical stakeholders, and the feedback is about what a page looks like.
  • You want the task board inside the tool rather than pushing everything into Jira.
  • You cannot get a script added to the site under test.
  • You run an agency and live in Asana, ClickUp, Monday.com or Trello.
  • You want published pricing you can budget against without talking to anyone.

Choose Usersnap if

  • You want bug reports and product research — NPS, CSAT, feature requests — from one tool and one budget line.
  • You need feedback from real end users, not just your own team, which needs the in-page snippet.
  • JavaScript console errors attached to reports matter to your developers.
  • EU hosting is a requirement you have to be able to evidence.
  • You want to evaluate properly on a free tier before committing.

A third option, and our disclosure

We make BugBundler, so weigh this accordingly. It is worth mentioning only because it answers a requirement neither of the two above can meet at any price: not having your captures stored by a vendor at all.

BugBundler is a browser extension that captures the screenshot, console output, network requests with headers and bodies, a DOM snapshot and the environment, and writes all of it to a single portable HTML file on the reporter's own machine. There is no snippet on the site under test and no dashboard of your captures on our side. Since version 1.4 it can also file a report into your own Jira as an issue, with the screenshot and the full report attached to the ticket; that send passes through EU infrastructure in Finland for one request and is discarded, never stored.

It is a narrower tool than either of these. There is no kanban board, no surveys, no public feedback widget, no session replay and no two-way tracker sync, and at $27–29 per seat per month with a five-seat minimum it is not the cheap choice. It exists for teams whose test environments contain data that cannot be uploaded to a third party. If that is not your constraint, one of the two above is probably the better answer.

Head-to-head detail: BugBundler vs Usersnap, BugBundler vs BugHerd, or the wider comparison of six tools in this category.

Frequently asked questions

Is Usersnap or BugHerd cheaper?

BugHerd is the one you can price without talking to sales: $50/month for five members, $80 for ten, $150 for twenty-five, with two months free on annual billing. Usersnap does not publish its paid prices, so a direct comparison is not possible from the public pages. Usersnap does have the more generous free entry point — your first 20 feedback items, with no time limit.

Does BugHerd capture console logs?

Not as an advertised feature. BugHerd's features page lists browser, operating system, screen resolution and the element the feedback is pinned to. Usersnap does attach JavaScript console errors along with browser info and the URL. If console and network detail is central to how your developers work, that difference matters more than anything else on this page.

Do I have to install a script on my website?

For Usersnap, yes for the full product: a code snippet goes into your HTML once, or you use the WordPress plugin. It also has Chrome and Firefox extensions and a mobile SDK. BugHerd deploys as a browser extension with no code setup, which is why agencies working on client sites often prefer it.

Which one is hosted in the EU?

Usersnap hosts report data on AWS eu-central-1 in Frankfurt. BugHerd's privacy policy states that data may be transferred to and from any country, including Australia, the United Kingdom and the United States, relying on consent and the European Commission's model contractual clauses for EU residents.

Can either of them keep bug reports off a vendor's servers?

No. Both are hosted products, so captures are stored by the vendor while you are a customer. That is the trade you make for a shared dashboard and a workflow that lives online. If storing captures with a third party is not acceptable in your environment, you need a local-first tool instead — BugBundler, which we make, is one, and the section above is candid about what it gives up in exchange.

Which has better integrations?

It depends which stack you mean. BugHerd names a wide spread of project-management tools — Asana, ClickUp, Monday.com, Trello, Jira, Linear, GitHub, Slack, MS Teams, WordPress, Zapier. Usersnap claims 100+ integrations overall and specifically names Jira, Azure DevOps, Zendesk, Slack and GitHub, with Zendesk pointing at its support-desk leaning.

If neither fits

Capture one bug and see what a local report looks like

If the blocker on both of these is that your captures would sit on someone else's servers, install BugBundler, capture a bug in your own environment, and open the file it produces. That is the whole evaluation — nothing hosted by us, and no account for whoever you send it to.