CamMicGo is a practical troubleshooting toolkit, not a hardware certification laboratory. We distinguish the value a browser can observe from what it cannot verify. This page explains how to repeat a test and avoid drawing conclusions from a single score.
1. Webcam: delivered frames, not advertised specifications
How to reproduce it
Start the webcam test, keep the camera still for 20 seconds, then repeat under brighter lighting.
What the result means
The browser reports the negotiated video-track resolution; observed frame timing provides an estimate of delivered frames per second. Brightness and sharpness are estimates derived from local image samples.
What it does not prove
A 1080p track does not prove that the sensor captures native 1080p detail. Browser scheduling, autofocus, exposure and power saving can all affect the result.
Run the webcam test →2. Microphone: digital levels and repeatable recordings
How to reproduce it
Record ten seconds in a quiet room, then record the same phrase at the same distance after changing one setting.
What the result means
The waveform and RMS-based level describe the signal received by the browser. dBFS uses digital full scale as its reference; 0 dBFS is the digital ceiling.
What it does not prove
dBFS is not a calibrated sound-pressure measurement. Operating-system drivers, automatic gain and noise suppression can change the signal before it reaches the page.
Run the microphone test →3. Headphones: left/right routing and perceived sound
How to reproduce it
Set a comfortable low volume, check the left and right channels separately, and compare the same audio at the same volume.
What the result means
Browser playback can expose channel routing errors and audible differences, but the assessment depends on the listener and the playback chain.
What it does not prove
An online listening test cannot measure headphone frequency response or hearing thresholds without calibrated equipment. Stop if any tone feels uncomfortable.
Run the headphone test →4. Internet: latency and variable throughput
How to reproduce it
Run several measurements on the same network, with other downloads paused; compare Wi-Fi and wired connections when available.
What the result means
Timing and data transfer observations can indicate network responsiveness and throughput at the time of the test.
What it does not prove
Results depend on the test endpoint, congestion, browser and network path. A single run cannot establish a guaranteed connection speed.
Run the internet test →5. Screen: visible patterns, not laboratory calibration
How to reproduce it
Clean the display, disable adaptive brightness if appropriate, and inspect solid colours and gradients at a comfortable brightness.
What the result means
Full-screen patterns can help reveal stuck pixels, obvious banding or uneven areas. Browser APIs can report some display characteristics.
What it does not prove
Colour accuracy, actual luminance, response time and HDR performance require suitable instruments; browser estimates are not a certification.
Run the screen test →Privacy and reproducibility
Media capture requires your browser permission. CamMicGo's browser-based diagnostics process camera and microphone signals locally where the tool allows it. Some network tests necessarily communicate with a remote endpoint. Results can vary between Chrome, Safari, Firefox, Android, Windows and macOS because the APIs and hardware paths differ.
If a test gives an unexpected result, check the relevant technical documentation and troubleshooting guides before assuming the device is defective.
