Send message
Ctrl+Enter to send
Message log
No messages yet. Connect and send something to see the exchange here.
Encoding & Text
WebSocket Test Tool
A WebSocket is a persistent connection between a browser and a server, so once the handshake succeeds, messages flow both ways without another request. This page is a browser-based WebSocket client: paste a ws:// or wss:// URL, connect, type a message, and read what comes back — every frame listed with the time it arrived, kept in a history you can resend from. It runs entirely in your browser, with no install, no account, and no server in the middle.
What you can do
Connect in seconds, install nothing
Paste a ws:// or wss:// URL and press Connect. There is no extension to install, no Node.js to set up, and no account to create — the connection is made straight from your browser to your server, so you see the same handshake and the same errors you would see in your own app. If the protocol is missing, the field adds it for you.
Send JSON, plain text, or binary
The composer has a Text tab, a JSON tab that pretty-prints what you type, and a Binary tab for bytes. Sent messages stay in the history with a timestamp and a direction arrow, so you can copy an exact payload, resend it, or compare what the server echoed back against what you sent.
Every reply, timestamped and replayable
Incoming messages land in the log with the time they arrived, marked as text or binary. Filter, copy one entry, or copy the whole session as JSON. When a server answers with a JSON error object, the raw payload is right there — no need to dig through console logs to find it.
Diagnostics that name the real cause
When a handshake fails, the page shows the browser's own error text and a plain-language reading of it: a 404 means the path is wrong, a 200 means you hit a plain HTTP endpoint instead of a WebSocket one, and a blocked ws:// URL means mixed content. A warning appears before you connect if the page is https and the URL is ws://.
Free, private, and stateless
No sign-up, no upload of your payloads, and nothing stored on a server — the messages go from your browser to the server and back, and nowhere else. You can clear the log whenever you like, and closing the tab ends the session.
How to use
- 01
Paste your endpoint and connect. Type or paste a URL such as wss://echo.websocket.org or ws://localhost:8080/ws into the address bar. If you leave the protocol off, ws:// is added for you. Press Connect and watch the status line change to open.
- 02
Send something and watch what comes back. Type into the composer on the left — Text for a plain string, JSON for a payload (it is formatted as you type), or Binary for bytes — and press Send or hit Ctrl+Enter. Every message you send and every reply you receive appears in the log on the right with the time it arrived and an arrow showing the direction.
- 03
Read the failure, then fix it. If the connection does not open, the diagnostic bar explains what the browser's error means and what usually causes it. Once you have a clean exchange, copy the exact payload from the log, or copy the whole session as JSON, and paste it into your test or your bug report.
About WebSocket testing
What WebSocket is, and how the handshake works
A WebSocket is a protocol that upgrades an ordinary HTTP connection into a persistent, bidirectional channel. The client opens the connection with an HTTP Upgrade request, the server answers with 101 Switching Protocols, and from that point both sides can push messages to each other at any time without another request or response cycle. That is the difference from plain HTTP, where the server only speaks when the client asks. A WebSocket carries no timezone and no unit of its own — it just moves bytes, and it is up to the application to decide whether a given frame is JSON, plain text, or a protocol buffer. The URL scheme is part of the contract: ws:// is the insecure variant, wss:// is the same protocol wrapped in TLS, and the two behave identically above the handshake.
How to test a WebSocket endpoint from a browser
Testing a WebSocket endpoint means four things: does the handshake succeed, does your payload go out unchanged, does the server's reply come back and look right, and can you tell the two apart when something goes wrong. This page covers all four for one connection at a time, which is enough for the large majority of API work. It also helps to know what the alternatives cost. Postman does WebSocket too, but it needs a desktop install and an account before you can save a payload template. wscat is excellent and free, but it needs Node.js and a terminal, which is the wrong place to be when the payload came out of a browser bug report. Chrome DevTools is always there, but its WebSocket panel is a view — you can watch frames go by, yet you cannot keep a history you can resend from, and the panel has to be open before the connection starts. If you want a scratch server rather than a client, this page cannot give you one: run your own server, or use a public echo endpoint such as wss://echo.websocket.org, and point this page at it.
Reading a failed handshake
When the handshake fails, the browser reports an error and the connection never opens. The wording you will recognise is "Error during WebSocket handshake: Unexpected response code: 400" — and the number is the HTTP status the server returned instead of 101. A 404 usually means the path is wrong or the route is only registered under a different prefix. A 401 or 403 means the server wants credentials you did not send. A 200 is a good clue that you pointed at a plain HTTP endpoint, because a WebSocket server answers the upgrade with 101 and nothing else. A 301 or 302 means the server tried to redirect the upgrade request, which browsers do not follow. A 502 or 503 usually points at a proxy or gateway in front of the server rather than at your own code. A connection reset part-way through the handshake means something closed the socket before the negotiation finished. Separately, if the page itself is served over https and your URL starts with ws://, the browser blocks it as mixed content before a single byte is sent — use wss://, or serve your front end over http while developing locally.
How this browser client compares
| Aspect | 1Tools | Postman | wscat | Chrome DevTools |
|---|---|---|---|---|
| Install | None — open the page | Desktop app | Node.js + npm | Built into Chrome |
| Account | No sign-up | Account to save templates | None | None |
| Replayable history | Yes — timestamped log you can resend from | Saved requests after setup | Terminal scrollback only | View only; panel must be open first |
| Custom headers | No — browser limit | Yes | Yes | No — browser limit |
| Best for | Quick browser-side checks and bug reports | Saved collections and team workflows | CLI scripts and CI | Watching frames in an existing page |
Free, private, and no install
No install, no account
Open the page and connect. There is no extension, no Node.js, no sign-up, and no API key to set up.
Your messages stay between you and your server
This site has no backend for your payloads. Frames go from your browser to the endpoint you typed, and nowhere else.
Clear the log any time
Message history lives in the page. Clear it or close the tab and it is gone; nothing is kept.
Honest about limits
Browsers cannot set custom headers or send protocol-level pings. The page tells you what works and what does not, instead of pretending.
FAQ
JSON Formatter & ValidatorJSON Diff & CompareText Diff & CompareAll toolsBack to home
Feedback
Found a confusing error, a missing diagnosis, or a payload shape this page should handle better? Tell us — real reports shape the next FAQ and UI tweaks.