Keyboard Tester Not Detecting Keys? What to Check First
If an online keyboard tester does not detect one key, several keys, or modifier combinations, start with focus, layout, browser shortcuts, rollover limits, and hardware checks.
Record a screen, window, or browser tab locally with supported desktop browsers, then download the result as a WebM file.
Capture your screen directly in the browser using the Screen Capture API. Download recordings as WebM video files.
Modern browsers support screen capture through the Screen Capture API, which provides the getDisplayMedia() method. This allows web applications to request permission to record the user's screen, a specific application window, or a browser tab — all without requiring any software installation.
The MediaRecorder API compresses the captured stream in real time using VP9 video encoding and Opus audio encoding, producing WebM files that are smaller and of comparable quality to H.264 MP4 for typical screen content. All processing is local — no data leaves your browser.
Click the Start Recording button. Your browser will show a permission dialog to choose what to share.
Select your entire screen, a specific window, or a single browser tab. Optionally include audio.
Click Stop Recording or use the browser's "Stop sharing" button. Then click Download WebM to save the file.
More free tools to check your setup.
Test your webcam or camera. Check live preview, resolution, frame rate, permissions, and image quality.
Estimate webcam frame-update rate delivered to your browser. View the live feed with resolution and device info.
Check your monitor for dead pixels, stuck pixels, and screen uniformity with a full-screen color test.
Measure browser animation-frame timing over 10 seconds using requestAnimationFrame. See average, min, and max FPS with a live bar chart.
Check backlight bleed, IPS glow, dirty screen effect, clouding, and color tinting with full-screen solid colors.
Learn about screen recording, video capture, and browser media APIs.
If an online keyboard tester does not detect one key, several keys, or modifier combinations, start with focus, layout, browser shortcuts, rollover limits, and hardware checks.
A browser GPU stress test can reveal crashes, throttling, noisy fans, and WebGL issues, but it cannot replace tools that read sensors, VRAM errors, or driver-level stability.
If a refresh rate test reports 60Hz on a 144Hz or 240Hz monitor, check OS settings, cable limits, browser throttling, VRR, duplicated displays, and power mode.
Mouse polling rate tests can jump between values because of movement speed, DPI, browser event delivery, wireless mode, CPU load, and USB power settings.
If a browser gamepad tester does not detect an Xbox, PlayStation, Switch, or generic controller, check connection mode, browser support, focus, permissions, and Steam input.
If an online microphone test cannot hear you, check browser permissions, the selected input device, OS privacy settings, exclusive mode, Bluetooth headset profiles, and HTTPS.