Can custom WebSocket headers be set?
No. Browser WebSocket connections do not allow arbitrary headers; use query parameters or subprotocols when supported.
WebSocket Tester
Connect to WebSocket endpoints and inspect live messages.
Requests go directly from this browser to the target server you enter. Your Free Tools does not receive, proxy, store, or log the URL, headers, body, files, messages, or results.
WebSocket Tester
Connect to WebSocket endpoints and inspect live messages. Supports subprotocols, timeouts, text, JSON, hex, Base64, binary previews, close code, close reason, and session log download.
WebSocket testWS endpointWSSlive messagesbinary messages
Use cases
- - Test browser-accessible WebSocket endpoints.
- - Inspect JSON and binary protocol messages during development.
- - Export a current-session log for debugging.
How to use
- 1Enter a ws:// or wss:// URL and optional subprotocols.
- 2Connect and send text, JSON, hex, or Base64 messages.
- 3Inspect live received messages, resend history, close the connection, or download the session log.
Features
Test browser-accessible WebSocket endpoints.
Inspect JSON and binary protocol messages during development.
FAQ
Can this send real ping frames?
No. Browsers do not expose WebSocket ping control frames; use an application-level ping message instead.
Does Your Free Tools store messages?
No. Messages and logs stay in the current page session and are not sent to Your Free Tools.