About Session Replay
Session Replay exists because of one exchange that everybody who has ever shipped software has had: "it's broken", followed by "can you send me more details?", followed by silence.
The problem
The person who found the bug is rarely the person who can fix it, and the information the fixer needs is exactly the information the finder does not know how to give: which browser, which screen size, what the console said, what was on screen at the moment it went wrong. Asking for it takes a day. Getting a useful answer takes another.
What we built
A Chrome extension that captures the bug and everything around it in one click - a screenshot or a video of the tab, plus the browser, the screen size and the console output - and turns it into a link you can paste anywhere. The person receiving it opens the link and sees what you saw. No account needed to send one, and no account needed to read one.
What we believe
- Reporting a bug should take seconds, not minutes. If it is any harder than that, people stop doing it, and you stop hearing about your own defects.
- The reporter should not have to sign up. Friction at that moment loses the report, and the report is the whole point.
- Say what the product does, not what it might do. We would rather have a short honest feature list than a long aspirational one.
Where we are
Session Replay is early. The recorder and the player work, share links work, and a signed-in account keeps a history of what you have reported. Features for site owners - claiming your domain, receiving reports for it, working on them as a team - are still being built, and pages across this site mark them as such rather than pretending otherwise.
Questions, bug reports about our own bug reporter, or ideas: get in touch.