Start free

Feedback widgets, and how much of the report they fill in

A feedback widget is one script tag that puts a button on your site and turns whatever somebody clicks into a report. What separates them is how much of that report they fill in without being asked: a screenshot alone, or a screenshot with the console, the network requests, the browser and the minutes before it. Userback, Marker.io, BugHerd and Notarus all ship one, and their free tiers differ more than their paid plans do.

Start free What each one costs

4 tools · Prices read 13 September 2026

What each one costs

Prices and plan contents read from each vendor's own pricing page on 13 September 2026.

  • Userback

    Entry paid price
    Team, $39 a month or $29 billed annually, for 5 seats and 5 projects
    Free tier
    Free Forever: 2 seats, 2 projects, and feedback stays visible for 7 days
    Best for
    Teams that want two free seats now and a ladder to climb later

  • Marker.io

    Entry paid price
    Starter, $59 a month or $39 billed annually, for 3 users and up to 10 projects
    Free tier
    None. Reporters are free and unlimited on every paid plan
    Best for
    Agencies with many client sites and few internal seats

  • Notarus

    Entry paid price
    Pro, $19 a month, for unlimited seats and 20 projects
    Free tier
    unlimited seats, 5 projects, with session replay and the full MCP server included
    Best for
    Teams who want the console and the session attached to the report without reaching a paid tier

  • BugHerd

    Entry paid price
    Standard, $50 a month or $42 billed annually, for 5 members
    Free tier
    None, though guests and projects are unlimited on every paid plan
    Best for
    Studios reviewing designs and sites with a long list of clients

Feedback widget: what the job actually is

A feedback widget is the visible half of a feedback tool: a button, usually in a corner, that opens a small form on top of your page. The person using your site marks what is wrong, types a sentence, and sends it. Nothing else is asked of them, which is the point.

The engineering questions behind that button are about isolation and weight. A widget renders inside somebody else's page, so it has to be immune to their CSS and unable to break their layout, which in practice means a Shadow DOM rather than injected markup. And it downloads on every page view, so its size is a cost paid by every visitor whether or not anybody files anything.

The product question is how much of the report it fills in on its own. This is where widgets diverge sharply. All of them capture a screenshot. Fewer capture the console and the failed network requests. Fewer still record the sequence of actions leading up to the report, which is usually the difference between a bug an engineer can reproduce and one they cannot.

What to check before you choose one

  1. 01

    How it is isolated from the host page

    A widget that injects plain markup inherits your stylesheet, and the first time a global rule changes it renders wrong on a customer's site. A widget in a Shadow DOM cannot be reached by the page's CSS and cannot reach out either. Ask which, because the failure mode only appears in production on somebody else's page.

  2. 02

    What it weighs

    The loader ships to every visitor on every page, so it is a permanent cost against your performance budget rather than a cost paid by the people who file reports. A few kilobytes gzipped is reasonable for a loader that fetches the rest on demand; anything in the hundreds means the widget is downloading its whole interface before anyone asks for it.

  3. 03

    How much of the report it fills in

    Every widget captures a screenshot. The ones worth paying for also capture the console output, the network requests that failed, the browser and viewport, and the actions before the report. Each of those is a question your team would otherwise have to ask, and each round trip costs a day when the reporter is a customer.

  4. 04

    Whether it can be made to look like your product

    A widget in somebody else's brand colours on your own site reads as a third-party bolt-on and gets fewer reports. Check whether theming is a colour picker or a full stylesheet, and whether the copy inside it can be rewritten, because the default wording is written for the vendor's market rather than yours.

  5. 05

    What it does to a visitor's privacy

    The widget runs on every page, so whatever it records, it records about people who never open it. Check that inputs are masked by default, that request and response bodies are not captured, and that authorisation headers and cookies are stripped before anything is stored. These should be defaults you cannot turn off by accident.

What each one is good at, and where it stops

Userback

A feedback platform with a four-step ladder, opening up AI insights, replay and mobile SDKs as a team moves up it.

Strength. A mobile SDK on Business Plus for native apps, integrations with Intercom and Zendesk so feedback lands where a support team already works, and MCP connectors from the Team plan for giving an AI assistant context on feedback.

Limitation. Session replay and the developer tools that capture console and network activity start at Business, $99 a month or $79 billed annually. On the free plan feedback disappears from view after 7 days.

Marker.io

A widget and browser extension aimed at agencies reporting bugs on client sites, priced by page views as well as by seat.

Strength. Reporters are free and unlimited, and sending feedback through the widget needs no account at all, so the people filing bugs never count against a seat.

Limitation. Session replay, console logs, network requests and the Jira integration all start at Team, which is $199 a month or $149 billed annually. Starter also caps page views at 5,000 a month.

Notarus

A widget, a fixed four-stage board, and an MCP server that exposes every action the panel can take.

Strength. Session replay, console, network and environment arrive on the free plan rather than on a paid tier, unlimited seats on every plan including that one, clients follow the work through a portal access that is not a member and never uses a seat, and every panel action is an MCP tool as a shipping rule, so an agent can work the board a person works.

Limitation. No mobile SDK at all, so a native app is out of scope, and no Intercom or Zendesk integration. What it takes feedback on is a live web page and nothing else: no Figma file, no PDF and no image.

BugHerd

A pin-on-the-page feedback tool for agencies and studios, sold by team members with clients thrown in free.

Strength. Unlimited guests and unlimited projects on every plan, and feedback works on Figma designs, PDFs and images rather than only on a live site.

Limitation. The project trackers most teams already run, Jira, Linear, Asana, ClickUp and Monday, are held back to the Premium plan at $150 a month. Extra members cost $8 each a month on top.

When Notarus is the wrong answer here

  • You want the widget to run surveys at scale with behavioural targeting and sentiment analysis over the answers. Ours asks questions and reports the aggregates; Usersnap is built for that job and we are not.
  • The widget has to live in a native iOS or Android app. Ours is a browser script and there is no SDK behind it.
  • You want a widget with no board behind it, feeding only an existing tracker. Notarus keeps its own configurable board, and if that duplicates a workflow you already run, the duplication is real.

Common questions

What is a feedback widget?

A script tag that puts a button on your site and opens a small form when somebody clicks it. The visitor marks what is wrong and types a sentence; the widget attaches the technical context and sends the report. The whole design goal is that the person reporting does not have to open a tracker or explain where they were.

Does a feedback widget slow down my site?

It costs whatever its loader weighs, on every page view, for every visitor. That is why the loader and the interface should be separate downloads, with the interface fetched only when somebody opens the widget. Ask for the gzipped size of the script in the tag rather than the size of the whole product.

Can a feedback widget break my page layout?

It can, if it injects ordinary markup into your document, because then your stylesheet applies to it and its stylesheet applies to you. Rendering inside a Shadow DOM prevents both directions. This is worth confirming before installing anything on a site you do not control.

What should a feedback widget capture automatically?

A screenshot with the annotation on it, the page URL, the browser, operating system and viewport, the console output, the network requests that failed, and the sequence of actions leading up to the report. Notarus includes these capture capabilities on Free. Screenshots are initiated by the reporter; automatic context depends on capture settings, browser support and available budgets.

Going deeper

How the widget is built and themed /features/widget Everything it attaches to a report /features/evidence-capture The recording behind the screenshot /features/session-replay

Start collecting website feedback with evidence.

Free includes evidence capture, session replay and the MCP server.

Start free See pricing
<script src="…/widget.js" data-key="pb_pub_…">