Unavailable
Secure context
WebRTC Camera, Microphone & Call Test
Permission-first browser diagnosticsTest camera, microphone, screen sharing and local WebRTC quality before a call.
Media starts only after your click
Previews and peer loopback stay in this tab. No signaling server, upload or background permission request is used.
Unavailable
MediaDevices
Unavailable
Camera and microphone
Unavailable
Screen capture
Unavailable
RTCPeerConnection
Unavailable
Device enumeration
Unavailable
Web Audio meter
Permission state
Some browsers do not expose camera or microphone state until requested.
Cameraprompt
Microphoneprompt
Device classes
Labels usually appear only after permission is granted.
0Cameras
0Mics
0Outputs
Preflight path
Test the media pipeline, then start an in-browser peer connection.
How to use it
- 01
Check browser readiness
Review secure-context APIs, permissions and enumerated device classes without requesting media automatically.
- 02
Test media deliberately
On your click, preview requested camera, microphone and display tracks with actual negotiated settings.
- 03
Measure a local call
Run a synthetic or device loopback, inspect standardized WebRTC stats and export a redacted report.
Frequently asked questions
Does opening the page start my camera?
No. Camera, microphone and display prompts occur only after the corresponding test button is clicked.
Does loopback measure my internet connection?
No. The built-in peers communicate inside this browser, so results validate the browser media pipeline rather than a remote TURN server or conference service.
What do the quality labels mean?
They are transparent triage thresholds over observed loss, RTT and jitter, not a guarantee of application call quality.
Is identifying network data exported?
Reports omit candidate addresses and redact recognizable IP addresses and long identifiers from events and settings.
Related tools
Keep working with other focused browser utilities.