RunTheTests
/

Device tools

73 tools that run in your browser. Nothing to install, nothing uploaded.

Browser-based device tests for the things you can actually check from a web page — your camera, your screen, your input devices. These are honest about their limits: a browser cannot read your hardware’s internal health, temperature or firmware, so where a native tool would be more authoritative, these say so. What they are good at is the interactive checks a chatbot cannot do for you — a webcam only tests by showing you a live image, a mouse switch only reveals a fault by how it clicks.

What a browser can genuinely test, and what it cannot

A web page gets whatever your operating system hands the browser, and nothing else. That is a real set of things: the live image from your camera, the audio from your microphone, every key and button event, pointer movement, gamepad axes, screen resolution, refresh timing and the frame rate a page is actually presented at. It is also a hard boundary. There is no route from JavaScript to CPU temperature, fan speed, SMART attributes, RAM integrity, battery wear level or the internal health of a display panel, so a browser tool that reports those is inferring or inventing them. Every test here states its own limits with its result rather than in the small print.

Why interactive tests are the ones worth running here

The tests that survive in a browser are the ones that need a human in the loop. Nobody can tell you from a description whether your webcam is focused, whether your microphone is picking up a hum, whether a mouse switch is double-firing, or whether a patch of your screen is a dead pixel or a speck of dust — you have to look, listen and click. That is also why these are the checks a chatbot cannot do for you and a spec sheet cannot answer. The measurement side handles what eyes and ears are bad at: drift as a number in millimetres of stick travel, dropouts as a count, latency in milliseconds, jitter between consecutive frames.

Testing a device you are about to buy or sell

A used laptop, phone, controller or monitor can be checked in about ten minutes from a browser, which is usually all the time you get. Work through the parts that are expensive to repair and easy to hide: run the dead pixel test on a fullscreen white and a fullscreen black, exercise every key including the modifiers, click each mouse or controller button several times looking for a double-fire, push both sticks to the rim and watch for a centre that does not return, and open the camera and microphone tests to confirm they enumerate at all. A device that fails any of these in the shop is a device whose price you now have a reason to argue about.

Reading a result that says “inconclusive”

Several of these tests can return a strong negative and only a weak positive, and they say so rather than rounding up. A double-click test that catches a stray second click has proved a failing switch; twenty clean clicks have not proved the switch is healthy, only that it did not misfire during the sample. A refresh rate test measures what your browser was allowed to present, which a power-saving mode or a background tab can cap well below the panel’s capability. Treat a pass as “no fault visible under these conditions”, and repeat anything marginal — on battery and on mains, in a foreground window, and after a reboot.

Frequently asked questions

Can a browser check my CPU temperature, RAM or drive health?

No, and any site that offers to is guessing. The browser is sandboxed away from hardware sensors, SMART attributes and memory addresses by design — there is no web API that exposes them. For those you need a native tool: your operating system’s own health reporting, or something like smartctl for drives. Several tools in the Interpreter category exist to read that output once you have it.

Why does a test ask for camera or microphone permission?

Because there is no way to test a device without opening it. The browser will not hand any page a camera or microphone stream without your explicit consent, and the permission is scoped to this site and revocable from the padlock icon at any time. The stream is rendered locally and never recorded or transmitted — you can watch the network panel stay quiet while the test runs, and closing the tab ends the access.

My hardware passed here but still misbehaves in a game or a call. Why?

A browser test measures the device as the browser is allowed to see it, which is often a best case. Games use exclusive full-screen modes and different input paths, conferencing apps apply their own processing, and both compete for resources a quiet test page does not. A pass means the hardware enumerated and responded correctly here; it does not clear the driver, the application, or the system under real load.

How reliable are these for checking a second-hand device?

Very good for the faults that are visible or interactive — dead pixels, dead keys, double-clicking switches, stick drift, a camera or microphone that does not enumerate — and no use at all for internal wear such as battery chemistry or drive hours. Use them as the ten-minute screening pass that catches the obvious problems in front of the seller, and treat anything about internal condition as still unverified.