Why it matters
Wireshark captures and proxy logs show WebSocket traffic as bytes. Reading the two-byte header and unmasking by hand is slow and error-prone.
Paste the hex to see each frame's type and contents, or build a frame to test a server.
How to use it
- Type or paste your input; the example shows the format.
- Press Decode frames. Results also update as you type.
- Read the summary line, then the table, notes or output below it.
- Copy or download what you need. Nothing leaves this page.
FAQ
Why are some frames masked?
RFC 6455 requires every client-to-server frame to be masked with a random 4-byte key, to stop cache poisoning through proxies.
Is my input uploaded?
No. The tool runs in your browser and nothing you type, paste or open is sent anywhere.
Can I rely on the result?
It follows the public specification or formula named on this page and says where it simplifies. Check anything critical against the official tool or documentation before you ship it.