How to cut and paste files on a Mac — every method

Why ⌘X doesn't work on files

On Windows, Ctrl-X → Ctrl-V has moved files since 1995. Apple deliberately left it out: their concern was that a file "cut" to an invisible clipboard feels lost — if you forget to paste, where did it go? (The answer, on every OS that supports it: nowhere, until you paste. But the anxiety shaped the design.)

So the Finder's Edit menu offers Copy and Paste for files, but no Cut. The good news: a move-on-paste operation exists in macOS — it's just hidden behind a modifier key most people never discover.

Method 1: ⌘C then ⌘⌥V Built in · Free

macOS's native answer, no apps required:

1. Select the file and press ⌘C (Copy) — yes, Copy, even though you want to move.
2. Open the destination folder.
3. Press ⌘⌥V — Option turns "Paste Item" into "Move Item Here."

You can see it in the Finder yourself: open the Edit menu, then hold ⌥ and watch "Paste Item" change.

The catch: it's backwards — you decide copy-vs-move at the destination, not when you grab the file. There's no visual feedback on the file you copied, the muscle memory is the reverse of Windows and of every text editor (where ⌘X means "this is leaving"), and if you press plain ⌘V out of habit you get a duplicate instead of a move.

Method 2: Drag with the mouse Built in · Free

The way most Mac users actually move files:

• Same disk: drag the file to the destination — it moves.
• Different disk or external drive: drag copies by default; hold ⌘ while dropping to force a move.
• Force a copy on the same disk: hold ⌥ while dropping.

The catch: you need both folders visible at once, which means arranging windows, opening split views, or hovering over spring-loaded folders. For one file it's fine; for the tenth time today it's friction the keyboard was invented to remove.

Method 3: Command X Free app

Command X by Sindre Sorhus is a free, sandboxed App Store utility that lets you press ⌘X then ⌘V to move files. It's well made, and if all you want is the keystroke, get it — it costs nothing.

The catch: the App Store sandbox limits what it can see and draw. There's no visual change to a cut file — nothing marks what's "in motion" — and a sandboxed app can't reliably tell a file cut from a text cut while you're renaming a file, an edge case you hit surprisingly often.

Method 4: FinderCut $4.99 · Ours

Full disclosure: this guide is by us, and FinderCut is our app. It exists because we wanted the complete Windows behaviour, not just the keystroke:

• Press ⌘X and the file ghosts to 50% opacity right in the Finder — you can always see what's about to move, exactly like Windows has done for thirty years.
• ⌘V moves it. Same disk: instant true move, even for huge files. Across disks: behaves like the Finder's own drag-move.
• Changed your mind? Esc cancels and the ghost snaps back. Never pasted? The file simply stays put — nothing is ever at risk.
• Cutting text while renaming a file still cuts the text — it knows the difference.
• Notarized by Apple, no subscription, no account, and it never touches the network.

It runs outside the App Store (with an Apple Developer ID) precisely because the ghost effect and the rename-detection can't be done from inside the sandbox.

Which should you use?

Honest recommendation: if you move a file occasionally, learn ⌘⌥V — it's free and always there. If you came from Windows and your fingers press ⌘X a dozen times a day, get Command X (free) or FinderCut ($4.99) depending on whether you want the visual feedback.