Mac Copy Paste Not Working? Here Are the Fixes

#The fast fix: restart the pasteboard server

Start here, because it resolves the majority of cases and costs you nothing. macOS keeps the clipboard inside a small background service called the pasteboard server, and its process is named pboard. Every copy hands data to pboard, every paste asks pboard for it. When that process hangs, and it does hang, copy and paste both fail silently: no error, no beep, the menu items even look normal. They just stop moving data.

The cure is to quit pboard and let macOS relaunch it, which it does instantly. Open Terminal (it is in Applications, Utilities) and run this:

killall pboard

Press Return. Nothing dramatic prints. Now go back to any app, select some text, press Cmd+C, click elsewhere, press Cmd+V. In most cases the clipboard is alive again. If you would rather avoid Terminal, open Activity Monitor, type pboard into the search box, select the row, and click the stop button in the toolbar, then confirm Quit. Same effect. macOS treats pboard as a managed service, so killing it is safe: the system brings it right back.

If that did not do it, do not keep hammering the same command. Move down the list, because the cause is somewhere else.

#Why Ctrl+V does nothing on a Mac

This one is not a bug, and it catches almost everyone who switches from Windows. The Mac does not use the Control key for clipboard actions. It uses the Command key, the one with the ⌘ symbol next to the space bar. So the shortcuts are:

• Cmd+C to copy
• Cmd+X to cut
• Cmd+V to paste

Press Ctrl+V out of habit and, depending on the app, you get nothing or a stray text-editing action. Your hand is on the right key in the wrong corner. I wrote the full muscle-memory map in how to copy on a Mac, including the paste-and-match-style variant that strips formatting, which is the shortcut most people actually want when a paste brings in ugly fonts. If your paste works fine with the Edit menu but not with the keyboard, this is your answer, and no amount of restarting pboard will change it.

One related snag: some apps remap Cmd+V for their own paste-special behavior, and a few remote-desktop or virtual-machine windows swallow the shortcut entirely and send it to the guest system. If paste fails only inside one specific window like that, the clipboard is fine and the app is the reason.

#What the pasteboard server is, and why it dies

Worth thirty seconds of theory, because it tells you which fixes are real and which are folklore. On a Mac there is one system clipboard, and it lives in memory managed by pboard. When you copy, the source app writes the data plus a list of formats it can offer (plain text, rich text, an image, a file reference) and pboard holds them. When you paste, the destination app asks pboard for the richest format it understands. That handshake is why you can copy from a web page and paste styled text into Pages but plain text into a code editor.

Things wedge that pipe. A poorly behaved app can copy something enormous, or copy a format it never finishes writing, and leave pboard waiting. A promise-based copy, where the app says "I will provide the data when asked" and then never does, is a classic. When that happens the next paste hangs on a reply that never comes. Killing pboard throws away the stuck state and starts clean. That is the whole reason the reset works, and why a reboot works too: a reboot just restarts pboard along with everything else, the slow way. If you want the longer explanation of how the macOS clipboard is structured, I laid it out in how the Mac clipboard actually works.

Two pieces of folklore worth retiring. Resetting NVRAM does nothing for the clipboard; it stores firmware settings, not pasteboard state. And there is no hidden clipboard-cache file to delete. The clipboard is in memory, so restarting the process, or the machine, is the reset. Anything telling you to trash a specific file to fix copy and paste is guessing.

#When it is one app, not the whole Mac

Before you assume the system is at fault, find out whether the problem is global or local. Test copy and paste between two plain apps, say TextEdit and Notes. If that works, your clipboard is healthy and one specific app is the offender.

The usual suspects and what to do:

• The app is hung. If copy fails only in one app and that app feels sluggish elsewhere, quit it fully (Cmd+Q, or Force Quit from the Apple menu) and reopen. A frozen app cannot answer a paste request.
• A browser tab is the source. Some sites block copy with JavaScript, and some rich editors put unusual data on the clipboard that other apps choke on. Try copying from a different tab, or use paste-and-match-style at the destination to force plain text.
• A clipboard tool is fighting the system. If you run more than one clipboard manager, or an automation utility that hooks the clipboard, they can collide. Quit them one at a time and retest. The tool meant to help is sometimes the thing jamming pboard.
• Login-session rot. If everything above checks out but paste is still flaky across apps and pboard restarts do not hold, log out and back in, or restart. A stale window-server or login session can drag the clipboard down with it.

Work top to bottom and you will almost always land on the cause without wiping or reinstalling anything.

#Copying from iPhone to Mac stopped working

This is a different animal, so treat it separately. Copying on your iPhone and pasting on your Mac is Universal Clipboard, part of Handoff, and when it fails your Mac clipboard is usually perfectly fine. It just is not receiving the handoff. The requirements are strict and all of them have to be true at once:

• Both devices signed into the same Apple ID.
• Bluetooth and Wi-Fi on for both, and they should be on the same network and close together.
• Handoff enabled: on the Mac in System Settings, General, AirDrop & Handoff; on the iPhone in Settings, General, AirPlay & Handoff.
• You paste quickly. Universal Clipboard times out after a couple of minutes, so copy on the phone and paste on the Mac in the same breath.

If it still refuses, toggle Bluetooth and Wi-Fi off and back on for both devices, which re-establishes the pairing more often than anything else. Universal Clipboard is convenience, not a channel you can lean on for anything you must not lose, so for real cross-device transfer of a file I would AirDrop it instead. And to be clear: a Universal Clipboard failure is not the same as your Mac clipboard being broken, so do not run killall pboard hoping it fixes iPhone paste. It will not, because that machinery is somewhere else entirely.

#Copy and paste in Terminal

Terminal has its own quirks worth knowing, because "Mac copy paste not working in Terminal" is usually one of three specific things, not a broken clipboard.

First, the keys. In Terminal, Cmd+C copies and Cmd+V pastes like everywhere else, but Ctrl+C is a signal that interrupts the running program. So if you press Ctrl+C expecting a copy, you just killed your command instead. Use Cmd+C. Second, a lot of paste failures inside Terminal are actually the shell running a program that grabs the keyboard for itself, like a full-screen editor or a paging tool, where the app decides what a keystroke means. And third, you can move text between the shell and the system clipboard from scripts with these two tools:

# put the output of a command onto the clipboard
echo "hello" | pbcopy

# paste whatever is on the clipboard into a command
pbpaste

Those talk to the same pboard everything else uses, so if pbpaste comes back empty when you know you copied something, that is another sign pboard has wedged and wants the restart from the first section.

#A clipboard manager so it never costs you again

The reason a clipboard hiccup stings is that the Mac clipboard holds exactly one thing. Copy again and the last item is gone. So when paste fails, whatever you copied can be lost for good. A clipboard manager fixes that by keeping a history: even if the current clipboard breaks, your last copies are still sitting in a list you can pull from.

Two I would point people at first: Maccy, which is free, open source, and does one job well, and Paste, a paid app with a richer, more visual history if you copy all day. Either one means a wedged pboard is an annoyance, not a lost paragraph, because the text is recoverable from the history rather than from a clipboard that just failed you.

I build one too. NotchBay keeps a clipboard tray in the MacBook notch: the last 60 clips, auto-sorted into text, links, colors, images and files, with screenshots run through OCR so you can search the words inside them, and any clip you pin never expires. It is one piece of a broader notch app rather than a standalone clipboard tool, and it needs macOS 26 and a MacBook with a notch, so it is not for everyone. Whichever route you take, the point holds: a history is cheap insurance against the exact failure this whole page is about.

#Frequently asked questions