Almost every round-up of bug reporting tools ranks them on features, then names a best bug reporting tool at the end. That hides the one distinction that actually eliminates candidates: most of these products are browser extensions or JavaScript snippets built for websites, and they cannot touch a native mobile or TV app at all.

It also blurs a second distinction. A bug management tool captures and organises what testers find; bug tracking systems such as Jira store and schedule the work afterwards. Almost everything below is the former and hands off to the latter.

If your product is a website, you have a wide field and the differences are about capture depth, seat pricing and which tracker they feed. If your product includes an iOS or Android build, the field narrows sharply before you compare a single feature.

The question that halves the list

Ask what has to be installed, and where.

Browser extension

Each reporter installs it themselves. Works on any site they visit; cannot see inside a native app.

JavaScript snippet

You add it to your site once and every visitor can report. Still web-only.

Native SDK

Compiled into your app binary. The only way to capture from inside a mobile or TV app.

BugHerd states in its own support material that it is designed to work on websites and web applications. Jam’s browser extension is officially supported on Chrome, Edge, Arc, Brave and Opera — its documentation notes Firefox and Safari are not supported. Marker.io’s extensions are documented for Chrome, Edge and Firefox and described as desktop-only, meaning they are not available on mobile browsers. Usersnap’s extensions are documented for Chrome and Firefox only.

That is four of the six tools below constrained to the web before you evaluate anything else.

The tools

BugHerd

A visual feedback tool: a sidebar overlay on the target site lets reviewers pin feedback directly to the page, and every item lands on a Kanban-style task board inside a project.

The plan gating is unusually consequential here, and worth reading before you price it. BugHerd documents that users on Standard and Studio plans must have the browser extension installed in order to capture screenshots, while Premium and above can use a JavaScript snippet instead. Jira integration also requires Premium or above. And its extensions explicitly cannot capture and pass custom data with bug reports. Its published Standard plan includes 5 members.

Strongest for agencies collecting client feedback on websites. Ruled out entirely if you ship a native app.

Marker.io

Installed as a JavaScript snippet before the closing head tag, with CMS plugins for WordPress, Webflow, Shopify, Squarespace, Bubble, Craft, Ghost and HubSpot, plus an npm package and browser SDK for modern JavaScript applications. Reporters click a widget button, which captures a screenshot, annotates it, and sends the issue with technical metadata attached.

Two documented constraints worth knowing. Sites behind Basic Auth may capture screenshots with missing images or styles, because Marker.io’s servers cannot reach the assets — the workaround is entering the site credentials in the widget’s screen capture settings. And to use the browser extensions collaboratively, reporters must have a Marker.io account, be added to the project, and install the extension themselves.

Usersnap

Installed as a snippet before the closing body tag, or via an official WordPress plugin. Widgets appear as a button or pop-up and capture annotated screenshots and screen recordings, with optional audio, from inside a web application.

One documented quirk that catches teams: Usersnap cannot automatically detect whether users are logged into your application, so developers must set the user identifier and email explicitly in the initialisation code. Its documented free plan gives you the first 20 feedback items with no time limit but a fixed quantity, and one documented plan caps live widgets and dashboard collaborators at five each.

Jam.dev

A browser extension aimed at support, product and engineering teams. Clicking it records the screen or takes a screenshot, and Jam automatically captures console logs, network errors, user actions and device information, with fully inspectable network requests included. Instant Replay is toggled on in settings and triggered from the extension or a keyboard shortcut.

The constraints are all about reach and duration. Chromium browsers only. WebSockets are not supported in Brave. Its pricing documents per-recording duration limits of 5 minutes on at least one plan and 15 minutes on another, and a cap of 5 recording links on at least one tier. A 2026 BetterBugs comparison claims free users are limited to 30 report sessions a month, and a G2 review reports the extension sometimes fails to launch until the browser is restarted.

Gleap

One of only two here with real native coverage. Gleap documents SDKs for iOS, Android, React Native, Flutter, Ionic or Capacitor, JavaScript and WordPress, initialised with a project key, and its JavaScript replays feature records and replays user interactions on the web specifically to help understand bug reports. There is also an unusual install path: running an agent-skills package and instructing a compatible AI coding agent to add Gleap to the project.

Worth noting for planning: automatic page tracking is not available for React Native applications due to platform limitations, so pages must be tracked manually. Gleap GmbH acts as data controller under GDPR and its terms are governed by Austrian law, which some European buyers will read as an advantage and some procurement teams will need to review.

Instabug, now Luciq

The most significant change in this category in the last year, and one that most comparison pages have not caught up with. Instabug announced its transformation to Luciq.ai and now markets agentic mobile observability for native apps on iOS, Android, Flutter and React Native, with infrastructure it says supports over two billion devices.

The commercial change matters more than the rebrand. Luciq’s Enterprise plan documentation states that self-serve pricing plans are no longer available for new sign-ups, that downgrades or switching between self-serve plans are not supported, and that existing self-serve customers can only upgrade to an Enterprise plan. If you were planning to sign up with a card this quarter, that route is closed.

On integration, its iOS guide recommends Swift Package Manager for new and existing work and notes CocoaPods is deprecated, to be used only by existing projects.

What the free tiers actually give you

  1. Read the cap, not the word. Usersnap's documented free allowance is the first 20 feedback items — no time limit, a fixed quantity. A BetterBugs comparison puts Jam's free limit at 30 report sessions a month.
  2. Check what the plan gates, not just the volume. BugHerd's Jira integration needs Premium or above, and snippet-based screenshot capture needs Premium too — so a cheaper plan changes how the tool installs, not only how much you get.
  3. Count seats separately from reporters. Several tools here distinguish paid members from unlimited external reporters, and the free tier usually caps the first.
  4. Confirm self-serve still exists. Luciq's documentation now says self-serve plans are closed to new sign-ups, which is the kind of thing a comparison table written last year will not tell you.

Searching for a bug reporting tool free of charge is reasonable for evaluation and misleading as a selection criterion — every tier here converts to paid at a threshold you should find before you standardise on it.

The extension tax

If you pick an extension-based tool, price the human cost as well as the licence.

Every reporter installs software themselves. Marker.io’s extension users must additionally have an account and project access. BugHerd’s Standard and Studio users cannot capture a screenshot without the extension present. For a small internal team that is a one-off annoyance. For a bug bash with twenty cross-functional colleagues, or for feedback from customers, it is a conversion funnel — and the people least likely to complete it are the non-technical testers who often find the most valuable bugs.

Snippet-based installs avoid this on the web. Native SDKs avoid it inside an app. Extensions do not.

Where TraceItX fits

TraceItX is in the native-SDK column. The reporter is compiled into your app, so a person presses a bubble or a keyboard shortcut, annotates the screenshot, blurs anything sensitive, and sends — with no extension, no account and no second tool. It covers iOS, iPadOS, tvOS, Android, Android TV, Fire TV and React Native, plus React on the web, and every platform returns one identical AI-ready envelope: annotated screenshot, console and network state, device and app context, and the trail of screens and actions leading to the report. Receiver code is written once rather than per platform.

Two things it does differently on price and delivery. Seats and reports are unlimited on every tier including the free one, because the meter is monthly active installs rather than people — so the extension tax and the seat tax both disappear. And delivery is a signed webhook rather than a proprietary inbox, using HMAC-SHA256 over the timestamp and raw body, the same scheme Stripe uses, with retries, a dead-letter queue and a per-subscriber circuit breaker behind it.

Where it loses, plainly. There is no Jira, Linear, GitHub Issues or Slack app — you write the receiver, and every other tool on this page ships integrations you configure in a settings screen. On the web it supports React only, with no framework-agnostic build, so a WordPress site or a Vue dashboard cannot use it where Marker.io and Usersnap can. Roku, Tizen and webOS need a conversation rather than a package install. There is no self-hosting option. And it is not a bug tracking system — it captures and delivers, and something else stores.

If your product is a website and you want bugs in Jira by Friday, one of the tools above is the better buy, and the honest recommendation is to take it.

How to choose

  1. Native app in scope? If yes, you are choosing between Gleap, Luciq and TraceItX before anything else matters.
  2. Who reports? Internal team only — an extension is tolerable. Customers or a large cross-functional group — insist on snippet or SDK.
  3. Which tracker, and on which plan? Confirm the integration exists at the tier you intend to buy, not just somewhere on the pricing page.
  4. What breaks capture? Basic Auth, cross-domain iframes, unsupported browsers and recording length limits are all documented constraints above, and all of them are cheaper to discover now.
  5. Then compare features. This is where most bug report software comparisons start, and it is the least decisive step.

If you are shortlisting for a native app and unlimited reporters, the free tier needs no card — 1,000 monthly active installs, unlimited seats and reports, with 14-day artifact retention as the constraint to plan around.