'Can't Write to Disk' on Mac? Here's the Fix

You finish editing a file and hit Save. macOS pushes back: “The document could not be saved. The file system could not write to the disk.” Or you try to copy something to an external drive and Finder says “Can’t write to disk.” Or Photoshop bombs out mid-export with a similar message. The disk has 200 GB free, you’ve been using it all morning, and now it refuses to accept any new data.

This error has half a dozen distinct causes. The visible symptom is the same; the fix depends entirely on which one you’ve got.

The exact errors and what they mean

Variants you might see:

• “The file system could not write to the disk.”
• “The disk is write-protected.”
• “Disk could not be written. Make sure the disk is not full or write-protected.”
• “Read-only file system.”
• “You don’t have permission to save the file in the folder .”

They all map to one of these underlying problems:

1. The disk is mounted read-only — macOS or the filesystem decided this volume should not accept writes.
2. You don’t have write permission for the destination folder.
3. The disk is full even though Finder may show free space.
4. The disk has hardware errors and the filesystem went read-only as a safety measure.
5. Locked file — the specific file you’re trying to overwrite is flagged locked.
6. A process holds an exclusive lock on the file or path.

Quick checks that resolve the easy cases

1. Verify the disk has actual free space

Apple menu → About This Mac → More Info → Storage. Wait for the bar to populate. If you’re under 5% free, swap and temp files have nowhere to go and writes fail.

For external drives: Get Info → check Capacity, Available, Used. Storage above 95% on APFS or HFS+ Journaled causes write failures even when space technically exists.

2. Check if the disk is mounted read-only

Get Info on the volume → look at “Permissions” or “Sharing & Permissions” at the bottom. If it says “You can only read,” the volume is read-only.

In Terminal:

mount

Look for the volume in the output. (read-only) means it’s mounted read-only by the system.

Common reasons a volume mounts read-only:

• It’s an NTFS volume and macOS can’t write NTFS natively.
• The previous unmount was unclean and the filesystem is in a recovery state.
• It’s a sealed Apple System volume — by design, can’t be modified.
• The drive’s hardware write-protect switch is engaged (some external SSDs).

3. Restart the Mac

Releases stuck file handles, clears launchd state, may force a remount. Five-minute fix; try it.

Free up disk in one clickMany errors stem from a full startup disk. Sweep finds gigs of cruft fast. Get Sweep free →

Fix permission denials

If the error says “you don’t have permission”:

1. Get Info on the destination folder.
2. Scroll to Sharing & Permissions at the bottom.
3. Click the lock, authenticate.
4. Make sure your user has Read & Write.
5. If your user isn’t listed, click the + and add yourself.

For external drives that move between machines, also check Ignore ownership on this volume in Get Info. That setting is a one-time toggle that grants any logged-in user read/write to the whole volume — appropriate for a personal backup drive, not for a shared multi-user system.

Sometimes deeper folders inherit broken permissions. To re-apply permissions recursively:

1. Get Info → click the lock.
2. Click the gear menu → “Apply to enclosed items.”
3. Confirm.

This propagates the visible permissions down through the folder tree.

Fix NTFS volumes that can’t be written

If the drive is NTFS-formatted (used to be in a Windows machine), macOS will mount it read-only by default. Three options:

1. Reformat to ExFAT if you don’t need to preserve the data — works on Windows and Mac with read/write. Disk Utility → Erase → Format: ExFAT.
2. Reformat to APFS if you’ll only use it on Macs.
3. Install third-party NTFS support. Tuxera NTFS, Mounty, Paragon all add NTFS write support to macOS. Each has trade-offs around stability and performance.

Reformatting destroys the data on the drive. Copy off first via the read-only mount.

Repair a filesystem that went read-only

If a previously writable volume is now read-only and you didn’t change anything:

1. Eject the volume (or unmount it via Disk Utility).
2. Reconnect or remount.
3. Disk Utility → First Aid on the volume. Let it complete fully.
4. If First Aid completes successfully, try writing again.

If First Aid fails or reports unfixable errors:

diskutil verifyVolume /Volumes/<name>

The detailed output identifies the specific corruption. For HFS+ Journaled volumes, sometimes:

diskutil enableJournal /dev/disk2s2

restores write capability if journaling was disabled.

For APFS volumes that won’t repair, your options are: restore from backup and reformat, or attempt rescue with specialized tools (Disk Drill, DiskWarrior). Don’t keep writing to a volume that’s failing repair.

Unlock a file flagged as locked

If a specific file refuses to overwrite:

1. Get Info on the file → uncheck Locked.
2. Or via Terminal: chflags nouchg /path/to/file.

If the locked flag won’t unstick, it’s because some app has the file open. Close everything that touches the file, restart, try again.

Find a process holding the file

In Terminal:

lsof /path/to/file

Lists every process with that file open. Kill the offending one with Activity Monitor or kill -9 <pid>. The next save attempt usually succeeds.

For “can’t save” errors that appear in apps that should own their own files (e.g., Photoshop saving its own .psd), the issue is often a Cloud sync client (Dropbox, OneDrive) holding a lock on the file mid-sync. Pause sync, save, resume sync.

Skip the manual huntSweep clears the cruft that triggers most of these errors — caches, logs, leftover daemons. Download Sweep free →

When the system volume itself is the problem

If you can’t save to your Documents folder or Desktop, something is wrong with your home folder, not an external drive.

1. Check disk space first. A full startup disk fails writes for everyone.
2. Check FileVault status. System Settings → Privacy & Security → FileVault. A FileVault encryption-in-progress slows writes dramatically; some apps time out.
3. Repair the system volume. Boot into Recovery Mode (Apple Silicon: hold power, choose Options; Intel: Cmd+R) → Disk Utility → First Aid on the Macintosh HD volume.
4. Look for runaway logs. ~/Library/Logs/DiagnosticReports/ and /Library/Logs/ can grow huge if a process is in a crash loop. Delete old logs to free space.

Specific scenarios

”Cannot save” in a specific app only

The app’s data path may be wrong. Check the app’s preferences for save location — it may be pointing at a now-disconnected external drive. Reset the path to a writable location.

Time Machine destination won’t write

Time Machine drives that fill or develop minor errors mark themselves read-only. Disk Utility → First Aid; if that fails, you need a fresh Time Machine destination. The history on a borked Time Machine drive is often unrecoverable.

iCloud Drive folder won’t accept writes

Sign out of iCloud (System Settings → your name → iCloud → Drive → toggle off, choose “Keep a Copy”). Sign back in. The local cache rebuilds, write capability returns.

”Read-only filesystem” inside a Terminal command

You’re trying to write to /System/... or other protected paths. macOS has system-protected paths that even root can’t modify when SIP (System Integrity Protection) is on. The right answer is to write somewhere else, not to disable SIP.

When the drive is failing

If write errors are spreading across files, repeated First Aid passes don’t help, and the drive is also slow to read, the drive is failing.

• Disk Utility → View → Show All Devices → click the physical drive → check S.M.A.R.T. status. “Failing” means replace now.
• Listen for clicking from spinning drives. That’s mechanical failure.
• Check Console.app for I/O errors. Search “I/O error” — patterns of failed reads/writes from kernel logs are diagnostic.

Back up everything you can off the drive, then replace it. Continued use risks losing what’s still recoverable.

Prevent the error from coming back

• Eject external drives properly before unplugging.
• Run First Aid monthly on important external drives.
• Keep at least 15% of your startup disk free.
• Don’t run cloud sync clients on volumes near capacity.
• For NTFS drives that move between Windows and Mac, reformat to ExFAT once and stop fighting macOS.

The “can’t write to disk” error is generic, but the underlying causes are specific and individually fixable. Walk through the list, identify which case applies, and the fix is rarely more than five minutes away.