Website feedback built for bug reports and release testing
Developers get perfect context by default — capture screenshots and browser debugging details automatically.
Trusted by QA teams catching bugs faster
Every step of a QA cycle from bug sweep to engineering handoff
Pre-release testingSweep every breakpoint of a build at once
Load any URL at every breakpoint and pin bugs to the exact viewport that breaks. No resizing.
Bug repro contextAuto-capture the full context of every bug
Browser, OS, viewport, device, URL, and selector land on every bug. No template, no missing fields.
Triage and hand-offTriage bugs and hand them to the right dev
Move bugs across a kanban board, assign each to the dev who owns it, and ship the release.
Run QA on any kind of website staging builds, marketing sites and apps
Built for smooth collaboration with no hidden fees
Bugs ship to engineering with the full repro packet
Get URL, viewport, device, OS, and browser details automatically – stop bouncing tickets back for missing context.
Run responsive bug sweeps in one tab
On Pro and Team, load mobile, tablet, laptop, and desktop side-by-side on the same URL and spot responsive bugs in one pass.
Verify spacing, typography, and colors on the live site
Catch design drift and issues inline. Computed sizes, spacing, type, and colors are one click away.
Triage by status, priority, breakpoint, or assigned to team member
Set priority on every comment, tag them, and run multiple test cycles inside one workspace without losing track of open work.
Plus drawing tools, private comments, file reviews and a widget for web apps. View all features
Beyond a screenshot and a viewport with the full context on every bug
HuddlekitDon't just take it from us hear it from the professionals
“Huddlekit has become a real part of my process. … The whole UI is friendly and refreshingly uncomplicated. A straightforward, much-needed tool, especially for Webflow freelancers who want to add a touch of professionalism to their process.”
Magnaem Ambata
Webflow Developer
“I was previously using Pastel, but it only offers two breakpoints. Huddlekit has been a really solid upgrade for my workflow.”
Gul Ahmed
Webflow Developer
“Clients love dropping comments that instantly become actionable. Nothing falls through the cracks.”
Douglas Tamm
Digital Designer
“I love this tool! The UI is super intuitive and clean, and the best part is being able to see all the breakpoints side by side.”
Mikael Brunnberg
Product Designer
“After 20 years of designing websites, I can confidently say that Huddlekit is an exceptional product for the modern designer.”
David Lozano
Web Designer & Youtuber
“We tried Markup, Ruttl, and a handful of other tools. Huddlekit was the first one that actually organized our feedback and felt easy enough for clients to use without a walkthrough.”
George Duckett
Growth Lead
“Before, we spent a lot of time just figuring out what the client actually meant. Now they point at it and tell us. Much easier.”
Christian Jigling
Web Developer
“I'm not one to fill out testimonials, but Huddlekit has been the best experience for a markup tool that I have used. The tool itself has the best features compared to other markup tools, but what got me to leave a review was their tech support. …”
Matthew Haire
Web Project Manager
“Excellent tool, worked with a lot of other markup software and this is best in class.”
Felix Hellström
Web Developer
Cutting bug-back time and tightening QA cycles
“We tried Markup, Ruttl, and a handful of other tools. Huddlekit was the first one that actually organized our feedback…”
George Duckett
Growth Lead at Stormfors
“We stopped wasting time interpreting vague emails and just started fixing things.”
Christian Jigling
Web Developer at Leadfront
Loved by bespoke agencies. View case studies
Simple per-workspace pricing with stakeholders and guests always free
- 3 team members
- 1 project
- Unlimited guests
- 100 MB storage
- 3 team members
- Unlimited projects
- Unlimited guests
- 5 GB storage
- Connect Claude & Cursor (MCP)
- 15 team members
- Unlimited projects
- Unlimited guests
- 50 GB storage
- Connect Claude & Cursor (MCP)
- Integrations
- API access
Every limit and feature, plan by plan. Compare plans
Commonly asked questions and some more.
How is Huddlekit different from Marker.io or BugHerd for QA teams?
Both tools capture bugs on a single viewport. Huddlekit adds a multi-breakpoint canvas so QA can run responsive bug sweeps in one tab, plus an inline inspect mode for catching design-system drift without DevTools. Browser, OS, viewport, device, URL, and the element’s selector are auto-captured on every comment, so engineers never bounce a ticket back for missing repro context.
What context is captured automatically with each bug report?
Every comment includes the page URL, viewport size, device, operating system, browser and version, and the selector and classes of the element it is pinned to. A screenshot of the page state is attached automatically, and reviewers can add notes, file attachments, or replies. Engineers get a full repro packet without QA filling out a template.
Can I run multi-breakpoint QA checks in one view?
Yes. On Pro and Team, canvas view loads the same URL at mobile, tablet, laptop, and desktop side-by-side. Run a bug sweep across breakpoints, pin issues to the exact viewport where they appear, and see at a glance whether a bug is responsive or universal.
Does Huddlekit work on authenticated web apps and dashboards?
Yes. Use the Web App project type to drop a lightweight SDK snippet into staging or production behind a login. QA can run sessions on any authenticated page, including feature-flagged routes, and the widget stays out of the way of the test surface.
How do bugs flow to engineering, and is there a Jira or Linear integration?
Linear, yes: on the Team plan each comment becomes a Linear issue with the screenshot and page link attached, and status stays in sync. ClickUp, Notion, and Trello work the same way, and Asana keeps completion in sync. Jira has no native integration yet, but Zapier can send new comments into it. Pro and Team workspaces can also connect Claude, Claude Code, or Cursor over MCP, so an agent pulls open bugs with their full context and updates them as it goes.
Can QA filter open issues by status, breakpoint, component, or release?
Yes. Filter by status (open, in progress, in review, resolved), assignee, custom tag, or breakpoint. Use tags to mark releases or components and keep multiple test cycles separate inside one workspace. Archive issues on release to keep the active board lean.
Can multiple QA cycles or releases run inside one workspace?
Yes. Each project (typically one site or app) can host any number of release-tagged comment streams, and projects are unlimited on Pro and Team. Run QA for v2.4 alongside smoke tests for v2.5 without spinning up a separate workspace per cycle.
Have more questions? Visit our support center.