See the real LED
Toggle Num Lock from the menu bar and synchronize the standard hardware LED across active keyboards.
Native macOS menu-bar utility
NumLockLED restores a dependable Num Lock LED and familiar Windows-style keypad navigation for compatible external keyboards. No drivers, no synthetic events, no keyboard seizure.
Version 0.1.0 macOS 13 Ventura and later Apple silicon
A small utility with careful boundaries
NumLockLED detects capable external keyboards, waits for a valid report, and keeps each device's original mapping safe. Turn it off and your keyboard returns to the exact state it had before.
Toggle Num Lock from the menu bar and synchronize the standard hardware LED across active keyboards.
With Num Lock off, the keypad becomes Home, arrows, Page Up, End, Insert, and Delete, just as you expect.
Durable, identity-bound leases preserve foreign mappings and restore them transactionally on disable, sleep, or quit.
Compatibility
NumLockLED works with supported USB and Bluetooth keyboards that expose standard keypad usages and a standard Num Lock LED. Built-in, virtual, NKRO, vendor-specific, and ambiguous devices are left untouched.
Simple licensing
Buy NumLockLED once and activate it on up to five devices. There is no subscription and no recurring charge.
Start with the full 7-day trial, then activate when you are ready.
Ready in under a minute
The signed package installs NumLockLED into your user Applications folder. Launch it, grant Input Monitoring when macOS asks, and the menu-bar control is ready.
Prefer a drag-and-drop disk image? Download the DMGSupport
Need help with installation, activation, or keyboard compatibility? Email service@gt4t.ai.
The app reads raw reports only from supported external keyboards so it can keep keypad key-down and key-up pairs consistent. It never posts synthetic events.
NumLockLED owns only the mappings for keyboards it manages. Configure Karabiner-Elements to ignore those devices so the two tools do not compete.
The app restores every saved, pre-existing mapping after held keys are released. If a write cannot be verified, it keeps retry state instead of claiming cleanup succeeded.