WebSocket Tester
Connect to any wss:// endpoint, send messages and inspect the live conversation log.
Closed
No messages yet. Connect and send something.
Tip: Ctrl/Cmd + Enter to send
Private & SecureRuns in your browser — nothing is uploaded
Easy to UseJust paste or type — instant results
Free ForeverUnlimited use, no sign-up
Fast & ReliableAdvanced tech, fast and stable
Testing a WebSocket usually means writing a throwaway script just to see if messages flow. This connects to a WebSocket endpoint from your browser, lets you send messages and watch what comes back, and keeps a running log of the session so you can see the whole exchange.
How to use: WebSocket Tester
- 1Enter inputEnter the WebSocket address you want to connect to (ws:// or wss://).
- 2Set optionsClick Connect to open a live connection to that server.
- 3ProcessType a message and send it to test the server's response.
- 4Get resultWatch every sent and received message, plus connection status, in the live log.
Common use cases
Check a connectionConfirm an endpoint accepts a connection and stays open before you wire it into an app.
Send test messagesType a message, send it, and see the server's reply in the log.
Watch a live feedConnect to a stream and watch messages arrive in real time to understand its format.
Debug a handshakeSee whether a connection opens, closes or errors, and when, while you chase a bug.
Good to know
Secure pages need secure socketsA page served over HTTPS can only open a secure WebSocket; a plain connection is blocked by the browser. Use the secure scheme.
The connection is yours, not oursYour browser talks directly to the endpoint you enter; we do not sit in the middle or keep your messages.
The log lives in this tabThe session record is held in the page while it is open; close or reload the tab and it is gone, since nothing is stored.
Auth may need a token in the URLMany servers expect a token as a query parameter or an early message, since browsers cannot set custom headers on a WebSocket. Check the API's docs.