Inspect WebSocket messages in real-time. Simulate network conditions like latency, jitter, and packet loss.
Perfect for debugging chat apps, live dashboards, multiplayer games, and any real-time application.
Also check out our webhook debugger for HTTP webhook testing.
Create Endpoint
Get a unique WS URL
Connect Client
Point your app to it
Debug & Test
Inspect & simulate
A complete WebSocket debugging toolkit. Inspect messages, simulate network conditions, and test real-time applications with ease.
From setup to debugging in under a minute. No complex configuration, just instant WebSocket inspection.
Create a new WebSocket debugging endpoint from your dashboard. You'll get a unique WSS URL.
wss://app.hooklistener.com/ws/my-debug-endpoint-abc1Point your application's WebSocket client to the debug endpoint URL instead of your server.
const ws = new WebSocket(
"wss://app.hooklistener.com/ws/my-debug-endpoint-abc1"
);
ws.onmessage = (event) => {
console.log("Received:", event.data);
};
ws.send(JSON.stringify({ action: "ping" }));Watch all messages flow through the debug console. See direction, timestamps, and payload content.
← Incoming │ 10:30:15.234 │ {"action": "ping"}
→ Outgoing │ 10:30:15.456 │ {"action": "pong", "ts": 1705746615}
← Incoming │ 10:30:16.001 │ {"type": "subscribe", "channel": "updates"}
→ Outgoing │ 10:30:16.089 │ {"type": "subscribed", "channel": "updates"}Add latency, jitter, and packet loss to test how your application handles poor network quality.
Network Simulation Settings:
├── Latency: 250ms (base delay)
├── Jitter: ±50ms (random variation)
└── Packet Loss: 5% (drop probability)
Message sent with 287ms delay (250 + 37ms jitter)
Message dropped (5% packet loss triggered)Ready to debug your WebSocket connections?
Create Your First Debug EndpointClaude Code, Codex or Cursor can drive these endpoints through the Hooklistener MCP server: create a WebSocket, Socket.IO, MQTT or SSE endpoint, wait for the message your client sends, answer like your server and read the whole session back.
Move from one-off bins to a production-grade webhook platform with replay, forwarding, and monitoring built in. Compare features side-by-side and migrate in minutes.
Persist webhook history for 14+ days, search instantly, and replay to any environment.
Send events to QA, staging, and production with conditional routing and transformations.
Invite collaborators, mask secrets, and stay audit-ready—no public bins or shared tokens.
How is this different from browser DevTools WebSocket inspection?
Browser DevTools only show WebSocket frames for that browser session. Hooklistener captures messages server-side, supports network simulation, and lets you debug multiple clients simultaneously from a single dashboard.
Can I test WebSocket reconnection logic?
Yes. Use packet loss simulation to trigger disconnections and verify your client's reconnection behavior. You can also pause endpoints to force clients to handle connection failures.
Does this work with Socket.IO?
Yes. Create the endpoint with the Socket.IO protocol and connect with socket.io-client 3.x or 4.x using the endpoint's path and transports: ["websocket"]. Events, namespaces, acknowledgements and binary attachments are recorded. MQTT over WebSocket and Server-Sent Events endpoints are available too.
Everything you need to know about debugging WebSocket connections
Have more questions about WebSocket debugging?
Check out our developer guidesStop guessing why your WebSocket connections fail. Get real-time visibility into every message, simulate network conditions, and ship with confidence.
Free tier available • No credit card required • Setup in seconds