WebSocket Tester

Connect to any WebSocket server right from your browser. Enter a ws:// or wss:// URL, click Connect, and watch the live connection status as it goes from connecting to open. Send text messages and see a timestamped log of everything you send, every message the server sends back, and each connection event. Disconnect cleanly or clear the log anytime. It uses your browser's native WebSocket API and runs entirely client-side.

Status: Not connected
Log

ToolsSoup's WebSocket Tester is a free online WebSocket client that runs entirely in your browser. Paste a ws:// or wss:// endpoint, hit Connect, and the tool opens a live WebSocket connection using the browser's native WebSocket API. You can watch the connection status change in real time, send text messages to the server, and read a timestamped log of every message you send, every reply the server pushes back, and every connection event. It is the fastest way to manually test a WebSocket endpoint without installing a desktop app or writing a single line of code.

What is a WebSocket tester?

A WebSocket tester is a small client that opens a WebSocket connection to a server so you can verify the endpoint works and exchange messages by hand. WebSocket is a protocol for full-duplex, real-time communication: once the connection is open, the server can push data to the browser and the browser can send data to the server at any time over a single long-lived connection. This tool lets you connect to any reachable WebSocket server, send arbitrary text frames, and inspect the live stream of incoming and outgoing messages, which is ideal for debugging chat backends, live dashboards, trading feeds, game servers, and any service built on WebSockets.

How to test a WebSocket connection

Testing a WebSocket endpoint takes only a few seconds:

  1. Type or paste the WebSocket URL into the input. It must start with ws:// for an unencrypted connection or wss:// for a secure one.
  2. Click Connect. The status badge shows Connecting and then Open once the handshake succeeds.
  3. Type a message and click Send to push a text frame to the server. Your message appears in the log marked Sent.
  4. Watch for replies. Any message the server pushes back is added to the log marked Received, with a timestamp.
  5. Click Disconnect to close the connection cleanly, or Clear log to empty the message history.

ws:// vs wss:// and secure pages

ws:// opens a plain, unencrypted WebSocket connection, while wss:// opens an encrypted one over TLS, the same way https secures normal web traffic. Because this page is served over https, browsers block insecure ws:// connections from it as mixed content, so prefer wss:// endpoints here. The tool validates the URL before connecting and shows a friendly error if it does not start with ws:// or wss://. If a wss:// connection fails to open, the most common causes are a server that is offline, a TLS certificate problem, or a server that does not allow connections from a browser origin.

Why use this WebSocket tester?

  • Uses the browser's built-in WebSocket API, so there is nothing to install and no extension required.
  • Shows live connection status as it moves through connecting, open, closed, and error states.
  • Logs every sent message, received message, and connection event with a timestamp.
  • Renders incoming server messages as plain text so untrusted content can never run as code.
  • Lets you disconnect cleanly and clear the log so each test session starts fresh.
  • Runs fully client-side: the connection is made straight from your browser and nothing is proxied through our servers.

Frequently asked questions

Does the connection go through your servers?

No. The WebSocket connection is opened directly from your browser to the server you enter, using the native WebSocket API. ToolsSoup never proxies, stores, or sees your messages. Everything happens on your device.

Why can't I connect to a ws:// URL?

This page is served over https, and browsers block insecure ws:// connections from a secure page as mixed content. Use a wss:// endpoint instead. The tool also rejects any URL that does not begin with ws:// or wss:// and shows an error so you can fix it.

Can I send JSON or binary data?

You can send any text, including JSON, by typing or pasting it into the message box; it is sent as a text frame exactly as written. The tester focuses on text messages. Binary frames the server sends are noted in the log but not decoded.

Why did my connection close right away?

A connection that opens and immediately closes usually means the server rejected the handshake, the endpoint does not speak WebSocket, the URL or path is wrong, or the server does not accept connections from a browser origin. The log records the close event so you can see when it happened.

Is it safe to connect to an unknown server?

The tester treats every incoming message as untrusted and displays it as plain text, never as HTML or executable code, so a malicious server cannot run scripts in your browser through this tool. Still, only connect to endpoints you trust, since you are making a real network connection to them.