Working on large Photoshop projects can be creatively rewarding, but at some point, many designers and digital artists encounter the dreaded “scratch disks are full” error. This issue is more than a nuisance—it can bring your workflow to a screeching halt at the worst possible moment. Understanding why it happens and how to fix it can save hours of frustration and missed deadlines.
TLDR:
When exporting large PSD files or working with heavy layers and filters, Photoshop can quickly consume the temporary storage it uses, called a “scratch disk.” This often causes crashes or error messages about full scratch disks. Cleaning up unused files, freeing up drive space, and managing Photoshop’s preferences to use multiple disks helped keep my project workflow running smoothly. Understanding and optimizing scratch disk usage became crucial to completing large design jobs on time.
What is a Scratch Disk and Why Does Photoshop Use It?
Photoshop requires a vast amount of temporary space to process large files, render previews, and apply complex effects. When your computer runs out of physical RAM, Photoshop uses your hard disk space instead—this is known as a scratch disk.
By default, Photoshop assigns your primary operating system drive (usually the C: drive on Windows or Macintosh HD on macOS) as the scratch disk. If that drive runs low on space—or if your project file balloons into multiple gigabytes—Photoshop can quickly exhaust available scratch space.
That’s when the dreaded error pops up:
“Could not complete your request because the scratch disks are full.”
This message can prevent you from saving, exporting, or even continuing to work on your file.
When the Problem Began
I encountered the issue midway through exporting a series of high-resolution PSD files for a multi-part client branding package. Each export included dozens of layers, multiple smart objects, and applied filters. The files averaged 2GB in size, with some ballooning near 5GB.
Suddenly, Photoshop began failing to export. Attempts to merge layers or save versions of the file were blocked. I’d close other programs, reboot, and try again—only to be met again with the same scratch disk error.
Diagnosing the Real Issue
I dug into some of the system diagnostics and discovered more than just a Photoshop bug. Over time, my main drive had accumulated:
- Unwanted cache files
- Archived PSD versions from past projects
- Installer leftovers and unused application data
My main drive had dipped below 10GB of free space. For large files with history states, cache previews, and autosaves turned on, that simply wasn’t enough. Photoshop was effectively choking on its own workspace.
Multi-Disk Strategy: Cleaning & Configuring
To put an end to these interruptions once and for all, I used a two-part approach: cleaning up system disks and assigning multiple scratch disk locations in Photoshop.
1. Cleaning System Drives
Here were the key steps I followed to reclaim storage space:
- Deleted old PSDs: Archived large files I hadn’t touched in over a year to an external backup drive.
- Emptied caches: Cleared temp files and system cache on both Windows and macOS (depending on which system I was using).
- Removed unused Adobe files: Deleted Adobe Camera Raw caches, plugin logs, and crash reports.
- Utilized disk cleaning tools: On Windows I used Disk Cleanup, and on macOS, I turned to CleanMyMac X to sort through junk files.
Clearing about 75GB from my primary drive gave me immediate breathing room—but that was just the start.
2. Assigning Additional Scratch Disks
You can assign additional drives as scratch disks in Photoshop. Here’s how I did that:
- Opened Photoshop Preferences.
- Navigated to Performance.
- Clicked on Scratch Disks.
- Selected an additional SSD with over 200GB free space.
This allowed Photoshop to offload temporary data far more efficiently.
By distributing the load across my primary internal SSD and a fast external Thunderbolt SSD, export times improved and the frequency of scratch disk errors dropped to zero.
Other Tips That Helped
Along with the disk cleanup, I also adapted a few key practices for long-term success:
- Split massive PSDs: Instead of a single 6GB file, I broke projects into modular parts.
- Limit history states: Reduced the number of undo history states in preferences from 100 to 20.
- Turned off auto-save: In projects I controlled tightly, disabling auto-save cut down temp data creation.
- Exported in batches: Rather than exporting all assets at once, I staggered the process to reduce memory load.
Conclusion: Prevention Is Better Than Panic
Scratch disk errors can feel like a technical mystery, but they typically come down to one thing: disk space. Once the underlying issue is resolved with both practical cleanup and optimized settings, Photoshop becomes vastly more stable—even when handling complex projects.
In my case, a combination of disk audits, custom export workflows, and proper scratch disk settings helped me complete my project on time—and without another crash. If Photoshop is central to your work, taking time to manage these aspects could mean fewer headaches and smoother deadline execution.
Frequently Asked Questions (FAQs)
-
Q: Can I use an external hard drive as a scratch disk?
A: Yes, you can. Just make sure it’s formatted in a format compatible with your OS (exFAT for cross-platform or APFS/HFS+ for macOS). SSDs are preferred for speed. -
Q: How much free space should I keep on my scratch disk?
A: Adobe recommends at least 20GB of free space, but for large project work, keeping 100GB or more is safer. -
Q: Do temporary Photoshop files delete automatically?
A: Not always. Photoshop *does* clean them up on a normal shutdown but may leave temp files behind after a crash. -
Q: What’s the difference between RAM and scratch disk?
A: RAM is temporary memory while you’re working. Scratch disks serve as overflow storage when RAM fills up—acting as virtual memory. -
Q: Can increasing RAM solve the problem?
A: It can help! More RAM reduces scratch disk reliance. But disk cleanup and management are still necessary in most large project scenarios.