Practical browser diagnostics without an account
WebRTCTest is an independent collection of browser-based tools for checking the parts of a device and network that commonly affect real-time communication. The site helps people confirm camera, microphone and speaker behavior before a call, while giving developers focused ways to inspect WebRTC capabilities, ICE candidates, codecs, session descriptions, data channels and browser statistics.
The project is designed around a simple idea: a useful diagnostic should explain what it actually measured. A successful browser check is evidence about the current browser, device and test path; it is not a guarantee that every meeting service or remote peer will work. Each tool therefore pairs its result with context, limits and relevant next steps.
How the tests work
Most tests execute directly in the current browser using standard web APIs. Camera and microphone checks request permission only after you start them. Screen sharing always uses the browser's own source picker. Parsers analyze pasted SDP or ICE candidate text locally, and the Data Channel and statistics tools use local peer connections for repeatable browser-level diagnostics.
Connectivity checks are different because ICE, STUN and TURN are network protocols. The main WebRTC readiness test contacts a public STUN endpoint to gather candidates. The dedicated STUN test and TURN test contact the endpoint you enter. Those pages state what is sent and what a successful result can establish.
Privacy and responsible measurement
WebRTCTest is built to minimize collection. Media previews stay in the browser and the project does not intentionally upload camera or microphone streams. Diagnostic values such as SDP, device labels, TURN credentials and ICE addresses should not be included in analytics. The complete handling details, including the current Google Analytics 4 status, are documented in the Privacy Policy.
Accuracy, compatibility and changes
Browser behavior changes over time, and results may vary with operating-system permissions, extensions, VPNs, firewalls, hardware drivers and browser privacy features. WebRTCTest aims to describe those boundaries plainly and to improve tests when browsers evolve. Material product changes and methodology updates are recorded in the Changelog.
If you find an inaccurate result, an accessibility problem or a browser-specific failure, visit the Contact page. Reproducible reports help the project improve without requiring users to share sensitive diagnostic content.