Compared with Jam, and the rest

Checked against each vendor's own published pages on 9, 12 and 17 September 2026; each source carries the date it was read. Rows run in order of install count, which puts Bugpacker last: it launched this month.

What Jam is

Jam is the product this category is currently about. A Chrome extension: you press record, reproduce the bug, and it produces a link holding the video, the console and network logs, the actions you took and the device details. Jam reports more than 250,000 users; the Chrome Web Store shows 200,000 installs.² It has a free tier that costs nothing, a SOC 2 Type II report, an iOS app and a customer support product. It is very good, and this page is more useful to you if it says so first.

It leads the table below because the feature list is its feature list. Every column comes from what reviewers say they use Jam for. None was picked because Bugpacker happens to have it.

What people actually praise about it

From public reviews on two independent sites, which agree with each other.¹ Roughly in order of how often it comes up:

1. Technical context attached automatically. Console and network logs on every report, with nobody gathering them by hand. Cited more than anything else, by a distance.
2. Instant Replay. A rolling two-minute buffer of the session that already happened, so a bug nobody set out to reproduce can still be sent. It buffers periodic HTML snapshots of the page and generates the video only when the user creates a Jam. It is off until the user turns it on in Settings, and Jam disables it automatically on sites with many animations or frequent high-volume re-renders, which the user can override per site.¹⁰ More than one reviewer calls it a game changer.
3. Issue tracker and Slack integrations. Jira, Linear, GitHub and Slack, named constantly.
4. Not having to explain. Send a link instead of writing three paragraphs.
5. It is pleasant to use. Repeated praise for the interface, and one reviewer says it makes QA fun.

And the others

Five more products appear in the table. Three of them are a different shape from Jam and from Bugpacker: a JavaScript snippet the site owner installs, so that clients and stakeholders can leave feedback on a live page. That is a different purchase made by a different person, which is worth knowing before reading their rows.

• BugHerd, around 80,000 Chrome Web Store users. A snippet plus an extension, aimed at agencies collecting feedback from clients on a site under review. Reviewers do not need to log in.
• Marker.io, around 30,000. The same shape, with unusually strong issue tracker integration and session replay.
• BrowserStack Bug Capture, around 30,000. Formerly Bird Eats Bug, acquired by BrowserStack in 2024 and now part of their test platform. The closest of these to Jam in what it captures.
• Usersnap, around 6,000. A feedback and QA widget, hosted in the EU.
• BugShot, 178 users. A side panel for QA: screenshots, recording, console, network and action logs, and AI drafts using your own API key, sent straight to Jira, GitHub, Linear and five more integrations, Slack among them. No BugShot account and no hosted storage. Of everything here, it is the closest to Bugpacker's position, and it is ahead of Bugpacker on features.

Also checked, not in the table

Chrome Web Store's related items on our own listing surfaced three more, read on 17 September 2026. For these we read only the store listing and the extension's manifest, not the vendor's own site, and every row in the table is held to reading the vendor's site. Each would need that before it gets a row.

• CrossCheck, 428 users. The same shape as Jam: sign-up, a hosted dashboard and share links, Jira and ClickUp, and an instant replay of the last one to five minutes.
• BugGenius, 114 users. Captures reports and exports them as Excel, JSON or HTML. Its listing says "All captured data is stored locally on your device", and that its Platform AI "routes requests through the AIdriventesting.ai backend". It names no issue tracker integration.
• webQsee, around 1,000 users. A network and console analyzer with session replay and share links. "Captures stay in your browser's IndexedDB until you choose to upload them", to its cloud storage or your own S3. A different kind of tool from a bug reporter.

All three, like BugShot, declare <all_urls> as a required host permission in their manifests.

Who does what

Rows ordered by Chrome Web Store install count, largest first.²

How to read it

• Y, the vendor's own pages say it has this. N, it does not.
• ? means it is not in that vendor's published feature pages. That says we did not find it, not that it is absent. Several of these are probably yes.
• Every product here captures browser, OS, screen size and page URL automatically, so there is no column for it.
• a BugHerd: "Clients can review websites & files without logging in." Whoever collects the feedback still has an account.
• b Not built. Roadmap item 1 would make it retroactive from the moment you open Bugpacker on a tab, as BugShot's is. A buffer that runs on pages you have not opened it on is not planned. The roadmap gives the reason.
• c On the Bugpacker roadmap, not built. Stated plainly below.
• d BugShot: the last 30 seconds, "optional, off by default", captured "whenever the side panel is open". Retroactive from opening the panel, not from before it.
• e BugShot: no BugShot account. Sending an issue needs an account on the tracker or Slack workspace you connect.
• f BugShot also sends anonymous usage events: install, side panel opened, platform connect and disconnect, and issue submitted. Its privacy policy says they carry "a random identifier (distinct_id) generated once on install", are "sent with the IP value set to 0.0.0.0", and "never include issue titles, bodies, URLs, or personally identifiable information". It also says: "There is no separate opt-out (off) setting for this analytics."

Which Jam plan each of those needs

The tiers matter more than the checkmarks, because the plan a solo developer actually uses is the free one. F is on the free plan, T arrives on Team at $14 per creator per month, E is Enterprise only.³

The three N's in that last row

Three of the five things reviewers praise most about Jam are things Bugpacker does not do today.

• No instant replay. The most praised feature after console logs. If you did not start recording, Bugpacker has nothing. It is the largest functional gap in the product. Closing most of it does not need a buffer that runs on every page you visit. BugShot, in the table above, shows that: its replay starts when you open its panel. The roadmap says what we intend and what it costs.
• No screen video. Every other product here records video. Bugpacker takes screenshots, and every other artifact it collects is text.
• No tracker or Slack integrations. You attach the file yourself. Every other product files the issue for you.

Tracker filing and video are next on our public roadmap, in that order, and that ordering was set before we read the reviews that produced this page's columns. Slack is not planned, and the roadmap says why.

Neither is shipped, so both read N here until they do. Instant replay reads N until roadmap item 1 ships, and even then it will reach back only to the moment you opened Bugpacker on the tab.

Where the capture goes

Five of the six products store captures on their own infrastructure. That is how most of the features above get delivered, and it is not a criticism of any of them. BugShot is the exception, and the difference between it and Bugpacker is narrower than the difference between either of them and the rest.

What separates the two that keep captures off a vendor's servers. BugShot requires access to all sites at install, and its privacy policy says Chrome shows that as "Read and change your data on all sites." That is what lets its capture continue when you navigate to another site, because Chrome's activeTab grant ends at a cross-origin navigation. Bugpacker declares no host_permissions, so its install prompt has no such line. The cost is that a Bugpacker recording that crosses to another site loses capture after the crossing, and the package says so. BugShot also makes the analytics requests in footnote f. Bugpacker makes no outbound requests.

So the trade is not storage against features. BugShot has replay, video and filing without hosted storage. What Bugpacker gives those up for is no all-sites permission at install and no outbound requests. For most teams that is not worth it. For a team whose security review stops at "read and change your data on all sites", it is the only row that matters.

What this page does not claim

• Not that Bugpacker has more features. It has fewer than every product listed.
• Not that these vendors mishandle data. Nothing here suggests it and we have no evidence of it. Jam holds a SOC 2 Type II report. Bugpacker holds no such report and no certification.
• Nothing about Jam's redaction. Their security page says automatic blurring is on all plans; their pricing matrix marks video blurring off on Free and auto-blur as Enterprise only. Those do not obviously agree, so this page makes no claim about it. Ask Jam.
• Nothing against BugShot's analytics. They are disclosed, they carry no capture data, and they are stated here because they are the concrete difference between its claim and ours, which you can check against its privacy policy.
• Not that Bugpacker is air-gapped. It runs in a browser on a networked machine. The claim is narrower and checkable: it declares no host_permissions, so Chrome will not let it reach any host. See the security page.

If a cell here is wrong

Tell us and it is fixed or removed the same day: hello@bugpacker.com. That goes for the vendors named here more than for anyone else.

Sources, read 9 September 2026 except where noted

1. Public reviews on G2 and Product Hunt.
2. Chrome Web Store install counts, which Google buckets and rounds: Jam 200,000, BugHerd 80,000, Marker.io 30,000, BrowserStack Bug Capture 30,000, Usersnap 6,000. BugShot 178, read 17 September 2026, which is small enough that Google reports it exactly.
3. jam.dev/pricing, feature matrix read in a browser.
4. jam.dev/docs/security.
5. marker.io/security and marker.io/features.
6. usersnap.com/security and usersnap.com/features.
7. bugherd.com/security and bugherd.com/features.
8. BrowserStack Bug Capture's Chrome Web Store listing, privacy practices section, and browserstack.com/bug-capture. The data categories are the developer's own declaration.
9. Checkable rather than asserted: the security page and the PDF packet.
10. Jam's own Instant Replay documentation, read 12 September 2026: jam.dev/docs/instant-replay, the performance page and the privacy page.
11. BugShot's Chrome Web Store listing, bug-shot.com/privacy (effective 9 September 2026), and the manifest of version 1.7.40 read out of the published package. All read 17 September 2026.