Rent, Don't Buy: A Two-Week Colemak and Dvorak Test Drive on macOS
Photo: Dietmar Rabich, CC BY-SA 4.0, via Wikimedia Commons
Every few months someone posts a typing-speed graph and announces they've seen the light, and the light is arranged in a different order. Dvorak! Colemak! Something with thumb clusters and a learning curve shaped like a cliff. The pitch is always the same: less finger travel, more comfort, fewer wrist complaints by 4 p.m.
Fine. But most of us can't afford to spend a month typing at eleven words per minute while Slack piles up. So treat it like renting an apartment in a neighborhood you're curious about. Two weeks, one deposit, no furniture. Here's how to run that experiment on a Mac without setting your workweek on fire.
What you're actually shopping for
Speed is not the prize. Anyone who tells you a new layout will make you faster is selling something — most people plateau near their old numbers, just with less contortion. The real upside is comfort: fewer awkward reaches, more work happening on the home row, and less of that dull ache that shows up after a long writing session.
If you have no discomfort to solve and you type 90 WPM happily, you can stop reading. Genuinely. Go review a keyboard.
Pick your flavor: built-in versus bolted-on
Dvorak is the easy one. It ships with macOS. Open System Settings, head to Keyboard, hit Input Sources, click the plus, and it's sitting under English. There's even a variant called Dvorak – QWERTY ⌘ that keeps your Command shortcuts on their old physical keys, which we'll come back to because it matters more than you'd think.
Colemak is a slightly bigger lift. macOS doesn't include it, so you install a .keylayout file into ~/Library/Keyboard Layouts, log out and back in, and it appears in the same input source list. The upside of that per-user location is that nothing touches system-wide files and removal is a drag to the Trash.
The other route is Karabiner-Elements, which remaps keys at the driver level. It works in nearly every app and handles the shortcut problem elegantly through community rules. The catch: it can behave oddly around secure input fields, password prompts, and anything that grabs the keyboard before macOS finishes waking up. Useful tool, slightly fussy roommate.
One thing worth knowing before you start: your login password is typed on whatever layout is active at the login window. If you've remapped at the driver level, "qwerty" may not mean qwerty at the FileVault screen. Type your password slowly the first time, or better yet, don't remap system-wide on day one.
The safety net: a burner account
Make a standard user account just for the experiment. Fast user switching (turn on the menu in System Settings > Control Center) gets you between accounts in a couple of seconds. For the first week, your real account stays pure QWERTY and the test account is where your fingers go to embarrass themselves.
This gives you a hard rollback that requires zero cleanup. If the whole thing goes sideways at 2 p.m. on a Tuesday, you switch back and your deadlines never notice.
The shortcut tax is the actual cost
Here's the part the blog posts skip. On macOS, keyboard shortcuts are tied to the characters your layout produces, not to physical key positions. Select plain Dvorak and Command-C is no longer the key your left hand thinks it is — it's wherever the letter C now lives. Command-Z, Command-V, Command-S, all relocated. It is astonishing how much of your muscle memory is short commands rather than words.
Two fixes, both legitimate:
- Use the Dvorak – QWERTY ⌘ variant so shortcuts stay put while text entry moves.
- Use a Colemak variant with a QWERTY shortcut layer (several are published) or a Karabiner rule that does the same thing.
Then brace for app-level weirdness. Single-key tools in Photoshop map to the character, so your brush shortcut wanders. Figma and Blender have their own opinions. Games with WASD bindings will feel drunk. Vim users get to relearn hjkl positions or accept that they're now pressing something else entirely. And any web app using Ctrl-style shortcuts on a remote Windows session will make you question your choices.
The two-week schedule
Keep a cheat sheet taped under your monitor. Printed, not on-screen — you want your eyes up, not hunting.
| Days | Where the new layout lives | Drills |
|---|---|---|
| 0 | Nowhere. Run a baseline. | Three 60-second tests plus one 300-word email draft |
| 1–3 | Test account only | 15 minutes on keybr |
| 4–7 | Test account + email and chat | 15 minutes, then real messages |
| 8–11 | Full workday, minus the code editor | 10 minutes warm-up |
| 12–14 | Everything | Two timed tests daily |
Log three numbers every day: drill speed, accuracy, and a 1–5 wrist-fatigue rating. Add a bonus column for "number of times I said a bad word," because it's a real signal.
Don't start this during a launch week or the week your taxes are due. That's not dedication, that's poor planning.
What counts as a win
By day fourteen you want to see drill speed somewhere in the 30–40 WPM range with accuracy within a couple of points of your baseline, and fatigue ratings trending down. That's the break-even zone. If you're still at 15 WPM with error rates that look like a CAPTCHA failure, the layout isn't wrong — it's just not for you, and you've learned that for the price of two slightly annoying weeks.
The clean exit
Rolling back takes about three minutes. Remove the input source from System Settings, delete the .keylayout from ~/Library/Keyboard Layouts, and if you went the Karabiner route, disable the rule and restore your saved config. Then check one sneaky setting: Automatically switch to a document's input source can leave individual apps remembering a layout you thought you'd deleted, which is a fun way to spend a Friday afternoon.
Keep the QWERTY source one keystroke away for the entire experiment. Not because you'll need it, but because knowing it's there is what makes the whole thing feel like a choice instead of a commitment.