Short answer: your Mac's Caps Lock feels slow because macOS delays it by about 75 milliseconds on purpose. Apple's keyboard input filter holds each Caps Lock press for 75 ms before it registers, to stop an accidental brush of the key from switching you into capitals. Tap faster than that and the press is thrown away completely — no toggle, no light. The delay applies only to turning Caps Lock on; turning it off is instant. And it can be removed.
Key facts
- What it is
- A deliberate ~75 ms delay on Caps Lock activation.
- Where it lives
- Apple's
IOHIDKeyboardFilter(the constantkCapsLockDelayMS = 75). - Why it exists
- To prevent an accidental key brush from turning Caps Lock on.
- What it affects
- Turning Caps Lock on only. Turning it off is always instant.
- Whose fault
- Not your keyboard and not your fingers. It's software, on every Mac.
- Can you fix it
- Yes — via the
CapsLockDelayOverrideproperty, or an app like FastKey.
Is the Caps Lock delay a bug or a feature?
It's a feature — a deliberate one. Apple built a short delay into Caps Lock so that a quick accidental touch of the key doesn't flip your Mac into capitals. The idea is reasonable: Caps Lock sits right where your little finger rests, and one stray brush shouldn't shout your next sentence.
The problem is the side effect. The same delay that ignores accidental brushes also ignores intentional quick taps. If you type fast, the delay can't tell the difference between a mistake and a deliberate press — so it swallows both.
Why do I have to press Caps Lock twice on my Mac?
Because your first tap was faster than the delay. macOS holds a Caps Lock press for 75 ms before it counts. A quick, confident tap is often shorter than that, so it never registers. Your second press — usually a little slower and more deliberate — clears the threshold and finally turns Caps Lock on.
People describe this exactly the way it feels: "I thought Caps Lock was just broken; I always had to hit it twice." It isn't broken. Your first tap was thrown away by design.
How long is the delay, exactly?
75 milliseconds. This isn't a guess or a vague "lag" — it's a fixed constant in Apple's open-source keyboard code. In the file that filters keyboard input, IOHIDKeyboardFilter.mm, the value is defined as kCapsLockDelayMS = 75. You can read it yourself in Apple's public IOHIDFamily source.
Here's the mechanism. When you press Caps Lock while it's off, the filter doesn't pass the press through right away. It stashes the key-down event and starts a 75 ms timer:
- Hold past 75 ms and the timer fires: the held press is released, and Caps Lock turns on.
- Release before 75 ms and the timer is cancelled: the press it was holding is discarded, and nothing happens at all.
That's why a swallowed tap gives you nothing — not a late toggle, not a flickering light. The event was deleted before it ever reached the system.
The 75 ms figure is the current default. macOS also exposes an override, so the effective delay on your Mac can be changed to zero — that's the whole basis of the fix further down.
Why does turning Caps Lock off feel instant?
Because the delay is deliberately one-directional. Apple's own code comments it as "Delay on activation only." The filter only holds the press when Caps Lock is currently off and you're trying to turn it on. When it's already on and you press to turn it off, the press passes straight through with no timer at all.
So the asymmetry you feel — sluggish to turn on, instant to turn off — is exactly what the software is designed to do.
Who does this actually hurt?
Anyone whose Caps Lock taps are quick and deliberate:
- Fast typists writing an acronym or a single capitalized word mid-sentence, where the tap is a reflex, not a pause.
- Bilingual typists toggling case constantly between scripts and styles.
- Developers and terminal users, especially anyone who has remapped Caps Lock to Control — the same delay can blunt a quick Control press, so a fast
Ctrlshortcut doesn't land. - Anyone who simply types fast and has quietly assumed for years that their keyboard was flaky.
Is it your keyboard's fault?
No. This is not a hardware defect, a worn key, or a "butterfly keyboard" problem, and no repair will change it. The delay lives in software that ships with macOS, so it behaves the same on a MacBook Air, a MacBook Pro, an external USB keyboard, or a Bluetooth one. If you plug in a brand-new keyboard, you'll feel the exact same 75 ms.
That's actually good news: because it's software, you can turn it off without touching your hardware.
Can you remove the Caps Lock delay?
Yes. macOS exposes a property called CapsLockDelayOverride. Set it to 0 and the activation delay is skipped — Caps Lock registers the instant you tap it, the way it does on Windows. There are two honest ways to get there:
- The free way: a single
hidutilcommand in Terminal. It works immediately, but it resets every time you reboot and ignores keyboards you connect afterward. - The permanent way: FastKey, a small menu-bar app that applies the same override and keeps it applied — across restarts, sleep, and every keyboard you plug in — with a one-click on/off and a built-in test to prove it's working.
We wrote a step-by-step for both, including the exact command, in the guide below.
Feel the difference for yourself
FastKey removes the 75 ms delay and keeps it removed, on every keyboard. Try it free for 14 days — every feature unlocked, no account.
Download the free trialFrequently asked questions
Why is my Caps Lock slow on Mac?
macOS delays Caps Lock activation by about 75 ms on purpose, to prevent accidental capitalization. If you release the key faster than that, the press is discarded, so Caps Lock feels slow or unresponsive. It is not a keyboard fault.
Does Apple add a delay to the Caps Lock key deliberately?
Yes. The delay is a fixed value (kCapsLockDelayMS = 75) in Apple's open-source keyboard filter. It is intentional, not a bug.
Why does my Caps Lock light come on late?
The light follows the actual toggle, and the toggle is held for 75 ms. If you hold long enough for the press to count, the light comes on at that moment — which feels late compared with an instant key.
Is the delay a bug I should report to Apple?
No. It's a design choice that has been in macOS for many years. Rather than wait for Apple to change it, you can override it yourself — free with a command, or automatically with FastKey.