Performance & device · browser-local
Use five private browser tools for screen recording, typing speed, CPS, reaction time, and camera or microphone diagnostics. No upload or account.
Work happens in the current browser. The route does not require an account or a server-side processing job.
Choose a task below. Each tool explains what to choose and what you get.
What it does
Browser compatibility
A modern JavaScript-enabled browser; media-capture routes require HTTPS or localhost and explicit permission.
Questions people ask
No. The tools report what the browser observes and explicitly avoid medical, anti-cheat, hardware-latency, or identity-verification claims.
Screen Recorder uses the browser-controlled display picker and can optionally request microphone or camera access. Camera & Microphone Test requests only the devices you enable.
Display refresh, input hardware, browser scheduling, operating-system behavior, and permissions can all affect interactive measurements and media capture.
Use these browser-based checks for local typing, reaction, capture, camera, microphone, keyboard, or screen observations when you want to understand the current session. The tools request only the permission or interaction their workflow needs and report local results. Hardware, display, scheduling, permissions, and background activity can change the outcome, so it is not a professional or device certification.
| Need | Focused route | Why it matches |
|---|---|---|
| Measure a timed typing sample with accuracy. | Typing speed test | The typing test owns WPM, error and consistency calculations. |
| Compare visual reaction trials and false starts. | Reaction time test | The reaction route reports a session distribution under visible browser conditions. |
| Inspect camera, microphone and a short local sample. | Test your camera, webcam, and microphone online | The camera and microphone route exposes permissions, negotiated facts and playback review. |
Use five private browser tools for screen recording, typing speed, CPS, reaction time, and camera or microphone diagnostics. No upload or account.
Choose a focused browser-local input, reaction, capture, camera, or microphone test.
Next step: Choose a related route when the input, output, or required workflow is different.
Selected file bytes and entered browser data remain in the current browser session and are not sent to an Aftermath processing service. How local processing is verified.
Checks the displayed limits and reports or creates a local measurement or test report from keyboard, pointer, timing, or explicit device permission.
A local measurement or export does not guarantee acceptance by an external destination.
