How to use Cmd+C and Cmd+V on Windows
Windows uses Ctrl+C and Ctrl+V to copy and paste — there is no Command key. To copy and paste with ⌘ like on a Mac, you remap the key in the Command position to act as Ctrl. Macifier does this automatically, while keeping Ctrl native where it matters (like the terminal).
If you've moved from a Mac to a Windows PC, the muscle memory that breaks first is copy and paste. On macOS it's ⌘C / ⌘V; on Windows it's Ctrl+C / Ctrl+V. Hit ⌘C on a Windows keyboard and nothing happens — the key in that spot is the Windows key.
The fix is to make the key in the Command position behave like Ctrl for shortcuts. You can do it by hand with a remapper, but the catch is the terminal, where Ctrl+C must stay an interrupt. Macifier handles both: ⌘C/⌘V copy and paste everywhere, and Ctrl stays native in the shell.
The fast way — with Macifier
- 1Install Macifier and let it start in the tray.
- 2Mac-style mappings are on by default — press ⌘C to copy and ⌘V to paste immediately.
- 3Leave terminal-aware Ctrl enabled so Ctrl+C still interrupts in cmd, PowerShell, and Windows Terminal.
Manual remapping (PowerToys or AutoHotkey)
- 1Open PowerToys Keyboard Manager (or write an AutoHotkey script).
- 2Remap the Windows/Command-position key to send Ctrl.
- 3Test copy and paste across your apps.
Manual remapping is static — it can't tell apps apart, so it will also override Ctrl+C in the terminal (breaking interrupt) and clobber Windows-key shortcuts. That context-awareness is the main reason a purpose-built app is easier here.
FAQ
Why doesn't Cmd+C work on Windows by default?
Windows has no Command key — the key in that position is the Windows key, and copy/paste are bound to Ctrl+C/Ctrl+V. You need to remap it for ⌘C/⌘V to work.
Will remapping break Ctrl+C in the terminal?
With a static remapper it can. Macifier is terminal-aware, so Ctrl+C still sends an interrupt in the shell while ⌘C copies everywhere else.