Device Test Tools
Use these device test tools to check common hardware inputs and displays quickly in your browser.
-
Microphone Test
Check your microphone input and permissions
-
Camera Test
Verify your camera works in the browser
-
LCD Test
Inspect LCD panels for display issues
-
Keyboard Test
Test keyboard input and key response
If you already know which part is acting up, route by the signal you need to confirm and skip the rest of the hub: a video preview that should show a live image points to the Camera Test, audio input the browser may be muting points to the Microphone Test, key registration after a spill or a repair points to the Keyboard Test, and a stuck pixel or patch of uneven backlight points to the LCD Test. Each opens on its own page above and runs in the browser, so you check the one part you came for and move on.
Check your hardware before it matters
Device test tools help you verify that your hardware is working before a meeting, recording, or troubleshooting session. A quick camera test can save a video call, and a microphone check can confirm that permissions are set correctly. These tests run in the browser, so you can validate devices on any computer without installing software or drivers.
Whether you are preparing for a remote interview or diagnosing a hardware issue, these tools give you immediate feedback. You can confirm that a camera is active, check microphone input levels, verify keyboard responsiveness, and inspect screen quality. Simple diagnostics like these can prevent small problems from turning into bigger disruptions.
Modern browsers require permission before they can access cameras or microphones. If you do not see any signal, check the permission prompt in the address bar and confirm the correct device is selected. Many laptops also have hardware privacy switches, so make sure those are enabled before testing. Running a quick test now can help you avoid last-minute surprises later.
If you are setting up a new device, it is worth testing each input once so you know what is working. A camera test can reveal resolution limits, while an LCD test can show stuck pixels or uneven color. These checks give you confidence before you begin critical work like remote presentations or recordings.
Common device test workflows
- Video call readiness: Confirm camera and microphone access before joining a meeting.
- Hardware troubleshooting: Diagnose faulty keys, screen defects, or microphone issues.
- New device setup: Validate that a new laptop or webcam works as expected.
A Windows update or a driver upgrade can quietly break a device that worked the day before: the update sometimes resets the default microphone or camera, or revokes the browser permission the test depends on. After any major system update, open the test for the input you rely on and confirm the signal is back - catching a reset device early beats discovering it the moment someone joins the call.
For a step-by-step walkthrough of the screen check on its own, read the LCD Screen Test guide.
Tips for accurate results
Close other apps that might be using the camera or microphone so the browser can access the device. If you are testing audio, try speaking at a normal volume and watch for consistent input levels. For camera tests, check lighting conditions so you get a true sense of image quality. When testing a keyboard, press each key once to confirm that the input registers reliably.
Screen checks work best at full brightness, and you should look for color consistency across the display. If you find a hardware issue, try a different USB port or device to isolate the problem. These tools do not store any recordings; they are used only for the live test and then discarded.
Quick comparison
| Tool | Best for | What you verify | Common fix |
|---|---|---|---|
| Camera Test | Webcam preview | Video signal + device selection | Allow permission / switch camera |
| Microphone Test | Audio readiness | Input levels + mic selection | Select correct mic / unmute |
| Keyboard Test | Key checker | Key presses + special keys | Toggle Num Lock / clean key |
| LCD Test | Screen check | Stuck pixels + color uniformity | Increase brightness / full-screen |
Troubleshooting checklist
Most device-test failures resolve with one of the steps below. Work through them top-to-bottom.
The cause is far more often a permission state than a hardware fault, so this checklist walks through the five permission layers that almost always own the failure: browser site-permission, an HTTPS origin, the OS privacy panel, another program holding the device, and the user-gesture rule on phones.
- Browser permission. These tools use the
getUserMediaandPermissionsAPIs. Click the camera/microphone icon in the address bar and re-grant access; on Chrome, Site settings → Camera / Microphone must be set to Allow forfreetoolonline.com. - Secure origin. Modern browsers only expose camera, mic, and sensor APIs over HTTPS. If you opened the page over plain HTTP, reload with
https://. - OS-level privacy. macOS: System Settings → Privacy & Security → Camera / Microphone and enable your browser. Windows: Settings → Privacy & security → Camera & Microphone. Linux: ensure
pipewireorpulseaudiois running and the user has device access. - Device in use elsewhere. Quit other apps that may hold the webcam or mic (Zoom, Teams, OBS). On Windows the Camera app often keeps an exclusive lock.
- Mobile sensor quirks. iOS Safari requires a user gesture (a tap) before the first sensor read, and it blocks motion sensors when the page is inside a cross-origin iframe. Android Chrome needs the page added to the home screen for some hardware-backed flags.
Scope disclosure. A browser-based test reflects what the browser can see through Web APIs. If every browser on the machine reports a failure, the fault is usually the hardware, driver, or OS permission layer - follow up with your OS's own diagnostic tool.
Browser-based camera test - no install required
The browser-based camera test confirms video signal, device selection, and permission grant in a single tab - open it, click Start Camera, and a live preview appears once the browser receives permission. For the camera specifically, the browser-side check surfaces the three failures that derail most video calls before the call begins - another app holding the device handle, a stale browser permission deny, or the wrong camera selected from the OS list.
If the piece you need to check is a sticking or dead key after a spill, a hinge repair, or a refurb arrival, the key-registration check is the page to land on directly: press each physical key and watch the matching key light up on screen as the browser receives the keydown event, so you can tell a truly unresponsive key from one that is just slow. It registers modifiers, function keys, and the numeric pad too, with nothing to install - so a reader who already knows the keyboard is the suspect skips the rest of the hub and goes straight to the page that proves it.
Pair device tests with media-production tools
The four device tests on this hub sit upstream of any recording or video-call workflow, so they pair naturally with the media-production tools elsewhere on the site. If your camera and mic check out and you are about to capture clips, you may also need to convert a video file between codecs the editor expects, extract GIF frames for thumbnail-quality stills, or prepare HEIC photos from your phone for tools that do not yet accept the iPhone-default format - all live in the image converter hub and video tools hub. If your remote-work setup needs to share the captured material after the call, the zip tools hub bundles folders into a single archive in the browser. Developers troubleshooting the underlying browser APIs on a new machine can cross-reference the developer tools hub for JSON parsing, CSS/JS minification, and MD5 conversion against the responses returned by their own service.
Want a broader check? The site map covers every device test plus related guides, including the remote-work checklist.
Laptop, phone, and shared-machine checks
The laptop's built-in webcam is the piece most laptop owners check first - before a video call, or before a return window closes on a new machine - and the camera check described earlier on this page confirms it in one tab: allow the permission prompt, watch for a live preview from the built-in lens, and switch to an external USB camera from the device list if the built-in one stays black.
A phone or smart-TV display can be checked the same way: open the full-screen color test directly in that device's own browser and step through the red, green, blue, black, and white frames to spot a dead or stuck pixel before you commit to keeping a new phone or television.
Related guides
Background reading on what each test catches and when to run one:
What an LCD test does (and when to run one)
Dead pixels, stuck pixels, backlight bleed, banding - what the four-color sweep catches, and the five times the two-minute test is worth running.
Dead pixel testing guide
How to tell a dead pixel from a stuck one, the ISO 9241 thresholds most warranties use, and the patterns to step through to be sure.
Device test checklist for remote work
A pre-meeting routine that checks camera, microphone, screen, and keyboard in under five minutes - so issues surface before the call, not during it.
How to test for dead pixels before returning a monitor
A timed routine for the return window: what to capture as proof, what counts as "defective" by warranty, and when a partial refund is the better path.
Why trust these tools
- Ten-plus years of web tooling. The freetoolonline editorial team has shipped browser-based utilities since 2015. The goal has never changed: get you to a working output fast, without an install.
- No install, no sign-up. Open a tool and get a working output in seconds - nothing to download and no account to create. Tools that need heavy processing run it on our service, so even a low-powered machine gets the job done.
- Analytics stops at the page view. We measure which pages get visited, not what you type or upload inside a tool. There is nothing to sign in to and no profile is attached to your input.
- Open-source core components. The processing engines underneath (libheif, libde265, pdf-lib, terser, clean-css, ffmpeg.wasm, and others) are public and audit-able. We link to each one in its tool page's footer.
- Free, with or without ads. All tools are fully functional without sign-up. The Disable Ads button in the header is always available if you need a distraction-free run.
Frequently Asked Questions
Which device test should I run before joining a video call?
Run Camera Test and Microphone Test in that order. The camera test confirms the right webcam is selected and shows a live preview; the microphone test verifies input levels and the correct mic is routed. Both run in under a minute.
The tool shows no signal - what's wrong?
Nine times out of ten, it is a permission issue. Click the camera or microphone icon in the address bar and re-allow access for freetoolonline.com. Then confirm your OS (macOS System Settings → Privacy, Windows Settings → Camera/Microphone) has granted your browser access.
Are recordings stored anywhere?
No. These tests run in your browser only. Nothing is uploaded, nothing is recorded, and the live preview ends the moment you close the tab.
Do these tests work on a phone or tablet?
Mostly yes - the camera, microphone, and screen tests work in mobile Chrome and Safari over HTTPS. A few sensor APIs (accelerometer, orientation) need a user gesture first on iOS, and some Android devices hide extra cameras from the browser. Desktop remains the most reliable environment.
What if every browser fails the same test?
When Chrome, Firefox, and Safari all fail the same sensor, the fault is usually the hardware, driver, or OS permission layer - not the browser. Try the OS's built-in camera or sound-settings diagnostic before assuming the hardware is broken.