Capture for Jira is for the testers you license.
Snag is for the users you do not.

Capture for Jira is SmartBear's exploratory-testing tool for teams working inside Jira. Capture for Jira records screenshots and screen video in the browser, annotates them with audio and visual tools, and runs shared testing sessions anyone on the team can join. SmartBear describes Capture for Jira on their product page in the present tense, so this is a straight comparison and not a migration guide. What separates the two is the model rather than the feature list. The Capture for Jira licence follows your Jira user count; Snag charges a flat workspace fee, takes reports from end users who have no licence at all, and finishes the job by opening a pull request.

Where they are genuinely good

Shared testing sessions are the clearest thing Snag has no answer to: Capture for Jira lets everyone create and join exploratory testing sessions, which is a way of working rather than a feature, and nothing in Snag resembles it. The Capture for Jira annotation tools go further than ours too, into audio as well as visual, where a Snag capture rides an annotated screenshot. And Capture for Jira records screen video from inside the browser, which Snag does not do at all: a Snag replay is a reconstruction of the page rather than a film of it. For a QA team that lives in Jira and tests deliberately rather than waiting for reports, Capture for Jira is doing a job Snag does not attempt.

Where Snag is different

Snag is built around one question: can this bug be fixed, and can we prove it? That starts with who is allowed to report. Anyone on your site can file, with no account and no licence, and the workspace fee never counts them. One click records a session replay with the console and the network beside it, and files a work item in Jira or an issue in GitHub linking back to all of it. Personal data is masked in the browser before anything uploads — inputs are never recorded. Then a sandboxed fix run reproduces the bug in a disposable copy of your repo, writes a repro test that fails before the fix and passes after, and opens a pull request for a person to review. Nothing merges without a human, and the sandbox is destroyed when the run ends. A run that produces no pull request costs half, and the first 5 fixes are free on every plan.

Which one to pick

Pick Capture for Jira when the people finding bugs are testers who already hold Jira licences, when exploratory sessions are how your team works, and when the record you want is a narrated video of somebody trying the product. Pick Snag when the people finding bugs are your users, when the next reader of the ticket is a coding agent, and when the thing you want back is a pull request with a test that proves the bug is gone. Plenty of teams have room for both, and nothing here needs to be chosen against the other.

Snag and Capture for Jira, side by side

Every Capture for Jira cell links to the page we read it on.

Questions people actually ask

Is Capture for Jira still around?

Yes, and it changed hands rather than closing. It started life as Atlassian's Bonfire; the dated Atlassian notice that turns up in search is about ownership, not about the product ending — it reads "As of November 13, 2017 ownership of the Capture for JIRA App transferred from Atlassian to Zephyr". Zephyr is part of SmartBear, and the SmartBear product page describes what it does in the present tense: screenshots and screen video recorded in the browser, audio and visual annotation, shared exploratory testing sessions. If somebody told you it was discontinued, they were probably remembering that transfer stub, or the end of Jira Server support in February 2024.

Who is each one for?

They point at different people, which is why this reads as a comparison rather than a replacement. Capture for Jira is aimed at testers working inside Jira: everyone can create and join shared exploratory testing sessions, screens are recorded and annotated with audio and visual tools, and the work lands in the project they are already licensed for. Snag is aimed at the end user who hit the bug and at the coding agent that has to fix it — the person filing needs no licence and no account, and what arrives is a replay with the console and the network beside it, then a pull request.

How does the licensing compare?

This is the sharpest structural difference. Add-ons for Jira are licensed at the maximum user count across all Jira Software, Jira Service Management and Jira Work Management instances on a single site, so the price follows how big your Jira is rather than how many people are testing, and an active Jira site is a prerequisite. A Snag workspace pays one flat fee that never counts members, filing a bug needs neither an account nor a licence, and fix plans add a monthly pool of fix-runs on top. The live figures are in the pricing section of the homepage.

How does a Snag fix run end?

It ends at a pull request, or it ends early and is charged at half. The finished shape is the diff, a repro test that fails on the code the ticket was filed against and passes on the code with the fix in it, and the capture the agent reasoned from. Everything before that happens in a disposable copy of your repo, destroyed when the run ends. None of the ending is automatic: Nothing merges without a human. The first 5 fixes on every plan are free.

Where these details come from

Every Capture for Jira detail on this page links to the Capture for Jira page we read it on, with the date we read it. Something out of date? Email admin@dvcllc.io and we will fix it.