Frequently asked questions

A Chrome extension and a website for reporting bugs. You capture a screenshot or a video of the page that is misbehaving, the extension collects the technical context around it - browser, screen size, console errors - and you get a link to send to whoever can fix it.

No. Anonymous reports work and are not second-class: the report and the share link are identical either way. Without an account you can upload 5 reports a day; signing in removes that limit and keeps a history of everything you have reported.

Not for a public report - the link opens for anyone who has it, with no sign-in. A private report is the exception: it opens only for you and for the team that owns the domain it was filed on.

From the Chrome Web Store. It works in Chrome and other Chromium browsers, and you open it from the side panel.

The screenshot or recording, the page address and title, your browser and version, operating system, screen and window size, and the console output from the page - errors and warnings included, with stack traces.

No. Nothing is captured until you press a button, and the extension records only the tab or the screen area you choose in Chrome's own picker.

During a recording, yes: every request the page made while you were recording, with its address, method, status and timing. The report page shows them, and offers the lot as a HAR file you can open in DevTools. Response bodies are the exception - they are off unless you turn them on for that recording, because a response body is the likeliest place for something private to be sitting.

Yes. Annotate it before uploading, and the drawing is baked into what the recipient sees.

Whatever is visible in what you capture is in the report. Treat a report the way you would treat a screenshot you are about to email - because that is what it is.

Usually anyone with the link. The share URL carries a long random token and needs no password, which is what makes it easy to send - and means you should treat it as public. A report filed on a domain somebody has claimed here can be private instead, in which case it opens only for you and for the team that owns the domain. Share pages are marked so search engines do not index them either way.

30 days by default, after which the link expires. A site on Starter keeps the same 30 days; Professional keeps 90.

Yes, signed-in users can delete their own reports, which removes the recording with them. For an anonymous report, send us the share link and we will remove it - there is nothing linking it to you, so we cannot find it any other way.

On dedicated servers in the EU. See the privacy policy for the full detail of what is collected and who else sees it.

Reporting bugs is free, with no cap once you have signed in. Receiving reports for your own site is paid: Starter is $19 a month for one domain, Professional $79 for five, and a year costs ten months rather than twelve.

Yes. Claim the domain on a paid plan, prove it with the meta tag we give you, and every report filed on it arrives in your dashboard instead of living only on a share link. You decide whether that covers the domain alone, its subdomains too or a list of hosts you name, and who on your team works through what arrives.

Every paid plan starts with 14 days, and those days cost $5 - charged on the day you start, with the plan's own price following when they run out. A card that will not take five dollars will not take nineteen a month later, which is most of the point of charging for a trial at all. The free plan needs no card.

Press Report a bug at the foot of this page. It captures the page, the console and the network log and sends the lot to us, which is more than any description carries - and it is the same route on any other website, ours or not. If the page is too broken for the button to appear, email support@session-replay.com. The contact form is for anything that is not a bug.

Not beyond these answers and the how-it-works page yet. The step most worth writing down - putting the meta tag on your site and checking it took - is the one we are writing first.