Capture with context.

A screenshot shows what broke. A Shotyx capture also carries the click path that got there, the console error underneath, the network call that failed, and the labels of the fields involved — in one file.

Record now — no install

The web app records your screen and is the editor. The Chrome extension is what adds the context.

Live

Don’t take our word for it — open a real capture

This is a genuine .shotyx bundle, not a video of one. It imports into your browser’s private storage and opens in the same editor you’d use for your own work: four screens, seventeen events on one clock, four drafted steps, and a redaction over the payment fields you can toggle, move, and export.

Imported locally, deleted whenever you want — like every other capture on this machine.

Context

The frames and the evidence, on one clock

Screens, clicks, keys, navigations, console output and network calls are recorded against the same timeline, so a step and the error it caused sit next to each other instead of in two tools. Field labels are captured; field values never are.

The event rail below is the demo capture’s, unedited.

  • 00:00.0 nav shop.northwind.test/cart
  • 00:01.4 click button.checkout — “Checkout”
  • 00:04.2 click input#email
  • 00:05.1 key Tab — field “Email”
  • 00:08.8 click button#pay-now — “Pay $128.40”
  • 00:08.8 submit Enter — form submitted
  • 00:08.9 net POST /api/payments/charge → 500
  • 00:10.5 error TypeError: … (reading 'total')
Privacy

Redaction destroys pixels, in your browser

Drawing a redaction doesn’t lay a black box over the image — the pixels underneath are resampled away before anything is written, exported, or shared. There is nothing left to peel off.

The rest follows from where captures live: your browser’s origin-private storage, on your own disk. Recording, editing and export all run on-device, and no capture is uploaded unless you deliberately share it.

Read exactly what that means

Distill

A recording becomes a steps doc

Distill condenses a long recording into one full-resolution keyframe per action, drafts a sentence for each from the events that caused it, and numbers them across the whole capture. Edit the wording, then export the walkthrough as a numbered document.

These four are the demo capture’s drafted steps.

  1. 1Open the cart and start checkout.
  2. 2Enter the payment details. (Redacted here — the pixels are gone, not covered.)
  3. 3Submit the payment and wait.
  4. 4Payment fails — the console shows the TypeError behind the 500.
Local AI

Free AI, on a model you already run

Point the editor at Ollama or LM Studio on your own machine and the summary, the reproduction steps and the drafted bug report are written there. Your browser talks to localhost directly — the capture never leaves the machine it was recorded on, and there is no account, no credits and no API key in the way.

Running a vision model? It reads the frames as well as the events. Running a text-only one? It works from the click path, the console error and the failed call, which is most of what a bug report needs anyway.

You install the runtime yourself — ollama.com or lmstudio.ai, a few minutes once. If you’d rather set up nothing at all, server credits draft the same things on our machines instead.

Upgrade

The extension is where context comes from

The web app records your screen — that alone is a good bug report. The Chrome extension records what the page was doing while you did it.

  • Click path

    Every click with its selector and the label the user actually saw.

  • Console

    Warnings and errors with their stack, on the same clock as the frames.

  • Network

    Method, URL, status and duration. Never response bodies.

  • Full-page shots

    Scroll-and-stitch capture with section markers for tall pages.

Coming to the Chrome Web Store Until then, start in the browser — captures move over intact.

Pricing

Free where it runs on your machine

Free

Everything local, forever.

  • Record, annotate, redact, export
  • Captures stay in your browser (OPFS)
  • A handful of Distill runs a day
  • Unlimited AI against your own local model
  • The Chrome extension and all its context

Capture, editing, export and local AI never need an account. Only the parts that use our servers — shares, hosted Distill runs, AI on our credits — are metered.

Record something broken. See what comes back.

Record now — no install