System Hardware & Media Audit

Automated health inspection of your browser's media hardware APIs, user permissions, and connected peripheral devices.

Hardware Subsystem Overview
Client-side runtime query of WebRTC, Web Audio, and media capture APIs.
Media Capture (GUM) Ready
Querying...
navigator.mediaDevices.getUserMedia
Device Enumeration Ready
Querying...
navigator.mediaDevices.enumerateDevices
Web Audio Pipeline Ready
Querying...
AudioContext & AnalyserNode DSP
Media Encoder Ready
Querying...
MediaRecorder Opus / WebM
Connected Hardware Peripherals Scanning...
Querying hardware descriptors...

How the Hardware Subsystem Audit Works

1
Query APIs
The browser runtime checks for WebRTC media ingestion and DSP sound synthesis capabilities.
2
Enumerate devices
Queries hardware buses to count all active camera, microphone, and speaker peripherals.
3
Diagnose bottlenecks
Flags missing drivers, disabled browser flags, or restricted privacy sandboxes.

Common Subsystem Errors & Fixes

Error / Symptom Root Cause Recommended Solution
Media Capture API reports Fail Insecure HTTP origin or disabled WebRTC flags in browser settings. Access the website using HTTPS (or localhost) and ensure WebRTC is not blocked by third-party privacy extensions.
Device Enumeration returns 0 devices Missing or corrupt audio/video drivers in Windows Device Manager. Reinstall OEM motherboard audio drivers and webcam manufacturer drivers, then restart your browser.
Device names shown as generic labels Browser anti-fingerprinting protection active before permission grant. Click 'Test my webcam' or 'Test my microphone' to trigger the browser permission prompt and reveal exact model names.
Web Audio Pipeline reports Unsupported Outdated legacy browser or disabled audio engine policy. Update to the latest version of Chrome, Edge, Firefox, or Safari with Web Audio API 1.0 support enabled.

Browser Hardware Sandboxing & Security Isolation

Modern web browsers enforce strict security sandboxes to protect user privacy. Websites cannot silently access microphones, cameras, or biometric hardware without explicit permission prompts. The navigator.mediaDevices subsystem was standardized by the W3C to give users total control over their connected media peripherals.

HWCheck operates entirely within this sandboxed client runtime. No video frames, audio samples, or hardware serial numbers are ever collected, transmitted, or logged to remote servers. All diagnostic evaluations occur directly in your computer's local memory.

Explore Other Hardware Diagnostics

Frequently Asked Questions

What does this automated system audit check?
The audit inspects four critical browser subsystems: MediaDevices getUserMedia support, enumerateDevices hardware querying, the Web Audio DSP sound processing pipeline, and hardware MediaRecorder encoding.
Why do some device labels say 'Audio Device' or 'Camera' instead of the model name?
For security and anti-fingerprinting protection, modern browsers mask exact hardware model strings until you grant microphone or camera permission to the site.
Does the system audit transmit my device identifiers to a server?
No. All checks run 100% locally in your browser's JavaScript runtime. Zero device IDs, hashes, or technical specs are uploaded or logged.
What should I do if the Media Capture API reports Fail?
Ensure your browser is updated to the latest stable release and verify that the page is loaded over HTTPS or localhost, as WebRTC APIs require a secure origin.
Can this tool detect disconnected or disabled USB peripherals?
No. The browser can only query devices that are physically plugged in, powered on, and recognized by your operating system's device manager.
Which browsers support full media subsystem auditing?
All modern desktop and mobile browsers, including Google Chrome, Microsoft Edge, Mozilla Firefox, Apple Safari, Opera, and Brave.