Event Snapshots

The HAR file that grew up.

An Event Snapshot is a single .esa file bundling network requests, console output, WebSocket frames, SSE messages, an optional screenshot, the cookie jar and environmental metadata. It's HAR's job, done properly, and it works between any two webQsee users, free tier included.

All features
Side-by-side comparison: a small .har file icon on the left and a larger .esa Event Snapshot file icon on the right that explodes outward into layered sheets representing HTTP requests, WebSocket frames, screenshot, cookies and environment metadata
Why a new format?

HAR forgets too much.

HAR, the HTTP Archive format, was designed in 2007 for HTTP performance traces. It records request and response data, and that's mostly it. No console messages. No WebSocket frames. No SSE streams. No screenshots. No cookie state. No browser fingerprint. The things a modern debugger actually needs.

Event Snapshots fill the gap. One file, everything inside, ready to attach to a ticket or drag into someone else's webQsee window.

What's in an .esa
  • Every captured HTTP request and response
  • Every WebSocket frame (both directions)
  • Every Server-Sent Event chunk
  • Every console log line + stack trace
  • A screenshot, visible area or full page, taken as you create it
  • Cookies of every URL the page requested
  • User agent, OS, browser, viewport, tab zoom, languages
  • CPU, memory, connected displays, timezone offset
  • Capture timestamp + event count
Side by side

Event Snapshot vs HAR.

CapabilityHAREvent Snapshot
Network requests
WebSocket frames
Server-Sent Events
Console messages
Screenshot
Cookies
User agent / OS / viewportpartial
CPU, memory, displays, timezone
Selective subset export (in webQsee) whole capture
Readable by non-webQsee tools
File extension.har.esa
Still need HAR for an external tool?

We export HAR too, with the same selective subset choice. Reach for .har only when the receiving tool isn't webQsee (Postman, Charles, perf analyzers). For human-to-human handoff between webQsee users, .esa is the format.

Open HAR page
Universally sharable

Free users get the full file.

Unlike Behavior Reports, which require a paid tier to import, Event Snapshots can be opened by anyone with webQsee installed. Free users can drop a teammate's .esa into the Import tab and inspect every captured event.

An Event Snapshot bundles the whole capture together with a screenshot taken at the moment you create it, so the two always describe the same instant. That makes it the cleanest way to file a bug report: no "what version of Chrome were you on?" follow-up, no "can you screenshot it?" round trip. Just the evidence. If you do need only a handful of rows, export those as HAR or Excel instead.

How import works
Typical workflow
  1. Reproduce the bug with webQsee capturing.
  2. Choose Save or Export > Create Event Snapshot.
  3. Pick visible area or full page for the screenshot.
  4. Attach the .esa to a ticket or chat, or share it as a link.
  5. Recipient drags it into webQsee and inspects it.
Related capabilities

More on this.

HAR Compatibility

Need the legacy format for an existing toolchain? We export it.

All export formats

HAR, Excel, ESA, BAR, MHTML, the full menu.

The Analyzer

Where you pick the subset to bundle into your snapshot.

Stop guessing. Start webQseeing.

Add webQsee to Chrome or Edge in one click. Most features are free, forever, no signup needed. Upgrade only if your team needs cloud sharing, S3 storage and Pro-grade tooling.

Try view.webqsee.com See pricing

Works in Chrome 103+, Edge 103+ and most Chromium-based browsers. Install instructions.