Your files stay on your device

WebRTC loopback test

Check that video-call connections work in this browser, without a server.
local loopback only · no STUN/TURN, no media · every connection closed on StopRun loopback test

Gathering ICE candidates enumerates network interfaces; host candidates carry your LAN addresses and mDNS names. Nothing leaves this tab: the second connection is another object in the same page, and only a USER-CLICKED run gathers anything.

This is a loopback test: two RTCPeerConnection objects in this page negotiate with each other over a data channel. No media is captured, no STUN/TURN server is configured, and no packet ever leaves the machine.
I understand ICE gathering lists my local network interfaces; nothing leaves this tab.

- Gathering ICE candidates enumerates network interfaces; host candidates carry your LAN addresses and mDNS names. Nothing leaves this tab: the second connection is another object in the same page, and only a USER-CLICKED run gathers anything.
- This is a loopback test: two RTCPeerConnection objects in this page negotiate with each other over a data channel. No media is captured, no STUN/TURN server is configured, and no packet ever leaves the machine.
- Close releases both connections and every transport; the candidate list lives in page memory only. The active indicator goes dark the moment the run ends; an idle page here holds zero WebRTC state.
- The acknowledge checkbox is the plan’s pre-run disclosure gate: the run button stays disabled until you have read what candidate gathering means.
Paste, drop, or type to begin. Everything stays on this device.

More device tests

- Codec matrix (/device/codec-matrix)
All device tests (/device)

Canonical HTML: https://nutter.tools/device/webrtc/
Markdown version: https://nutter.tools/device/webrtc/index.md
Plain-text version: https://nutter.tools/device/webrtc/index.txt
Agent index: https://nutter.tools/llms.txt