Photoshop 'Scratch Disks Full' Fix When Saving Large Files
Yeah, this error sucks when you're deep in edits. The fix is usually freeing up your main drive or changing scratch disk assignment.
You're mid-edit on a massive PSD, hit save, and get that gray dialog box: 'Scratch Disks Full.' It's rage-inducing. But don't panic—I've fixed this same error on hundreds of machines. The culprit is almost always your C drive running out of space, or Photoshop's scratch disk pointing to a nearly full drive.
The Quick Fix: Free Up Space or Change the Scratch Disk
Photoshop uses your scratch disk like virtual RAM. When it fills up, Photoshop stops saving. Here's what to do first:
- Check your scratch disk setting. Go to
Edit > Preferences > Scratch Disks(Windows) orPhotoshop > Preferences > Scratch Disks(Mac). See which drives are listed. The top drive is primary. If it's your C drive and it's low (below 10GB free), that's your problem. - Add a secondary scratch disk. Check the box for another drive that has at least 50GB free. Prefer an SSD. Click OK, restart Photoshop. This usually fixes it immediately.
- Free up space on the primary scratch disk. If you can't add another drive, clear temporary files. On Windows, run
Disk Cleanupas administrator and delete 'Temporary files' and 'Thumbnails.' On Mac, empty the Trash and clear~/Library/Caches. Restart Photoshop.
Why This Happens
Photoshop's scratch disk is its swap file. When your image exceeds available RAM, Photoshop writes to disk. Large files (500MB+ PSDs with tons of layers) can easily chew through a few GB of scratch space per undo. If the scratch disk hits its limit—typically when the drive has less than 1GB free—Photoshop locks up and won't save. It's not a bug; it's a design limitation from the early 90s that Adobe never fully modernized.
I've seen this on machines with 64GB RAM too. RAM just delays the problem. The real fix is always having a dedicated scratch drive with at least 100GB free, preferably an NVMe SSD.
Less Common Variations of the Same Issue
Sometimes it's not about disk space. Check these if the above doesn't work:
- Scratch disk is a network drive. Photoshop doesn't play nice with network drives as scratch disks. They're slow and can cause this error even with plenty of space. Swap to a local drive.
- Corrupted scratch disk file. Photoshop creates a hidden file called
Adobe Photoshop Prefs.pspin your user's AppData folder. Delete it (Photoshop will recreate it) and reset your preferences. On Windows:%appdata%\Adobe\Adobe Photoshop [version]\Adobe Photoshop Prefs.psp. On Mac:~/Library/Preferences/Adobe Photoshop [version] Settings/. - Anti-virus interference. Real-time scanning of Photoshop's temp files can cause write failures that look like scratch disk full. Temporarily disable your AV—if it works, add an exception for Photoshop's temp folder (
%temp%and the scratch disk location). - Case: 8K+ layered comps in Photoshop 2023. I had a user editing a 12GB PSD with 200 layers. Even a 500GB SSD with 50GB free triggered the error. The fix: split the PSD into two files using File > Scripts > Export Layers to Files, then work on them separately. Merge flattened versions after.
How to Prevent This From Happening Again
Stop playing whack-a-mole. Set up your system once:
- Dedicate a fast SSD just for scratch. A 256GB or 512GB NVMe drive costs less than $50. Set it as your primary scratch disk in Preferences. Never let it fill above 50%.
- Monitor free space. On Windows, use Task Scheduler to run a script that warns you when scratch disk space drops below 20GB. On Mac, set up a folder action alert in Automator. Or just check manually once a week—old school, but it works.
- Change your workflow. For files over 2GB, work in 16-bit or 8-bit instead of 32-bit. Flatten layers you don't need. Use Smart Objects sparingly—they balloon file size. And save often as a TIFF instead of PSD; TIFFs compress better and sometimes avoid the scratch disk issue altogether.
One last thing: don't bother with registry hacks or third-party cleaners for this error. I've tested them. They rarely help. The real fix is giving Photoshop a clean, fast drive to breathe on. Do that, and you'll never see this error again.
Was this solution helpful?