Browser Hardware Checkers
Device Tests
Choose a focused device test for microphone input, webcam preview, controller buttons, keyboard keys, mouse buttons, or input timing.
All tools run in the browser and are built for quick checks before calls, games, streams, recordings, or desk setup changes.
Input & Hardware
Pick the device you want to check.
These pages target direct search intent: open the test, grant permission if needed, and confirm whether the browser receives input.
Check mic permission, live level, peak input, and local browser detection.
Webcam TestPreview camera video, inspect resolution and framing, fix permission issues, and capture a local snapshot.
Gamepad TesterCheck controller buttons, analog sticks, axes, triggers, and drift symptoms.
Keyboard TestPress keys to confirm browser key detection, key names, and key codes.
Keyboard Polling Rate TestEstimate keyboard Hz, input interval, peak rate, and consistency.
Mouse TestCheck left, middle, right, double-click, wheel, and pointer movement.
Double Click TestCheck browser double-click events and possible unwanted mouse double-clicking.
Click Speed TestMeasure click speed and clicks per second with 5s, 10s, and 30s modes.
Which device test should I use?
Use the microphone test before recording or joining a call, the webcam test before streaming or meetings, and the gamepad tester before playing with a controller. Keyboard and mouse tests are useful after changing devices, layouts, switches, USB hubs, or browser settings.
Why does a device test need permission?
Browsers require explicit permission for microphone and camera access. If a test is blocked, check the browser prompt, operating system privacy settings, and whether another app is already using the device.
Camera and microphone blocked checklist
If camera or mic access is blocked, open the browser site settings for quicktesthub.com, allow the camera or microphone, reload the page, and check macOS or Windows privacy settings. Close Zoom, Meet, Teams, recording software, or other apps that may already be using the same device.
How to troubleshoot a failed device test
Start with the browser permission icon near the address bar, then check operating system privacy settings, input/output device selection, and whether another app is already using the same hardware. For USB devices, reconnect the cable or try a different port before assuming the hardware is broken.
Browser tests vs installed diagnostic apps
Browser device tests are best for quick confirmation that a website can receive your microphone, camera, keyboard, mouse, or controller input. Installed diagnostic apps may expose deeper driver details, but they are slower to set up. Use this hub first when you need a fast answer before a meeting, stream, game, recording, or support call.
Device Tests FAQ
Are these tests private?
The tests run locally in your browser. Microphone and camera pages request permission only so the browser can preview input on the page.
Why does my device work in one browser but not another?
Browser permissions, hardware API support, extensions, and operating system privacy settings can differ. Try Chrome or Edge when testing gamepads or media devices.
What should I test before a call or stream?
Run the microphone test, webcam test, and keyboard or mouse test if you recently changed devices, hubs, cables, drivers, or privacy settings.