Native WebRTC diagnostics
Find where a peer connection fails
Connect two browsers, compare direct ICE paths with and without STUN, and inspect the selected candidate pair, state transitions, data-channel RTT, and synthetic-video stats.
- 01Open twiceLoad this page in both browsers.
- 02Exchange payloadsSend the offer over, then the answer back.
- 03Read the pathCompare live results on both sides.
01
Start or answer a connection
Ready
Choose how this browser starts
Create an offer here, or paste an offer from the other browser below.
Couldn't continue
Clipboard handoff. Send the outbound payload privately, then paste the response you receive.
From this browserSend
Nothing generated yet
From the other browserReceive
Paste below
02
Connection snapshot
Not started
No connection tested yet
Complete the clipboard exchange to test a direct path.
No TURN server is configured, so failure does not prove WebRTC is unavailable.- Role
- idle
- ICE path
- none
- Peer connection
- new
- ICE connection
- new
- ICE gathering
- new
- STUN discovery
- not started
- STUN server
- none
- Selected path
- waiting
- Data channel
- closed
- Video track
- not negotiated
- Local candidates
- none
- Remote candidates
- none
- Selected candidate pair
- none
View raw diagnostic JSON
No manual connection is active.
Browser readiness
- Secure context
- checking
- WebRTC API
- checking
- Configured STUN servers
- loading