TailWASM / demo
EXPERIMENTAL

WebRTC direct. DERP fallback.

Connect browsers with encrypted streams. Use WebRTC for a direct connection, with automatic DERP fallback when needed.

Connection setup

1 This browser

Preparing your temporary address…

Relay settings

Use the public Tailcat map, the Tailscale relay map, or a CORS-enabled custom map. Custom maps must allow cross-origin reads from this page.

2 Connect a browser

Use an address from another browser or device.

One connection carries messages in both directions. Either browser can connect first.

Live transport

No peer connected

Connections start through DERP and attempt a WebRTC upgrade.

WebRTC upload / download— —Total sent / received
DERP upload / download— —Total sent / received
ICE round trip—No selected candidate pair
Turn off to move an active stream to DERP.

WebRTC debugging

Open Chrome’s diagnostics in another tab before connecting. Select this demo’s PeerConnection, then inspect data-channel and candidate-pair statistics. Regular DevTools Network shows DERP WebSockets, not WebRTC DataChannel packets.

Paste it into the address bar of a new tab. Browser internal pages cannot be opened reliably by ordinary web links. WebRTC debugging guide

Transfer test

1 GB = 1,000,000,000 bytes. Sent in small chunks and verified by the receiver.

Send · receiver-confirmed — Ready to send 1 GB
Receive — Waiting for a test
How measurements work

Test speeds use received payload bytes over the last 2 seconds. Transport speeds above count encrypted packets, including overhead and retransmissions. Transport upload counts local sends, not confirmed delivery. The final average includes streaming, payload verification, and the receiver’s completion receipt.

Messages

    Messages appear here on both browsers.