You’re in a hurry. The drive won’t eject. You pull the cable anyway. We’ve all done it.

Maybe nothing happened. Maybe you got that annoying “Disk Not Ejected Properly” notification and everything seemed fine afterward. So you start to wonder whether ejecting is really necessary, or just one of those cautious habits that doesn’t matter in practice.

It matters. But not always in the way you’d expect.

What ejecting actually does

When you eject a drive on macOS, the system does three things in sequence.

First, it flushes the write cache. macOS keeps recently written data in memory before committing it to the drive. This improves performance but means that data you “saved” might not actually be on the disk yet. Ejecting forces all cached data to be written.

Second, it closes all file handles. Every process that has a file open on the drive gets notified to release it. This gives applications a chance to finish what they’re doing and close files cleanly.

Third, it unmounts the volume. The drive is removed from the filesystem tree, and the operating system stops acknowledging its existence. Only after this step is it physically safe to disconnect.

When you skip ejecting and just pull the cable, you skip all three steps simultaneously.

The real risk: write caching

The write cache is where the danger lives. Modern operating systems, macOS included, don’t write data to external drives immediately. They batch writes together and flush them periodically for performance reasons.

If you copy a file and the progress bar completes, that doesn’t guarantee the data is on the drive. The system might have confirmed the copy from its own cache while the actual write is still queued. Disconnect at that moment and the file on the drive could be incomplete, corrupted, or missing entirely.

The window of risk varies. After a small file copy, it might be a second or two. After a large transfer, it could be ten seconds or more. There’s no visual indicator that tells you when the cache has been fully flushed.

What about drives you only read from?

If you connected the drive, opened some files, and never saved anything to it, the risk of unplugging drops significantly. No writes means no write cache to flush, and no files in mid-transfer.

But “never saved anything to it” is harder to guarantee than you’d think. macOS writes .DS_Store files to any folder you browse in Finder. Spotlight writes indexing data. Some applications create temporary files or lock files on volumes they access.

You might not have explicitly saved anything, but macOS probably wrote something.

Filesystem corruption

Beyond individual file loss, there’s the broader risk of filesystem corruption.

Filesystems maintain internal structures: directories, allocation tables, journal entries. These structures describe where every file lives on the disk and how space is allocated. When you write a file, the filesystem updates these structures. If you disconnect mid-update, the structures can end up in an inconsistent state.

HFS+ uses journaling, which records planned changes before making them. If a disconnect interrupts the process, the filesystem can replay the journal to recover to a consistent state. APFS takes a different approach entirely, using copy-on-write instead of journaling. New data is always written to free space first, and pointers are updated only after the write completes. If a disconnect interrupts the process, the old data is still intact at its original location. With either filesystem, you might lose the file that was being written, but the filesystem itself stays intact.

exFAT and FAT32 have no journal. A disconnect during a structure update can leave the entire filesystem in a broken state. Files might disappear, folders might become unreadable, or the drive might refuse to mount entirely.

If your drive is formatted exFAT (common for drives shared between Mac and Windows), ejecting properly is even more important.

Physical damage to the drive

Modern drives handle sudden disconnection at the hardware level reasonably well. SSDs don’t have moving parts, so there’s no head crash risk. Hard drives park their read/write heads automatically when power is lost.

The bigger physical concern is the connector. Yanking USB cables repeatedly can wear out the port on both the drive and your Mac. USB-C connectors are more durable than older USB-A, but they’re not immune to wear.

Repeated unexpected disconnections can also affect SSD firmware. The drive’s controller has to perform recovery operations after each ungraceful shutdown, which adds write cycles and complexity.

The cumulative effect

A single unplanned disconnect is unlikely to cause catastrophic damage. The journaling in modern filesystems handles it, and drives are built to tolerate it.

The problem is when it becomes a habit. Each time you skip ejecting, you’re rolling the dice on whether the write cache is empty, whether the filesystem was updating, and whether everything will be consistent when you reconnect.

Over dozens or hundreds of improper disconnections, the odds of something going wrong increase. Small inconsistencies accumulate. Files develop subtle corruption that doesn’t show up until you try to open them weeks later.

Just eject the drive

The safe path is obvious: always eject. But the reason people skip it isn’t laziness. It’s that ejecting fails so often on macOS. You try to eject, get told the disk is “in use,” and you don’t know why or what to do about it.

Ejecta removes the reason people skip ejecting in the first place. When your drive won’t eject, it tells you exactly what process is blocking it and lets you quit that process in one click. The whole thing takes a few seconds instead of becoming a research project.

Ejecting your drive properly is one of those small habits that prevents rare but painful data loss. Make it easy to do the right thing, and you’ll do it every time.