Skip to content
All products

postMessage Catcher

Every message. Every frame. No console noise.

Pasting console.log into a page to read postMessage fails in three ways: it sees one frame, it starts too late, and it floods the console. This replaces that with a panel that was built around those three failures.

Latest release v3.0.0 · Nov 15, 2026

postMessage Catcher: Every message. Every frame. No console noise.
What it does

01

Every frame, from document_start

iframes, srcdoc, about:blank and data: frames are covered before any page script runs, including traffic sent during page load.

02

Observe, never modify

The probe never wraps window.postMessage. Replacing it rewrites event.source and breaks pages that validate the sender, so capture is receive-only.

03

Trusted attribution

event.origin plus the relationship — self, parent, child or other — including senders from another origin.

04

Payloads parsed, not dumped

JSON-encoded payloads open as a tree with a Parsed / Text switch; the list shows the inner discriminator so messages are easy to tell apart.

05

Survives reloads

A per-tab ring buffer lives in the worker and persists a compact copy to storage.session, so you can open the panel after the bug happened.

06

Search, filter, export

Direction filters, keyboard navigation, ⌘F search across payload and origin, and JSON export for the whole session.

Inside
The postMessage panel listing captured messages with time, origin, type and size
Every message, with origin, direction and size.
A JSON payload parsed into a tree view with parsed and raw switches
JSON payloads open as a tree, with the raw text one click away.
The extension popup with per-tab recording and a theme switch
Recording per tab, plus a master switch.

Why it exists

Most postMessage bugs are not bugs in the handler — they are bugs in what the handler never saw. A message sent before your listener attached, a frame you forgot about, a payload that arrived twice.

v3 is a rewrite built on three rules: be early, observe without modifying, and never break the page. That meant moving capture into the MAIN world at document_start across all frames, and keeping everything pass-through with bounded snapshots and a try/catch on every capture path.

Where it stops

targetOrigin is not shown — it only exists on the sending side, and patching senders is the thing that breaks pages. Cross-origin frameId is unknowable for the same reason. MessagePort, BroadcastChannel and Worker traffic are not captured yet.

No network, no telemetry, no remote code. Messages are captured and stored in your browser and never leave it.

Also from the studio

Changicon