WebRTC Data Channel Test
Test RTCDataChannel in your browser with a local WebRTC loopback. Verify text and binary transfer, average RTT, channel state and approximate throughput.
RTCDataChannel loopback test
ReadyThis is a same-browser loopback test. Throughput and RTT reflect browser/device behavior, not Internet speed.
What does this RTCDataChannel test measure?
The test creates two local RTCPeerConnection objects in your browser and negotiates an RTCDataChannel between them. It then verifies text and binary data transfer, measures repeated ping-style round trips, and sends a larger payload to estimate local browser throughput.
Local loopback versus real network performance
The resulting RTT and throughput describe browser and device behavior only. They should not be interpreted as Internet speed, remote WebRTC latency or TURN performance because both peers run on the same machine. A meaningful network test requires a remote peer or controlled test endpoint.
Related WebRTC tools
Use the WebRTC stats viewer to inspect live peer-connection statistics, the ICE candidate test to inspect network candidate gathering, or the TURN server test to verify relay allocation with your own TURN credentials.
RTCDataChannel test FAQ
Is the Data Channel throughput result my Internet speed?
No. This test uses two peer connections inside the same browser, so its throughput and round-trip time are local browser and device diagnostics, not measurements of your Internet path.
What does the text and binary test verify?
The tool sends a text message and a binary ArrayBuffer over RTCDataChannel and checks that the receiving peer gets data of the expected type and size.
Why is the measured RTT very low?
Because both peers run locally in the same browser process and machine. A real remote WebRTC connection includes network transport, routing, congestion and possibly TURN relay latency.