Choose a test
Find the tool for the device you want to check.
Learn how to test your devices, understand the results, and troubleshoot common issues.
Find the tool for the device you want to check.
Follow the prompts; media tests start only when you choose their controls.
Review results with their limitations and repeat anything unexpected.
Inputest brings together browser tools for checking keyboards, mice, displays, microphones, speakers and webcams. It also includes reaction-time and click-speed tests. These tools help you observe input and output; they cannot certify that a device is fault-free.
Use a current browser, connect the device you want to check, and close applications that could compete for camera or microphone access. Start with one test, repeat a suspicious observation, and compare another browser or device before drawing a conclusion.
Open a tool from Browse Tools. Expand Mouse Test to find its individual checks, or use Guided Testing to visit the seven hardware-oriented tools in order.
Perform the requested key presses, clicks, movements or visual checks. Camera, microphone and speaker tests start only after you activate their controls.
Read the measured values alongside each tool’s limitations. Repeat unexpected results under similar conditions before changing hardware or system settings.
A registered key or click means the browser received an event. A missing event may be caused by the device, operating system, focus, permissions or browser restrictions. A warning is a reason to investigate, not a confirmed hardware failure.
Repeat measurements with the same browser, display, power mode and input device. Keep the tab active and reduce background load. Change one condition at a time so you can tell what affected the result.
Milliseconds describe time; lower reaction times are faster. Hz describes a rate per second; FPS describes video frames per second. CPS is clicks per second. Browser event rates and frame cadence should not be mistaken for direct hardware specifications.
Webcam Test requests camera access when you start it. Microphone Test requests audio access when you press Record. Allow only the device you intend to test. If access is blocked, use your browser’s site-permission controls and check the operating system’s privacy settings; the exact controls vary by browser and system.
The current webcam implementation displays a live stream and creates snapshots in the browser. Microphone recordings are assembled in the browser for playback and download. These capture paths do not upload media. This statement describes those features, not a blanket promise about all network activity or future versions of the site.
Use Stop Camera or Stop Recording and leave the tool when finished. Camera tracks are also released when the tab is hidden; returning does not restart the camera. Speaker playback stops when the tab is hidden or the page is left. Downloads remain wherever your browser saved them. Revoke camera or microphone permission in the browser’s site settings if you no longer want to allow access.
Check the connection, hardware mute switch, system input device and site permission. This tool uses the browser’s default audio input rather than an in-page device selector. Select the desired input in your system or browser, close competing apps, then retry Record.
Open testWait for the live preview to initialize, check the lens cover and lighting, and confirm the selected Camera Device. Close apps using the camera. Try Auto resolution if a requested mode fails; virtual cameras may expose different constraints from the physical webcam.
Open testClick outside search fields and controls, keep this page focused, and try the keys individually. Operating-system shortcuts, Fn keys and browser-reserved combinations may never reach the page. Compare a different keyboard or application before concluding that a switch has failed.
Open testUse Single Click Test and press deliberately once at a time. Compare the recorded intervals, then try Click & Hold Test without releasing the button. Check remapping software, accessibility settings, connection quality and a second device. A flagged short interval alone does not confirm switch damage.
Open testChoose a fixed expected direction and scroll only that way inside the test area. Reset before repeating. Intentional reversals, a touchpad, smooth-scrolling software or browser processing can create misleading results. Compare another application and inspect the mouse for dirt or wear if the pattern persists.
Open testKeep the tab visible, close heavy tasks and compare plugged-in and battery power modes. Check the system display setting and which monitor contains the browser. A repeatable browser rate can still differ from the display setting; it is not evidence by itself that the monitor is faulty.
Open testThe tools in this version are available without a payment or account flow. Open the catalog and choose a test.
No installation is required to use the website. Device drivers and operating-system settings can still affect which hardware your browser can access.
Camera and microphone capture require your approval. Speaker tests need a user action to start audio; fullscreen may also require a direct interaction. Other tools observe input events or render patterns without requesting camera or microphone access.
No. Browser tests cannot inspect every switch, sensor, connection, driver or physical component. Use repeatable observations to guide further checks, and consult the device manufacturer when a problem persists.
Focus, system load, power-saving modes, display timing, input latency, browser event processing and your own actions can all change the results. Repeat a test under comparable conditions.
The interface adapts to small screens. Useful tests depend on the phone’s hardware and browser APIs. A touchscreen cannot reproduce a physical mouse wheel or all keyboard events, and fullscreen or media features may be limited.
Support depends on each feature. Camera and microphone need media-capture APIs and a secure context, while recording, fullscreen and video-frame callbacks have their own availability checks. Try an up-to-date browser if a tool reports that a feature is unavailable; there is no guarantee that every feature works on every browser or device.
No. Interface language and the keyboard’s form factor, ANSI/ISO geometry and US/Finnish keycap layout are separate settings. Choose the layout that matches your physical keyboard inside Keyboard Test.