Compact layout differences
Laptops may combine navigation keys, omit right-side modifiers, shrink arrows, or move Delete and power controls. This visual is representative, not a manufacturer-specific diagram.
Compact layout diagnostic
Laptop Keyboard Test
Test a focused laptop-style layout with no dedicated numpad by default, or switch to a general laptop-with-numpad view when that better matches your keyboard.
Key state remains in temporary browser memory.
Compact layout test
Press each key on your laptop
Keys tested0 / 76
Last key—
Currently pressed0
Swipe sideways if the compact layout is wider than your screen.
- Esc
- F1
- F2
- F3
- F4
- F5
- F6
- F7
- F8
- F9
- F10
- F11
- F12
- ~`
- !1
- @2
- #3
- $4
- %5
- ^6
- &7
- *8
- (9
- )0
- _-
- +=
- Backspace
- Tab
- Q
- W
- E
- R
- T
- Y
- U
- I
- O
- P
- {[
- }]
- |\
- Caps Lock
- A
- S
- D
- F
- G
- H
- J
- K
- L
- :;
- "'
- Enter
- Shift
- Z
- X
- C
- V
- B
- N
- M
- <,
- >.
- ?/
- Shift
- Ctrl
- OS
- Alt
- Space
- Alt
- Ctrl
- ←
- ↑
- ↓
- →
Untested Pressed now Tested
Fn is intentionally not represented as a detectable browser key.
A practical pass
How to test a laptop keyboard
- Choose the closest general layout, not a claimed model match.
- Press and fully release keys across each row.
- Check arrows and both observable modifier positions.
- Compare missing events in another app, browser, or the operating system.
Embedded and dedicated numpads
A compact laptop may expose number-pad behavior through an Fn layer, while a larger laptop may send distinct Numpad1-style codes. Use the optional view only for a dedicated physical keypad. For deeper checks, use the Numpad Test.
Fn and Fn Lock limitations
Fn is often handled by keyboard firmware and may never create a browser event. Brightness, volume, keyboard backlight, airplane mode, and other Fn-layer controls can also be processed outside the page. This tool does not create a fake Fn result.
BIOS, OS, and app differences
A key can work in firmware setup but be remapped by the operating system, or work in one application but be reserved in another. The Function Keys Test explains common browser-sensitive top-row behavior.
What detection proves
A tested state means the browser received a matching physical KeyboardEvent.code. An untested state does not prove hardware failure; layout, shortcuts, drivers, firmware, focus, and accessibility settings can affect events.
Private by design
The test keeps pressed, tested, and last-key state in this page's memory. It does not save raw key events, timings, or typed content, and it does not send them to a server.