How to Safely Eject an SD Card on Mac (and Errors)
To safely eject an SD card on a Mac, click the Eject button next to the card in the Finder sidebar, or select the card and choose File › Eject (⌘E), or drag its desktop icon to the Trash. Wait until the card’s icon disappears, then pull the card out. Apple describes all three on its storage devices page.
The three ways to eject an SD card
- Finder sidebar. Under Locations, click the small Eject button (⏏) to the right of the card’s name.
- File › Eject, or ⌘E. Select the card in Finder or on the desktop and choose File › Eject. The shortcut is Command-E; we read it from Finder’s File menu on macOS 27.2.1.
- Drag to the Trash. Drag the card’s desktop icon to the Trash in the Dock. This ejects it; it doesn’t delete anything.
Whichever you use, the card is safe to remove once its icon is gone from the sidebar and desktop. The same steps work for an external drive.
What happens if you remove an SD card without ejecting?
Often nothing visible, and that is what makes it a bad habit. Ejecting tells macOS to finish every pending write and close the card’s file system cleanly. Pull the card early and you can lose:
- A file that was still being written. macOS doesn’t always write data to the card the moment an app says “saved”; some of it can still be on its way.
- The file system’s own bookkeeping. If the card’s directory records were mid-update, the card can come back needing repair, or with files missing.
Even when you only copied from the card, macOS can write small housekeeping files of its own to it, so “I wasn’t writing anything” isn’t a guarantee. Apple also warns not to remove an SD card while the Mac is asleep, because it could lead to data loss (Apple).
The worst case is a camera card in the middle of a copy. The copy on your drive is cut short, the card goes back into the camera, and the gap only shows up in the edit. That case has its own page: why ejecting a card mid-offload is risky.
”Disk Not Ejected Properly” keeps popping up
That notification means macOS lost the disk without an eject. If you pulled the card, that’s the reason. If you didn’t touch it, the problem is usually the connection, not you. Common causes:
- Sleep. Some readers and hubs drop their disks when the Mac sleeps. Eject cards before you close the lid, or keep the Mac awake during long copies. Apple’s sleep warning for SD cards above applies here too.
- Hubs and power. A bus-powered hub or dock may not supply enough power for a reader plus a drive. Apple’s advice for USB devices that get disabled is the right checklist: reconnect, try another port, connect directly instead of through a hub, or use a self-powered hub on its AC adapter.
- Cables and readers. A worn cable or a cheap reader can drop for a split second, which is enough for macOS to report an unexpected removal. Swap the cable first, then the reader.
- The card or drive itself. If the message follows one card or one drive across readers and ports, suspect that device.
One narrow Apple case: on Mac Pro (2023), internal SATA drives could show this after sleep; Apple fixed it in macOS Ventura 13.5 (Apple).
If the notification appears while footage is copying, treat the copy as suspect and check it before you format anything.
Can’t eject the disk because an app is using it
macOS refuses to eject a disk that an app still has files open on. Apple’s steps for this:
- The warning may name the app. Quit it.
- If an app won’t quit, close its documents that are on the disk.
- Press ⌘-Tab to see which apps are open.
If that doesn’t help, Apple suggests logging out and back in, and if it still won’t eject, shutting down, disconnecting the disk and starting up again. Another user logged in on the same Mac can also hold a disk (Apple).
Find the app that’s using the card with lsof
When the warning doesn’t name the app, Terminal can. lsof lists open files; with +D it lists every open file inside a folder or volume. In this example a test file, held open by tail, stands in for a clip on a card named A001. Output from macOS 27.2.1, with the path shortened:
$ lsof +D /Volumes/A001
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
tail 80593 you 3r REG 1,16 5 92008900 /Volumes/A001/A001C003.mov
The COMMAND column is the app or process and PID its process ID. Quit that app normally. Once nothing has the card open, lsof prints nothing at all, and the eject goes through.
Background tools are the usual suspects: preview and indexing services, a media player, an editing app that still has a project pointing at the card, or a backup or sync tool.
Force eject, and its risk
If an app won’t let go, Finder may offer to force the eject. Treat that as pulling the card while it’s in use: whatever the app was reading or writing is cut off. On a card you have already copied and checked, that’s acceptable. On a card that is the only copy of the footage, find and quit the app instead.
FAQ
Can I remove an SD card without ejecting it?
You can get away with it sometimes, but every pull without an eject risks an unfinished write or a damaged file system. Ejecting takes a second. Always do it with a card that holds the only copy of something.
Why is the Eject option missing for my SD card?
Look in the Finder sidebar under Locations. If the card isn’t listed there at all, it isn’t mounted. See SD card not showing up on Mac.
Do I need to eject before closing my MacBook?
Apple warns against removing an SD card while the Mac is asleep. Eject first, then close the lid, or leave the card in until the Mac is awake again.
Keep reading: How to transfer videos from an SD card to a Mac · Why ejecting a card mid-offload is risky · SD card not showing up on Mac · Olycen vs ShotPut Pro
Try Olycen free for 14 days.
The trial starts at your first offload, so a whole shoot fits in it. Olycen copies each card to two or more drives, reads every copy back against the card, and tells you when it is safe to format. Then $129 once, two Macs, no subscription.