[ Compare ]
Website feedback tools compared
BugHerd, Marker.io, Userback, Usersnap and Feedbucket collect feedback for people to work through. feedback2code hands it to a coding agent. This page puts them side by side, with prices taken from each vendor's own pricing page.
Updated
At a glance
| Tool | How feedback is given | What you end up with | Free plan | Paid from |
|---|---|---|---|---|
| feedback2code | A widget on the live site. The visitor describes the change in plain text. | A GitHub pull request with the change implemented, ready for review. | Yes: 10 feedback submissions per 30 days, unlimited repositories, pull requests included. | $20 per month for 100 feedback submissions per 30 days |
| BugHerd | Point and click on the page. Feedback also works on Figma files, PDFs and images, with screenshots, video and text edit suggestions. | A task on a board that someone on the team picks up and fixes. | No free plan. Free trial and a 60-day money-back guarantee. | $50 per month for 5 members ($42 when billed yearly) |
| Marker.io | A widget on the site: screenshot, annotations, and technical context collected automatically. Higher plans add session replay. | An issue in the tracker you already use, such as Jira, GitHub, GitLab, Linear, Trello or Asana. | No free plan. 15-day free trial without a credit card. | $59 per month for 3 users and 10 projects ($39 when billed yearly) |
| Userback | A feedback widget with screenshots and annotations. Business plans add session replays, user surveys and targeting. | Feedback items in Userback, pushed to project management tools through integrations. The Team plan lists MCP connectors for AI tools. | Yes: 2 seats and 2 projects, with feedback kept available for 7 days. | $39 per month for 5 seats and 5 projects ($29 when billed yearly) |
| Usersnap | Feedback widgets and other channel sources, with segments and email automations on higher plans. | An opportunity board and analytics for product managers, plus integrations into other tools. | No free plan. The trial ends after the first 20 feedback items. | €49 per month for 2 seats and 2 projects |
| Feedbucket | Screenshot and video feedback on the live site, with unlimited client reporters. | Feedback in Feedbucket and in the connected project management tool. Both plans list an MCP connector. | No free plan. 14-day free trial without a credit card. | $49 per month for 2 team members ($39 when billed yearly) |
Prices and plan details were read from each vendor's public pricing page on 1 October 2026. They are monthly prices, with the yearly rate in brackets where the vendor shows one. Plans change, so check the vendor's page before you decide.
Two kinds of tools
The five established tools solve a reporting problem. A client or tester sees something wrong, and the tool makes sure a developer gets a precise report: a screenshot, an annotation, the browser, sometimes a session replay. Someone on the team then does the work.
feedback2code solves the step after that. The report is a sentence of text, and an AI coding agent turns it into a change in your repository. You get a pull request to review. That makes it useful for requests that are easy to describe and tedious to do, and less useful for anything that needs a picture to explain.
Which one fits
- BugHerd: Your clients need to point at things: a misaligned image, a wrong colour, a typo in a specific place. feedback2code vs BugHerd
- Marker.io: Your team lives in Jira, Linear or another tracker and every report has to end up there. feedback2code vs Marker.io
- Userback: You run a product and want feedback, surveys and session replays in one place. feedback2code vs Userback
- Usersnap: You are a product team that wants to find patterns across hundreds of feedback items. feedback2code vs Usersnap
- Feedbucket: Clients should record a video or mark up a screenshot instead of writing. feedback2code vs Feedbucket
- feedback2code: Your code is on GitHub, the requests are small and concrete, and you would rather review a pull request than work through a list of tickets. How the widget works
What feedback2code does not do
- Feedback is text. There are no screenshots, annotations or video.
- The site's code has to be in a GitHub repository.
- There is no task board. Each submission has a status: coding, awaiting review, merged or failed.
- Nothing is merged automatically. Every change waits for your review.
Questions and answers
Which website feedback tools have a free plan?
On 1 October 2026, two of the tools on this page listed a free plan: Userback (2 seats and 2 projects, feedback kept available for 7 days) and feedback2code (10 feedback submissions per 30 days). BugHerd, Marker.io, Usersnap and Feedbucket offered free trials instead.
How is feedback2code different from a visual feedback tool?
Visual feedback tools capture a screenshot with annotations and create a task or an issue for a person. feedback2code takes written feedback and has an AI coding agent implement it as a GitHub pull request. It has no screenshots and no task board.
Can I use feedback2code together with another feedback tool?
Yes. A common split is a visual tool for design and QA rounds, where pointing at things matters, and feedback2code for the small change requests that arrive after launch.
Is feedback2code open source?
No. Its source code is public on GitHub so you can read how it works, but the licence is proprietary and there is no self-hosted version.