PostHog / PostHog/posthog

Feature Request: Annotated Screenshot Bug Reporting Widget

Open
#47,543 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
6h 51m
Merged PRs (30d)
232

Description

Feature request

Is your feature request related to a problem?

Currently, PostHog has surveys and session replay features, but there's no built-in widget that allows users to capture, annotate, and submit screenshots directly when reporting bugs - similar to what Hotjar offers with their feedback widget.

Users need a frictionless way to report issues with visual context. Right now, they would need to:

  1. Take a screenshot separately
  2. Annotate it in another tool
  3. Submit feedback through a survey or external channel

This creates unnecessary friction and reduces the quality/quantity of bug reports.

Describe the solution you'd like

A side-tab widget (similar to PostHog's survey widget) that allows users to:

  • Click a "Report Bug" button
  • Automatically capture a screenshot of the current page/view
  • Annotate the screenshot with arrows, highlights, text boxes, or drawings
  • Add a text description of the issue
  • Submit the annotated screenshot + description as an event to PostHog
  • Link the report to the user's session replay for additional context

Describe alternatives you've considered

  • Using PostHog surveys with custom implementation for screenshot capture (requires significant custom development)
  • Third-party tools like Marker.io or Userback (adds another vendor and doesn't integrate with PostHog's session replay)
  • Manual bug reporting through support channels (loses context and session data)

Additional context

This would complement PostHog's existing session replay and surveys features, making it easier for product teams to collect high-quality bug reports with visual context directly tied to user sessions.

Debug info
- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by locating the existing survey widget and session replay integration, then trace how submitted survey data becomes a PostHog event. Done means users can capture and annotate the current view, add a description, submit the report, and link it to the session replay.

Written by the indexing model from the issue text.

Assessment

Domain
analytics, frontend, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.