WebSocket Tester
Connect & debug WebSockets
100% local — nothing is uploaded
Disconnected
Try an endpoint:
Browsers cannot send custom headers over WebSocket. Put tokens in the URL query or a subprotocol.
Received / Sent0
Messages will appear here once you connect.
How to use
- Enter a WebSocket URL (ws:// or wss://) and click Connect. The status dot shows the connection state.
- Type a message and click Send (or press Enter). Sent and received messages appear in the log with direction, time and size.
- JSON messages are pretty-printed automatically; use Pause to freeze the log while streaming.
- Click any example endpoint to try the tool instantly, or Disconnect to close the socket.
FAQ
Can I set custom headers like Authorization?
No — the browser WebSocket API does not allow custom handshake headers. Pass tokens as a query parameter or via the subprotocol field instead.
Why does my connection close immediately?
Common causes: the server requires authentication, the URL uses the wrong scheme (wss:// for TLS endpoints), or a proxy/load balancer rejects the handshake. Check the close code shown in the log.
Is my traffic stored anywhere?
No. Messages exist only in this browser tab; nothing is logged to a server. URL history is kept in localStorage only.