How We Test

Browser-first by design

Every core tool is a static page with a small amount of client JavaScript that calls browser APIs such as getUserMedia, the Web Audio API, keyboard and pointer events, and capability signals from navigator and screen. There is no DeviceHub desktop installer for these checks.

What we verify

• Whether the browser can open the requested device or report capability signals
• Permission state (allowed, blocked, or not required)
• Live feedback such as camera preview, mic levels, key highlights, or tone playback
• Basic device labels and settings the browser exposes after permission

What we do not claim

Results are session-based and limited by browser privacy rules. DeviceHub is not a substitute for manufacturer diagnostics, driver utilities, or professional hardware repair. A pass on this site means the browser could exercise the device in this tab — not that every app on your OS will behave the same way.

Privacy during tests

Camera and microphone streams are processed locally for the active test whenever APIs allow. See our Privacy Policy and Cookie Policy for analytics and advertising details.

Editorial standards

Tool copy, FAQs, and troubleshooting tips follow our Editorial Policy. Methodology questions: Contact us.