WebSocket Frame Parser (RFC 6455)

Look inside captured WebSocket traffic to see exactly what each frame carries.

Use the tool

Why this tool exists

Paste hex bytes of one or more frames. For each frame the parser shows the opcode (text, binary, ping, pong, close, continuation), whether it is a final fragment, RSV bits (compression extensions), the mask and payload length (7, 16 or 64-bit forms), the unmasked payload as text or hex and any close code and reason. Output was compared with frames built by the ws library.

Client-to-server frames are always masked and server frames are not. Payloads of permessage-deflate frames are compressed and show as binary.

No data is sent anywhere: the work happens in your browser, so you can use it offline once the page has loaded.

How to use it

  1. Copy the frame bytes from your capture tool.
  2. Paste the hex.
  3. Read each frame.
  4. Check masking and opcodes against what your client or server should send.

Frequently asked questions

Why are some payloads unreadable?

The connection may use compression (RSV1) or a binary protocol.

What is the mask for?

Clients XOR the payload with a random key so intermediaries cannot confuse it with HTTP.

Can it capture traffic?

No. Use your browser dev tools or a proxy to copy the bytes.

Is my data sent anywhere?

No. Everything is processed in your browser, and the page makes no network requests with your input.