Guide

How to use Windows keyboard shortcuts on a Mac

By Wondering Works, maker of Windsify · Updated

You know the keys. Your hands know the keys. Then you sit down at a Mac and Ctrl+C does nothing. Here is why that happens, the three ways to fix it, and what each one costs you.

Why your shortcuts stopped working

Nothing is broken. macOS simply puts application shortcuts on a different key.

On Windows, almost every shortcut runs through Control: Ctrl+C, Ctrl+S, Ctrl+Z, Ctrl+F. On macOS those same shortcuts live on Command, the key next to the space bar. Control on a Mac is kept for something older and more specific — control characters. In a terminal, Ctrl+C still means interrupt the running process, the way it has for fifty years.

So Ctrl+C on a Mac isn't a dead key. It is a busy key doing a different job. That distinction matters, because it is exactly what most fixes get wrong.

The Windows-to-Mac cheat sheet

If you only want the translation table, here it is. Anywhere you would press Ctrl on Windows, press Command on a Mac.

Everyday shortcuts
WindowsmacOS
Ctrl+C / Ctrl+V / Ctrl+XCommand+C / V / X
Ctrl+Z / Ctrl+YCommand+Z / Command+Shift+Z
Ctrl+A / Ctrl+S / Ctrl+FCommand+A / S / F
Ctrl+T / Ctrl+WCommand+T / Command+W
Alt+TabCommand+Tab
Alt+F4Command+W or Command+Q
Ctrl+Left / Ctrl+RightOption+Left / Option+Right
Home / EndCommand+Left / Command+Right
F2 (rename)Return
Delete (to Recycle Bin)Command+Delete
Win+L (lock)Control+Command+Q
Win+Shift+S (screenshot)Command+Shift+4
Ctrl+Shift+EscCommand+Option+Esc

Some of these are close enough to learn in a week. Others aren't: Home and End moving to Command, undo and redo splitting across two different combinations, and rename landing on Return are the three that people are still fighting six months later.

Memorising the table is one option. The rest of this guide is about not having to.

Option 1: swap Control and Command in System Settings

macOS has a built-in remapper. Open System Settings › Keyboard › Keyboard Shortcuts › Modifier Keys, pick your keyboard from the menu, and you can reassign Caps Lock, Control, Option, Command and the Globe key. Set Control to act as Command and Command to act as Control, and Ctrl+C copies.

It works, it is free, and it takes ten seconds. It is also all-or-nothing, and that is the problem.

The swap moves the key, not the shortcut. Everything that used Command now needs Control, and everything that used Control now needs Command:

If you only ever write documents and never touch a terminal, this may be all you need. If you write code, it will bite you within a day.

Option 2: remap with hidutil

macOS ships a command-line tool called hidutil that remaps keys at a lower level than System Settings, using USB HID usage codes. It can do things the settings panel can't, such as remapping individual non-modifier keys.

Two caveats. First, it has the same fundamental limitation as the modifier swap: it moves keys, so it cannot tell the difference between Ctrl+C in a text editor and Ctrl+C in a terminal. Second, a hidutil mapping does not survive a reboot on its own — keeping it means writing a property list and loading it as a launch agent, and then remembering it exists the next time your keyboard behaves strangely.

Option 3: translate the shortcut, not the key

The third approach is different in kind. Instead of swapping which physical key is which, it watches for the shortcut you pressed and sends the Mac equivalent — one shortcut at a time, with the option to behave differently depending on which app is in front.

This is what Windsify does. Physical Control stays Control. There is no system-level modifier swap. When you press Ctrl+C in a text editor, it copies. When you press Ctrl+C in Terminal, it still interrupts, because a terminal is a place where Ctrl+A through Ctrl+Z should stay exactly what they have always been.

The same idea covers the shortcuts a straight key swap cannot reach at all:

What translation adds
You pressWhat happens on the Mac
Alt+TabSwitches apps, forward and back
Alt+F4Closes the active window
Home / EndStart and end of line, but only in a text editor
F2Renames the selected file in Finder
Ctrl+X then Ctrl+VMoves a file in Finder
Tap the Windows keyOpens Spotlight
Win+LLocks the Mac
Win+Shift+SScreenshot selection
Ctrl+Shift+EscOpens Activity Monitor

Home and End are the clearest example of why context matters. They should jump to the start and end of a line — but only while you are actually editing text. Everywhere else the keys pass through untouched, so nothing unrelated fires. A key-level remapper has no way to know the difference.

The full list is on the shortcut reference page.

What about the Windows key itself?

Plug a Windows keyboard into a Mac and macOS reports the Windows key as Command and Alt as Option. That is the right logical mapping, but the physical order is crossed: a Windows keyboard runs Ctrl, Win, Alt from the left, while an Apple keyboard runs Control, Option, Command — so Command ends up one key further from the space bar than a Mac user expects. If you are pressing Windows shortcuts, that doesn't matter. There is more detail in the Windows key on a Mac.

What about snapping windows?

This is the other half of the switch, and it catches people who have already solved their keyboard. Windows has had Win+Left and Win+Right since 2009. macOS has window tiling, but the keyboard shortcuts and the drag-to-edge behaviour don't match what your hands do.

Windsify covers both halves in one app: halves, quarters, fill and restore, drag-to-edge previews and multi-display moves, on the Win+Arrow keys you already use.

For the window half of the setup, see native Mac tiling and Win+Arrow. For custom keyboard rules, see the Karabiner-Elements comparison.

Which one should you pick?

Free uses generic Windows mappings inside embedded terminals, where Ctrl+C maps to copy instead of interrupt. Pro adds automatic VS Code terminal support; Codex and Claude use explicit terminal copy shortcuts.

Frequently asked questions

Why doesn't Ctrl+C work on a Mac?

macOS puts application shortcuts on the Command key, not Control. Ctrl+C is reserved as a control character — in a terminal it sends an interrupt. So Ctrl+C on a Mac isn't broken, it is doing a different job. Copy is Command+C.

Can I swap Control and Command on a Mac?

Yes. System Settings › Keyboard › Keyboard Shortcuts › Modifier Keys lets you remap Control, Option, Command and Caps Lock, per keyboard. It is a global, all-or-nothing swap: every Command shortcut moves to the Control key, including Command-click, Command+Tab and the terminal's control sequences.

What is the Windows key equivalent on a Mac?

On a Windows keyboard plugged into a Mac, the Windows key is reported to macOS as Command and Alt is reported as Option. The physical position matches, so your thumbs are already in the right place.

Does remapping keys stop Ctrl+C from interrupting in Terminal?

A global modifier swap does, because the Control key itself has moved. A per-shortcut translation layer can leave terminal applications alone, so Ctrl+A through Ctrl+Z stay native control sequences and Ctrl+C keeps interrupting.

Can I keep the remapper I already use?

With Windsify, yes. It detects other keyboard remappers and window managers automatically and stays out of their way — while another tool is actively remapping, including a macOS Modifier Keys or hidutil mapping, Windsify pauses only its own overlapping keyboard layer. Window management keeps running. You can migrate at your own pace.

Keep your muscle memory

Windsify translates the shortcuts your hands already know and manages your windows, in one native menu-bar app. No telemetry, no account, and typed text is never collected or sent.

Download Windsify 1.4.13

Every download runs full Pro for 14 days, then keeps every Free feature. macOS 15 or newer, signed and notarized.

Related guides