Pick the channel 
No more “send me a screenshot”
Annotated screenshots arrive inline in the Slack message, so your team sees exactly what the user saw.
Get visual feedback in Slack, instantly
Pings to your channel the second someone hits the Feedback button — annotated screenshot, browser, OS, and a console summary right in the message. No tab-switching to find what broke.
Start free trialNo credit card required
Ybug widget
Feedback submitted
Slack
Posted to channel · with screenshot
Trusted by 1,000+ teams worldwide
How feedback gets into Slack
Point-and-click capture
Users point at the bug — your channel gets pinged
A user clicks the Feedback button, draws on the page where the bug is, and types a sentence. Seconds later your Slack channel gets a message with the annotated screenshot inline, the URL, and a one-click link to the full report in Ybug.
- In-page widget — no logins, no plugins for the reporter
- Reporter annotates with arrows, rectangles, or free draw
- Works on staging, production, and password-protected sites
Everything in the message
Every alert lands with the screenshot inline
Each Slack post includes the reporter’s name and comment, the annotated screenshot, the page URL, browser, OS, screen size, and a one-line console summary. No clicking around to figure out what your tester actually saw.
- Annotated screenshot embedded right in the Slack message
- Reporter, URL, browser, OS, screen, and viewport on every alert
- Screen recordings linked from the message when the user records one
Pick the channel
Send each project to its own channel
Connect different Ybug projects to different Slack channels — keep client work in #client-acme, your own product in #bugs-internal, urgent QA in #release-blockers. Custom fields you collect in the widget land in the message too, so the right person can pick it up at a glance.
- One Slack channel per Ybug project — public, private, or DM
- Custom fields included in every alert by default
- Auto-push every report, or post manually from Ybug after triage
Console logs at a glance
JavaScript errors show up on the same line
Ybug captures the browser console automatically and includes a one-line summary right in the Slack alert — counts of errors, warnings, and logs, ready for triage. The full console log lives in the Ybug report, one click from the message title.
- Auto-capture uncaught JavaScript errors
- Error and warning counts in the Slack message
- Full console log a click away in the linked Ybug report
Set it up in under 5 minutes
No webhook scripting. No bot to maintain. Connect Slack, pick a channel, and let Ybug ping you the moment someone reports a bug.
1.
Connect Slack
Authorize the Ybug Slack app to post into your workspace.
2.
Pick the channel
Each Ybug project posts to one Slack channel — #bugs, #qa, #client-acme, whatever fits.
3.
Choose the handoff
Send every report automatically, or keep auto-forwarding off and post selected reports from Ybug manually.
4.
Start collecting
Add the widget to your site and watch annotated bug reports land in Slack.
“Ybug makes collecting feedback and bugs extremely smooth, even for non-technical users. Annotated screenshots, automatic environment information (browser, console, URL, screen size), and integrations with our project management tools save considerable time during testing and support phases.”
Gianito R.
Consultant et développeur web
Why teams use
Ybug with Slack
Slack is where your team already lives. Ybug makes sure the bug reports landing there have everything you need — not just a sentence saying “it’s broken”.
Context in every alert
Every Slack post includes the URL, browser, OS, viewport, and a console summary — no chasing details on Tuesday morning.
JS errors spotted from the channel
Slack alerts include counts of console errors and warnings, so devs can flag a JavaScript bug before they even open the report.
Click through to fix
Every alert title links straight to the report in Ybug, where you can reply to the reporter and forward to Jira, ClickUp, or Trello.
Need a task tracker too?
Pair Slack with the rest of your stack
Frequently asked questions
Can I send reports to multiple Slack channels?
Each Ybug project posts to one Slack channel. If you manage several products or clients, create a separate Ybug project for each and connect it to the right channel.
What does Ybug include in the Slack message?
The message shows the reporter, comment, annotated screenshot, page URL, browser, OS, screen size, viewport, and a one-line console log summary. Custom fields are included by default, and screen recordings link from the message when the user records one.
Does it work with private channels?
Yes. Pick any channel — public or private — when authorizing the Ybug Slack app.
Can I disable Slack alerts for some reports?
Yes. Keep auto-forwarding off and post selected reports from Ybug manually, or split widgets across separate Ybug projects so only certain ones ping the channel.
Are screen recordings included?
Yes. If a report has a screen recording, the Slack message includes a direct link to play it.
Do Slack reactions or threaded replies sync back to Ybug?
Not right now. Ybug posts to Slack and the alert title links back to the report, but reactions and threaded replies don’t sync into Ybug.
Can our users submit feedback without logging in?
Yes. Users can submit visual feedback and bug reports directly from your app in a few clicks – no signup or login required. Less friction means more useful feedback.
Stop chasing screenshots in DMs
Get feedback with the annotated screenshot, browser context, and console summary as Slack messages — automatically.
Start free trialNo credit card required