Skip to content

WebSocket Tester

Connect to ws:// or wss:// endpoints with the native browser WebSocket API. Send and receive frames in JSON, text, or hex.

WebSocket Tester

Connections go directly from your browser to the target host using the native WebSocket API. No AI Dev Hub server is in the path. The remote endpoint will see your browser's IP, headers, and Origin.
idle

Send

Log (0)

No messages yet.

Last updated:

This tool is provided as-is for convenience. Output should be verified before use in any production or critical context.

For AI agents: how to call this tool

Machine-readable contract, endpoints and examples. Humans can ignore this section.

Best Path For Builders

Browser workflow

Runs instantly in the browser with private local processing and copy/export-ready output.

Browser Workflow

This tool is optimized for instant in-browser execution with local data handling. Run it here and copy/export the output directly.

/websocket-tester/

For automation planning, fetch the canonical contract at /api/tool/websocket-tester.json.

How to Use WebSocket Tester

  1. 1

    Enter your endpoint

    Provide a ws:// or wss:// URL and an optional comma-separated list of subprotocols. The browser opens the connection directly with the native WebSocket API.

  2. 2

    Send text or binary frames

    Use Send text for the textarea contents as a string frame, or Send hex bytes to ship the input as raw binary. Hex is parsed pair-by-pair into a Uint8Array.

  3. 3

    Switch payload views

    Toggle between text, JSON, and hex on the message log. JSON tries to parse strings into pretty objects; hex shows space-separated UTF-8 byte equivalents.

  4. 4

    Replay or auto-reconnect

    Click replay on any past message to load its payload back into the draft. Enable Auto-reconnect to retry on close events outside an explicit Disconnect.

Frequently Asked Questions

What is WebSocket Tester?
WebSocket Tester is an in-browser client for ws:// and wss:// endpoints. Open a connection, send and receive frames, and inspect each payload as text, JSON, or hex with timestamps.
Where does the connection actually go?
The browser opens a direct WebSocket from your tab to the target host using the native WebSocket API. No AI Dev Hub server proxies the traffic; the remote host sees your IP, headers, and Origin.
Can I send binary frames?
Yes. Switch the textarea contents to space-separated hex bytes, then press Send hex bytes. The bytes are parsed into a Uint8Array and shipped as a binary frame; logged echoes also render as hex.
How does auto-reconnect behave?
When enabled, the client schedules a reconnect after the configured delay any time the socket closes without an explicit Disconnect. The attempt counter resets to zero on a clean open event.
Does it send my data to a server?
Frames go directly from your browser to the WebSocket endpoint you specify. AI Dev Hub does not see the URL, payloads, or headers; the remote host receives them as if you connected from your own client.