Bug reports that explain themselves
Capture a screenshot or recording in Chrome, and Screencrab.me attaches the console errors and network requests behind it, then files an issue for every finding where your developers already work.
No card needed. From $12 a month for your whole team, viewers free.
- GitHub
- GitLab
- Jira Cloud
- Linear
- Shortcut
- Slack
From “it’s broken” to fixed, in three steps
- 1
Capture
Take a screenshot or record the tab, a window, your screen or just an area of it, with your voice if it helps. The toolbar sits on the page you’re testing.
- 2
Explain
Point at the problem with arrows, boxes and numbered steps, blur anything private, and write it up. The console and network logs come along on their own.
- 3
Share
Publish the report to the project. Everyone on it gets an email, each finding becomes an issue in your tracker, and the pull request gets a comment.
Every integration, on every plan
Lands where your developers already work
Connect a service once. When a report is published, each finding becomes an issue, the pull request it tested gets a comment listing them, and your channel hears about it. The screenshots and logs stay in Screencrab.me, behind its own sign-in, and every issue links back.
GitHub
An issue for each finding, labelled by severity, and a comment on the pull request.
GitLab
The same for merge requests, on GitLab.com or your own instance.
Jira Cloud
An issue in the project and issue type you choose, with its priority set.
Linear
An issue for the team you choose, made by the app, with its priority.
Shortcut
A bug story for the team you choose, labelled by severity.
Slack
One message per report in the channel you pick, linking every issue.
screencrab-mebotcommented just nowCheckout pass, Tuesday
Devon Tester found 3 issues testing this change with Screencrab.me.
| Finding | Severity | Issue | |
|---|---|---|---|
| 1 | Place order does nothing | Critical | acme/shop#142 |
| 2 | Total is off by a cent with tax | High | acme/shop#143 |
| 3 | Coupon field ignores lowercase codes | Medium | acme/shop#144 |
No more “can you reproduce it?”
The error and the failed request, right under the screenshot
Screencrab.me keeps the last minutes of console and network activity in your browser, so a screenshot shows what led up to it, and a recording keeps it all the way through. Every plan has it, where Marker.io and Userback keep it for their dearer plans.
See how they compare →
More for your team, for a lot less
What five people pay a month once console and network logs are included, from each tool’s own pricing page.
Screencrab.me$30 a month
Team, billed monthlyJam$70 a month
Team, billed yearly onlyUserback$119 a month
Business, where its logs startMarker.io$199 a month
Team, where its logs start
Jam also has a free plan with logs, for up to 30 bugs a month. BugHerd’s pages don’t list console or network logs. Every comparison →
Everything a developer asks for, captured the first time
Console and network logs, on every plan
Errors, warnings and every request with its status and timing, from the minutes before the screenshot or during the recording.
Record the tab, a window or the screen
Or an area of any of them, with narration from your microphone: up to 10, 30 or 60 minutes, by plan.
Annotation built in
Arrows, boxes, ellipses, freehand, text, numbered steps, crop and a blur box for anything that shouldn’t be kept.
Secrets stay out
Passwords, tokens, cookies and authorization headers are removed in the page, before anything leaves it.
Reports per project
Drafts while you test, then one published report with every finding, and a page to read it on.
Viewers are free
Developers, managers and clients can read reports and get the emails for free, however many you invite.
Private by default
Screenshots and recordings are stored in the EU, reached only through links that expire in minutes, and never copied into your tracker.
An activity log
Owners and admins see who joined, changed roles, published or deleted, and what was cleaned up.
Questions
- What can the extension see?
- Only the sites you give it access to, and only what you choose to capture there. It keeps the last 10 minutes of console and network activity in your browser so a screenshot can show what led up to it; nothing leaves your computer until you save a finding.
- Who counts towards our plan?
- Everyone who captures: owners, admins and members. Each plan includes some, and Team and Business take more for $5 a month each. Viewers read reports and get the emails for free, however many you invite.
- What happens when the trial ends?
- Your 14-day trial needs no card. When it ends, capturing pauses and reports stay readable until you choose a plan. Screenshots and recordings are deleted 30 days later if you don’t, after a warning email.
- Does it work with our issue tracker?
- On every plan, publishing a report makes an issue for each finding in GitHub, GitLab (self-managed too), Jira Cloud, Linear or Shortcut, comments on the pull or merge request it tested, and posts a summary to a Slack channel. Each issue links back to the screenshots, recording and logs, which stay in Screencrab.me.
- Which browsers does it work in?
- The extension is for Google Chrome on desktop, from the Chrome Web Store. Reports open in any modern browser.
- Can I cancel any time?
- Yes. Your plan carries on until the end of the period you paid for, and any payment can be refunded within 14 days.
Your next bug report could be the last one anyone has to ask about
14 days free, no card. Then from $12 a month for your team.