How Num Lock changes output
Depending on the platform, Num Lock can switch keypad keys between digits and navigation functions. Physical codes may remain Numpad codes even when the resulting action changes.
Numeric keypad diagnostic
Numpad Test
Test the dedicated numeric keypad, distinguish it from top-row digits, and enter a short Numpad-only sequence using physical key positions.
Numpad events and challenge progress are not stored.
Physical keypad test
Test your numeric keypad
Focus the keypad and use the separate numeric keypad. Top-row codes such as Digit1 do not count as Numpad1.
Num Lock
/
×
−
7
8
9
+
4
5
6
1
2
3
Enter
0
.
Keys tested0 / 17
Last numpad key—
Currently pressed0
Num Lock observedUnavailable / not observedBrowser-reported state only
Numpad-only challenge
7 4 2 9 0
Entered with numpad: —
Next expected: 7Only physical Numpad digit codes advance this challenge.
Physical-position distinction
Numpad keys are not number-row keys
The key marked 1 above the letters normally reports Digit1. A separate keypad 1 reports Numpad1. Only the latter advances this page's challenge.
Top rowDigit1Does not count
Numeric keypadNumpad1Counts as keypad input
Keypad behavior
Interpret Num Lock and application differences
The browser may report Num Lock as on or off through modifier state. That observation is useful context but is not guaranteed to be available or reliable on every operating system.
Laptops without a separate keypad
Many laptops omit a dedicated numeric keypad. Others provide an embedded or Fn-layer keypad that firmware handles differently.
Embedded numeric layers
An Fn-layer number may not report the same physical code as a full-size Numpad key. This page does not pretend every compact layout exposes all 17 positions.
Works here but not in an application
Check the application's Num Lock assumptions, shortcuts, input mode, decimal separator, layout settings, and remapping software.
Operators and Enter
The focused keypad includes Add, Subtract, Multiply, Divide, Decimal, and NumpadEnter so they remain distinct from similar main-keyboard positions.
Browser limits and privacy
Current states and the predefined 74290 challenge remain in temporary memory. No keypad sequence or raw event is transmitted or persisted.
Example interpretations
Examples of numeric-keypad observations
These examples explain possible outcomes. They are not results from your current session.
Dedicated keypad detected
- Observed
- Physical Numpad positions appear and the keypad-only challenge advances.
- May mean
- The browser distinguished those keys from the top number row.
- Does not prove
- That every application interprets Num Lock or decimal input the same way.
- Next step
- Compare the application's keypad mode if numeric entry still differs.
Top-row digit entered
- Observed
- A Digit code appears instead of a Numpad code, so the challenge does not advance.
- May mean
- The browser saw the main number row rather than a dedicated keypad position.
- Does not prove
- A failed numpad key.
- Next step
- Focus the keypad surface and use the separate physical numeric keypad.
Embedded layer inconclusive
- Observed
- An Fn-layer number performs an action but does not report a dedicated Numpad code.
- May mean
- Laptop firmware or the operating system may be translating the embedded layer.
- Does not prove
- That the embedded key is broken.
- Next step
- Check the laptop's documented Fn/Num Lock behavior and test the intended action outside the browser.