Free tools that run in your browser. Use any tool without an account.

Favourites Cart
Sign in
Join free

WebSocket Tester

  • Free
  • Nothing stored
  • No account needed

This tester opens a WebSocket (ws:// or wss://) from your browser, sends text or JSON frames, and shows a timed log with JSON pretty printed plus the close code. Example: send 1 JSON message and view the reply.

Fetches public data to give your answer. We do not keep your inputs. Report a problem
Advertisement

About WebSocket Tester

This is a browser WebSocket client you use to test servers from your machine. Developers, QA engineers, and operators use it to smoke test endpoints, check subprotocols, or validate messages. The tool opens ws:// or wss:// directly from your browser and sends text or JSON frames. It logs sent and received messages with timestamps, pretty-prints JSON, and shows the close code. Connections go straight to the server; FreeToolr does not relay or see your messages or frames. You do not upload files or need an account. The tester runs entirely in the page so you do not install software. The page also highlights common browser limits such as mixed content and the inability to add custom handshake headers to help you troubleshoot.

How to use it

  1. 1Enter a ws:// or wss:// server URL and optional subprotocols.
  2. 2Click Connect to open a direct WebSocket from your browser.
  3. 3Send text or paste JSON in the message box and press Send.
  4. 4Watch the timed log of Sent and Received messages and the final close code.
Advertisement

Worked example

Connect to ws://localhost:8080 and send one JSON message: {"ping":1}. If the server echoes, the log shows: 2026-11-07T12:00:00.000Z Sent: {"ping":1} and 2026-11-07T12:00:00.150Z Received: {"ping":1} then Close code: 1000.

How it works

Connects to a WebSocket server (wss:// or ws://) from the visitor's browser, sends text or JSON messages and shows a timed log of sent and received messages with JSON pretty printed, plus the close codeThe connection goes straight from the browser to the server; FreeToolr does not relay or see itWorks in the browser with nothing to install

Source: RFC 6455 - The WebSocket ProtocolMDN WebSocket APIChrome Local Network Access guidance. Last checked 7 November 2026.

What it is good for

  • Run tests from your browser with no install or account.
  • See timestamps and pretty-printed JSON for easy debugging.
  • Connection is direct; FreeToolr does not relay or store your messages.
  • You cannot add arbitrary HTTP headers like Authorization in the browser handshake.
  • An HTTPS page can only open wss://; ws:// will be blocked as mixed content.
Advertisement

Questions people ask

Can this page set HTTP request headers for the WebSocket handshake?

No. Browsers do not let script add arbitrary headers during the WebSocket handshake. Use cookies, a query token, Sec-WebSocket-Protocol, or send an auth message after connect. See RFC 6455 and MDN for details.

Why does ws:// fail when the page uses HTTPS?

Mixed content rules block insecure ws:// from an HTTPS page. Use wss:// for public servers. Local loopback or private addresses can behave differently per browser, and may prompt for permission.

How do I inspect binary frames?

Compose binary as hex or base64 and send it. Incoming binary is shown as hex or base64 in the log so you can inspect raw frames. The tester converts formats in the browser before sending.

What does close code 1006 mean in the log?

Close code 1006 means the connection closed abnormally and no close frame was received. See RFC 6455 and the MDN CloseEvent.code documentation for the full list of standard codes.

Does FreeToolr see or store my WebSocket messages?

No. The page opens a direct WebSocket from your browser to the server. FreeToolr does not relay, receive, or store the frames or messages.

Why can't I reach a WebSocket server from this tester?

Common causes are mixed content blocking, server firewall rules, certificate trust issues, or ISP filtering. Test from the same network your users use and check browser console for errors.

Help keep every tool free

FreeToolr stays free because people help it grow. Share a tool you like, tell us what to build next, or support us on Ko-fi.

Advertisement
Advertisement