Switch layout with Caps Lock —
without the lag.
macOS can already switch languages with Caps Lock. It just feels slow — because it has to be. Zwitch uses the same key with no debounce, so the layout flips the instant you tap it.
Why the built-in Caps Lock switch drags
One physical key has to mean two things: toggle Caps Lock, or switch input source. macOS tells them apart by waiting — you hold the key briefly and only then does the layout change. That deliberate pause is the lag. In practice it's around 200 ms before the new layout is live, every single switch.
How Zwitch removes it
Zwitch treats a Caps Lock tap as the switch itself — no hold, no waiting to disambiguate. It sets the active input source directly through the macOS Text Input Source API, so the layout changes in about 14 ms from key release, with no animation.
| Gesture | Animation | Speed | |
|---|---|---|---|
| Caps Lock (native) | hold to disambiguate | — | ~200 ms |
| Caps Lock (Zwitch) | single tap | none | ~14 ms |
Set it up in two steps
- Turn off the native Caps Lock switch. System Settings → Keyboard → Input Sources (and Shortcuts), so macOS doesn't also try to switch — otherwise both fire and you switch twice.
- Pick Caps Lock as your Zwitch trigger and grant Accessibility once. Tap it to cycle the layouts you already use in macOS, in their order.
Same key, none of the wait
FAQ
Why does the built-in Caps Lock switch feel slow?
macOS has to tell a real Caps Lock toggle apart from a layout switch, so it waits for a brief hold before acting. That deliberate debounce is the lag — roughly 200 ms before the layout changes.
How is Zwitch faster on the same key?
Zwitch treats a Caps Lock tap as the switch itself and sets the input source directly — about 14 ms from key release, with no hold and no animation.
Will I lose the actual Caps Lock function?
If you assign Caps Lock as the trigger, that key becomes your layout switch. Pick Fn / Globe or right Command instead if you still need Caps Lock to capitalize.