Keyboard Test
The Keyboard Test is a comprehensive keyboard diagnostic tool that detects and displays information about physical and virtual key…
Keyboard Test Area
Click in the box below and start typing to test your keyboard. Press any key to see its details.
Last Key Pressed
Test Results
Recent Key Presses
Virtual Keyboard Test
Click the keys below to simulate key presses:
About Keyboard Test
Key detection: Test all keyboard keys and see their codes, Unicode values, and modifier states.
Virtual keyboard: Click virtual keys to simulate key presses without a physical keyboard.
Statistics: Track total keys pressed, unique keys, modifiers, and special keys.
Key history: View a log of recent key presses with timestamps.
Related tools
More from the same category
DNS Lookup
Look up DNS records for a domain (A, MX, TXT, and more).
HTML Table Generator
Generate an HTML table with rows and columns.
HTTP Headers Viewer
View HTTP response headers.
Internet Speed Test
Test your internet connection speed.
IP Address Lookup
Look up geolocation and info for an IP address.
Password Strength Test
Test password strength and security.
Learn more — open a section when you need details
The Keyboard Test is a comprehensive keyboard diagnostic tool that detects and displays information about physical and virtual key presses in real time, showing detailed key information including key names (character representation), key codes (browser-specific numeric codes), Unicode values (character encoding values), and active modifier keys (Ctrl, Alt, Shift, Meta/Command). It maintains a log of recent key presses for review, tallies comprehensive statistics including total key presses, unique keys pressed, modifier key usage, and special key counts (function keys, navigation keys, etc.), and offers an on-screen virtual keyboard interface to simulate key input for testing purposes. The tool processes all keyboard detection entirely locally in your browser, ensuring privacy and fast performance without server uploads. This is helpful for diagnosing stuck keys, identifying keyboard layout issues, validating keyboard shortcuts and key combinations, troubleshooting input problems across different browsers and operating systems, testing international keyboard layouts and IME (Input Method Editor) behavior, and documenting key mappings for support tickets—all without installing additional software, making it an essential tool for keyboard troubleshooting, development, and accessibility testing.
-
1
Click or focus the text input area in the keyboard test interface to activate keyboard event detection, then press keys on your physical keyboard (or use virtual keyboard buttons), as keyboard events only register when input field has focus requiring explicit focus activation before keyboard testing begins.
-
2
Watch the real-time display panels update live showing Key name (character or key identifier), Key Code (browser-specific numeric code), Unicode value (character encoding), and active Modifiers (Ctrl, Alt, Shift, Meta/Command status) for each key press, as live display provides immediate feedback on keyboard input enabling real-time keyboard testing and key detection verification.
-
3
Check "Test Results" or statistics panel displaying totals including total key presses, unique keys detected, modifier key usage counts, and special key statistics, and review "Key History" panel showing recent key presses in chronological order for comprehensive keyboard activity analysis and key press review.
-
4
Use the Virtual Keyboard buttons on the on-screen keyboard interface to simulate specific key presses without physical keyboard, enabling keyboard testing when physical keyboard is unavailable or for isolating keyboard input issues requiring virtual keyboard simulation for comprehensive keyboard testing.
-
5
Press keyboard shortcuts (Ctrl+C, Alt+Tab, Shift+Click combinations, etc.) to test modifier key combinations and shortcut detection, observing how modifier keys affect key detection and shortcut registration for keyboard shortcut validation and modifier key testing purposes.
-
6
Test international keyboard layouts by switching OS keyboard layout and pressing keys to verify layout-specific key detection and character output, enabling international keyboard testing and layout validation for multi-language keyboard support and international keyboard layout verification.
-
7
Click "Reset Test" or "Clear" button to clear all statistics and key history when finished testing or starting new test session, as reset functionality enables fresh testing sessions and statistics clearing for clean keyboard testing workflow requiring reset capability for multiple test iterations.
-
8
Review keyboard test results and statistics to identify patterns, stuck keys, missing key detections, or keyboard issues, then document key mappings, key codes, or keyboard problems for support tickets or troubleshooting reports requiring comprehensive keyboard testing documentation and issue identification.
Keyboard hardware troubleshooting and stuck key detection
Verify if certain keys repeat, fail to register, or report incorrect key codes indicating hardware problems, enabling keyboard hardware diagnostics and troubleshooting requiring keyboard testing to identify stuck keys, failing keys, or keyboard hardware malfunctions for keyboard repair or replacement decisions.
Keyboard shortcut validation and development
Confirm detection of Ctrl/Alt/Shift/Meta key combinations and keyboard shortcuts for application development, enabling keyboard shortcut testing and validation requiring modifier key combination detection to ensure keyboard shortcuts work correctly in applications and web interfaces.
International keyboard layout testing
Check non-US keyboard layouts (AZERTY, QWERTZ, international layouts) and IME (Input Method Editor) behavior for special characters, enabling international keyboard support testing and layout validation requiring keyboard layout testing to ensure applications work correctly with different keyboard layouts and input methods.
Kiosk and QA testing documentation
Document key mappings, key codes, and keyboard behavior for support tickets, QA reports, or technical documentation, enabling keyboard testing documentation and issue reporting requiring detailed keyboard information for troubleshooting and support workflows.
Accessibility input device testing
Ensure switch devices, remapped keys, or alternative input devices trigger expected keyboard events correctly, enabling accessibility testing and assistive device validation requiring keyboard event verification to ensure accessibility input devices work properly with applications and assistive technologies.
Browser compatibility and cross-platform keyboard testing
Test keyboard behavior across different browsers (Chrome, Firefox, Safari, Edge) and operating systems to identify browser-specific keyboard differences, enabling cross-browser keyboard compatibility testing requiring keyboard testing across platforms to ensure consistent keyboard behavior in all target browsers.
Development and debugging keyboard input
Debug keyboard input issues in web applications, verify keyboard event handling, or test keyboard-based interactions during development, enabling development debugging and keyboard input validation requiring keyboard testing for application development and keyboard event debugging workflows.
Educational and training keyboard awareness
Demonstrate keyboard functionality, key codes, and keyboard behavior for educational purposes or training sessions, enabling keyboard education and awareness requiring keyboard testing demonstrations for teaching keyboard concepts and keyboard input understanding.
Test keyboard in multiple browsers (Chrome, Firefox, Safari, Edge) as key codes can vary by browser engine, as different browsers use different key code systems causing browser-specific keyboard differences requiring cross-browser testing to ensure keyboard functionality works consistently across all target browsers and browser engines.
Disable browser extensions that intercept keyboard input (password managers, hotkey tools, accessibility software) while testing to eliminate interference, as extensions may intercept or modify keyboard events causing false test results or missed key presses requiring clean browser profile or private browsing mode for accurate keyboard testing.
Try both hardware physical keyboard and virtual on-screen keyboard buttons to isolate device issues, as comparing physical vs virtual keyboard results helps identify whether problems are hardware-related (physical keyboard) or software-related (browser/OS) requiring dual keyboard testing for comprehensive keyboard troubleshooting and issue isolation.
If a key does not register, check OS accessibility filters, input method settings, and keyboard layout configurations, as OS-level keyboard settings may block or modify keyboard input causing missed key presses requiring OS accessibility and input method configuration review for complete keyboard testing and issue resolution.
Use a clean browser profile or private/incognito window to reduce interference from browser extensions, saved settings, or installed add-ons, as browser profile settings may affect keyboard event handling requiring clean testing environment for accurate keyboard testing results and elimination of external interference factors.
Focus the input area explicitly before testing keys to ensure keyboard events are captured, as keyboard events only fire when input element has focus causing missed key presses if input area isn't focused requiring explicit focus activation before keyboard testing to ensure all keyboard events are properly detected and logged.
Test modifier key combinations (Ctrl, Alt, Shift, Meta) individually and in combination to verify modifier detection, as modifier keys affect keyboard event properties requiring comprehensive modifier key testing to ensure keyboard shortcuts and modifier combinations work correctly in applications and web interfaces.
Review key history log and statistics to identify patterns or anomalies in keyboard behavior, as pattern analysis helps identify stuck keys, missing key detections, or keyboard issues requiring thorough review of keyboard test results for comprehensive keyboard diagnostics and problem identification.
Confusing keyCode values with actual character output causing misinterpretation of key detection, when keyCode values are browser-specific numeric codes that may differ between browsers and don't directly correspond to character output, causing confusion about key detection accuracy and requiring understanding that Unicode values are more stable across browsers while keyCode varies by browser engine and may not match character representation.
Testing keyboard keys without proper focus on the input area causing events not to fire, when keyboard events only trigger when input field or text area has focus, causing missed key presses, incomplete testing, or false negative results requiring explicit focus on input area before testing keys to ensure keyboard events are properly captured and logged during keyboard testing.
Ignoring modifier key state (Ctrl, Alt, Shift, Meta) when testing keyboard shortcuts causing incomplete shortcut validation, when keyboard shortcuts rely on precise modifier detection and modifier state affects key combinations, causing shortcut testing failures and requiring attention to modifier state display to ensure keyboard shortcuts are tested with correct modifier combinations for accurate shortcut validation.
Concluding hardware keyboard failure before testing in another browser or operating system causing incorrect diagnosis, when key detection issues may be browser-specific, OS-specific, or driver-related rather than hardware failure, causing unnecessary hardware replacement and requiring cross-browser and cross-platform testing to isolate whether issues are hardware, software, browser, or OS-related before concluding keyboard hardware problems.
Overlooking IME (Input Method Editor) and keyboard layout differences that change produced characters causing international keyboard testing failures, when different keyboard layouts (QWERTY, AZERTY, international) or IME systems produce different characters for same physical keys, causing confusion about key detection and requiring understanding that key codes may remain similar but character output varies by layout and IME settings affecting keyboard testing accuracy.
Not disabling browser extensions or hotkey managers during testing causing interference with key detection, when browser extensions (password managers, hotkey tools, accessibility software) may intercept or modify keyboard events, causing false test results or missed key presses and requiring clean browser profile, extension disabling, or private browsing mode to eliminate interference during keyboard testing.
Assuming all keys work identically across browsers without cross-browser validation causing compatibility issues, when browser keyboard event handling differs (keyCode, code, key properties vary), causing browser-specific keyboard issues to go undetected and requiring testing across multiple browsers (Chrome, Firefox, Safari, Edge) to ensure keyboard functionality works consistently across all target browsers.
Not testing special keys (function keys, media keys, navigation keys) assuming they work automatically causing incomplete keyboard validation, when special keys may require different handling, have OS-level behavior, or may not be detectable in browser context, causing missed keyboard functionality issues and requiring explicit special key testing to verify all keyboard features work correctly.
Expecting keyboard test tool to fix keyboard problems when it only diagnoses issues, when tool provides diagnostic information but doesn't repair hardware, driver, or system issues, causing misunderstanding of tool capabilities and requiring separate troubleshooting steps (driver updates, OS settings, hardware repair) to actually fix detected keyboard problems beyond diagnostic information.
Not reviewing key history or statistics during testing missing patterns or issues, when key history reveals stuck keys, repeated presses, or modifier state problems that aren't immediately obvious, causing missed keyboard issues and requiring review of key history, statistics, and test results to identify keyboard problems, patterns, or anomalies during comprehensive keyboard testing.
Testing keyboard in environments with accessibility filters or input method restrictions causing incomplete testing, when OS-level accessibility settings, input method restrictions, or security policies may block or modify keyboard events, causing incomplete test results and requiring testing in clean environments or understanding how OS settings affect keyboard event detection and reporting.
Not preserving test results or key history before resetting causing loss of diagnostic information, when test results, key history, or statistics may be needed for troubleshooting, support tickets, or documentation, causing loss of valuable diagnostic data and requiring screenshot capture, copying test results, or exporting key history before resetting test to preserve diagnostic information for analysis or support purposes.
Key code implementations vary by browser engine—Chrome, Firefox, Safari, and Edge may report different keyCode values for the same physical key. Unicode values are more stable across browsers, but keyCode and code properties can differ. This is normal browser behavior, not a bug. Test in multiple browsers to verify consistent key detection across your target browser environments.
Yes, most browsers report function keys and media keys. F1-F12 typically work in browser context. Media keys (play, pause, volume) may be handled at OS level rather than browser level, so some media keys may not generate browser events. Function keys usually work, but test in your specific browser to confirm media key detection based on your browser and OS combination.
No, everything runs entirely in your web browser using JavaScript keyboard event APIs. No software installation, browser extensions, or downloads are required. Simply open the tool in your browser and start testing keys immediately. The tool works offline once the page is loaded, requiring no internet connection during testing.
Hold modifier keys (Ctrl, Alt, Shift, Meta/Command) while pressing another key. The Modifiers panel shows which modifiers are active. Watch the Modifiers display to confirm all pressed modifiers are detected. For example, hold Ctrl and press C to test Ctrl+C—both Ctrl modifier and C key should register in the key history.
No, all keyboard testing happens entirely locally in your browser using client-side JavaScript. Key presses, key codes, and test data never leave your device and are not transmitted to servers. Your keystrokes remain completely private and secure during testing, making this tool safe for testing sensitive or confidential keyboard input.
Yes, IME systems work with this tool. Composed characters (from IME input methods for languages like Chinese, Japanese, Korean) appear in the character output, and keyboard events still register. The tool detects both direct key presses and IME-composed characters, making it suitable for testing international keyboard input methods and non-Latin character input.
The tool displays space characters as [Space] label in the key history for clarity and readability, since actual space characters would be invisible and difficult to identify in the history list. The key press is still detected and logged correctly—the [Space] label is just a visual representation to make space key presses visible in the test history display.
You can copy the key history text or take screenshots of test results for documentation. The tool doesn't have built-in export functionality, but copying history text or capturing screenshots provides sufficient documentation for support tickets, troubleshooting documentation, or keyboard issue reporting. Copy functionality makes it easy to share test results with support teams or save for records.
Click the "Reset Test" button to clear all statistics, key history, and reset displays to initial state. This clears total key count, unique key count, modifier statistics, special key counts, and the entire key history log, allowing you to start a new keyboard test session from scratch without page refresh.
Caps Lock changes character output (uppercase vs lowercase) but the key press itself is still detected and logged correctly. When Caps Lock is active, letter keys produce uppercase characters, but the physical key presses are still registered. The tool detects both the key press event and the resulting character output, so Caps Lock affects output but not key detection accuracy.
Yes, the tool works with both physical keyboards and virtual on-screen keyboards. On touchscreen devices, tapping virtual keyboard keys generates keyboard events that are detected by the tool. The virtual keyboard buttons in the tool can also simulate key presses. However, some physical keyboard features (function keys, media keys) may not be available on virtual keyboards.
Common causes include: input area doesn't have focus, browser extensions intercepting keys, OS-level keyboard shortcuts capturing keys, accessibility filters blocking events, or keys that are handled at OS level (like some media keys). Ensure input area has focus, disable extensions, test in clean browser profile, and verify key isn't handled by OS shortcuts or security software that might block keyboard events.