It watches. It explains. · Chrome extension
The AI screen recorder
that explains what happened.
Record a tab. Get the bug report, the step-by-step guide or the recap, written for you. No narration needed.
- Explained in about a minute
- Every claim linked to its second
- Keystrokes never logged
- Hosted in the EU
Checkout — Payment
Activity0 events
Watching the pixels and the interaction stream. Say nothing — it doesn't need you to.
- GitHub
- Linear
- Jira
- Slack
- Notion
- DOCX
- Markdown
- HTML
- GIF
How it works
Record. Watch. Explained.
Record
One click in Chrome. Talk, or don’t.
It watches
Pixels, clicks, console and network.
It explains
A report you can share, export or file.
Four modes
One recording. Four outputs.
Pick a mode when you record — or re-analyze later in a different one.
Retry after 402 returns 500 and disables the CTA
- 1.Add item, open checkout0:08
- 2.Click “Pay now” → 4020:52
- 3.Retry → 500, button disabled1:03
Agents · Pro and above
It doesn’t stop at the report.
Reproduction runs the recorded flow headlessly against an origin you control; results reflect that environment, and we report when it can’t reproduce.
No install · No account
Try it on a recording you already have.
QuickTime, OBS, a Loom export. Drop it in and watch it get explained.
Try it now — no account
≤ 3 min · ≤ 200 MB · deleted after 24 h unless you keep it
After the record button
The recorder is the easy part.
Search
Jump to the exact second.
Share
Public, password or team.
Export
PDF, DOCX, Markdown, GIF.
File issues
GitHub, Linear, Jira.
Voiceover
Narrate a silent clip.
API
Keys and signed webhooks.
FAQ
Questions people ask.
What is SceneRecap?
SceneRecap is an AI screen recorder for Chrome. You record a tab — with or without talking — and the AI watches the pixels and the interaction events (clicks, navigations, console errors, network failures) and writes the explanation: a bug report with reproduction steps, a step-by-step tutorial with screenshots, a plain-language explanation, or a recap of decisions and action items.
Do I have to narrate my screen recording?
No. SceneRecap is built for silent recordings. It reads the screen and the interaction log directly, so it does not depend on a transcript. If you do speak, the audio is transcribed and used as extra context.
How is this different from Loom, Scribe or Jam?
Loom is async video with transcription; Scribe captures click-through guides; Jam captures bug context. SceneRecap records the whole session and then explains it in four modes — bug report, tutorial, explain, recap — with every claim timestamped to the video, and it exports to GitHub, Linear, Jira, Notion, PDF and DOCX. And on Pro, the Repro Agent re-runs a bug report's flow headlessly against an origin you control and reports whether it actually reproduces. See the comparison pages for details.
Can SceneRecap turn a screen recording into a bug report?
Yes. Bug Report mode produces numbered reproduction steps, expected vs actual behaviour, the first bad moment, and console/network/visual evidence, each linked to a second in the video — plus a paste-ready issue body you can file to GitHub, Linear or Jira in one click.
Can it create step-by-step guides or SOP documentation?
Yes. Tutorial mode writes an ordered guide with a screenshot per step and exports to PDF, DOCX, Markdown, HTML or a Notion page.
What about passwords and sensitive data?
Keystrokes are never logged as text: when you type into a password or payment field we record only that a sensitive field was used, never its value. URLs are stored path-only, with query strings dropped. The recording itself is pixels — we do not alter what was on your screen — so you review the clip before anything uploads, and nothing leaves your machine until you do. Data is hosted in the EU (Google Cloud, Belgium/Frankfurt).
Is there a free plan?
Yes. The Free plan includes 1 free recording of up to 1 minute — enough to see the AI write a real report from your own screen, no credit card. Pro adds unlimited recordings, all four modes, PDF/DOCX exports, integrations, API and AI voiceover.
Can my own users report bugs on my site?
Yes — that is the reporting widget, a $39/month add-on. You paste one script tag; visitors click “Report a problem”, record what went wrong, and watch it back before anything is sent. The report arrives in your Inbox already written, with the JavaScript error and the failed request that caused it attached, because the widget is on the page when things break. Reports about the same bug on the same page are grouped, so five visitors hitting one problem is one row marked ×5 rather than five videos. It works on phones too, by asking for a recording from the device’s own screen recorder. See the reporting widget page for how it installs and what it collects.
Does it work without the Chrome extension?
Yes, two ways. You can record a tab directly in the web app (Dashboard → Record) with no install at all, or upload a recording you already have — QuickTime, OBS, a Loom export, a clip from your phone — and it goes through the same pipeline. The extension is still the richest path, because only it captures the click and console trail the AI uses as evidence.
Stop explaining your screen recordings.
Let them explain themselves.
Free plan · No card · Bug Report mode included