WebRTC Diagnostics
Online WebRTC diagnostics tool for ICE candidate collection, NAT analysis, STUN connectivity testing, and media device inspection
This tool runs WebRTC diagnostics in your browser and sends connectivity checks to the STUN servers you specify.
Browser Compatibility Check
WebRTC Connectivity Test
Test Result
Media Stats
0
Bitrate (Kbps)
0%
Packet Loss
0ms
Jitter
0ms
Round Trip Time
Media Devices
Diagnostics
WebRTC Support
0/0
User Agent
Platform
Language
Timezone
Network
Offline
Connection Type
Unknown
Documentation
WebRTC diagnostics helps identify real-time communication issues by checking browser support, collecting ICE candidates, inferring NAT behavior, reading connection metrics, and validating local media devices.
How to Use
- Review compatibility checks to confirm browser WebRTC support.
- Set or select STUN servers, then run connectivity diagnostics.
- Use connection status, NAT type, and stats to judge direct path quality and relay needs.
- Load media devices to validate microphone, camera, and speaker detection.
FAQ
Why does the connection fail?
Typical reasons include UDP blocked by firewall, incompatible NAT behavior, unreachable STUN service, or browser policy restrictions.
When is TURN required?
If symmetric NAT or strict enterprise network policies prevent direct paths, TURN relay is commonly needed.
Why are device names empty?
Browsers hide media labels until microphone or camera permission is granted. Allow permission and reload device list.
Optimization Tips
- Prefer wired network over Wi-Fi to reduce jitter and packet variation.
- Use STUN/TURN nodes close to user regions to reduce latency.
- Open required UDP ports and TURN domains in enterprise firewall policies.
- Run multi-region tests in production-like network environments before release.
- Keep browsers and OS updated to reduce compatibility issues.