When Photoshop crashes or closes abruptly, orphan temporary scratch files remain locked on your storage drive, consuming tens or hundreds of gigabytes of space. If the application refuses to launch because your startup drive is completely full, you must delete these temp files manually directly from the operating system directory. Purging orphan temp files while Photoshop is fully closed is entirely safe and instantly reclaims your drive space.
Fast-Fix: The 45-Second Solution
If Photoshop won’t open due to full scratch disks, you can safely clear temp files directly from your system directory while the app is closed. On Windows, navigate to
%TEMP%and delete files namedPhotoshop TempXXXXXXXX. On macOS, search/tmpor your user Cache folder forPhotoshop Tempfiles and move them to Trash, then reboot.
Quick Status Snapshot
- Severity Tier: High (Prevents Photoshop from initializing and locks up system storage)
- Project Risk: Low risk to original source files; high risk of losing unsaved state changes from the crashed session
- Root Cause: Abandoned swap space allocations (
Photoshop Tempfiles) left behind after an improper application shutdown or system crash - Rare Cause: Background process hanging (
Photoshop.exeghost process) holding an active file lock on temporary data
Low-Friction vs. High-Friction Scenarios
Determining how to purge your temp files depends on your system’s current operational state:
- Scenario A: Photoshop crashed during a heavy edit and will not reopen because the primary drive has 0 KB of free space.
This is the most common low-friction recovery scenario. Photoshop created multi-gigabyte temp files during your session, crashed before it could run its automatic deletion routine, and left those files taking up space on your hard drive. Since the app is closed, deleting these files manually instantly resolves the space bottleneck. - Scenario B: Photoshop is closed, but Windows or macOS reports that the file is “In Use” when you try to delete it.
This is a high-friction scenario caused by a hung background process. Even though the main Photoshop interface is closed, a background service likeAdobe IPC Broker,node.exe, or a ghostPhotoshop.exethread is still running in memory, holding a lock on the temp file handle. - Scenario C: Your drive is full, but you cannot find any files named “Photoshop Temp” in the standard user folder.
This occurs when custom scratch disk paths were defined on secondary internal drives, or when macOS redirects temporary system handles into protected system paths like/private/var/folders/.
Service-Level Mechanism
To understand why Photoshop leaves these massive files behind, consider how the app handles document data. When working on high-resolution images, multi-layer PSDs, or Smart Objects, Photoshop quickly exceeds your available physical system RAM. To maintain performance, it uses your storage drive as virtual memory swap space, writing temporary data blocks into scratch files named Photoshop TempXXXXXXXX (where X represents a random string of hexadecimal numbers).
Think of your system RAM as a small workbench and your storage drive as a large warehouse next door. When the workbench gets cluttered, Photoshop moves temporary project pieces into the warehouse. When you close Photoshop normally, the application cleans up after itself, clearing out those temporary warehouse boxes before shutting down.
However, if Photoshop crashes, loses power, or is force-quit through Task Manager, the application never gets to run its cleanup routine. The heavy boxes remain sitting in the warehouse. The next time you try to launch Photoshop, it checks the warehouse for available space, finds it packed with old temporary boxes from the previous crashed session, and throws an error stating that the scratch disk is full before the user interface even loads.
Probability Breakdown
| Root Cause | Frequency | Operational Context |
|---|---|---|
| Orphan Temp Files from Prior Crashes | 70–75% | Photoshop terminated abnormally due to OS updates, plug-in faults, or power loss. |
| Ghost Process File Locks | 15–20% | Photoshop.exe or background Adobe sync tools remain active in system memory after closing. |
| Hidden Path Redirection (macOS / Custom Drives) | 5–10% | Temp files written to secondary scratch drives or hidden system directories. |
Escalation Variables
Several factors influence how fast and large these temporary files grow:
- Heavy Generative Fill and AI Tool Usage: Using AI Neural Filters or Generative Fill generates massive cached state layers in the temp file. For a deep dive on why AI tools balloon file sizes, read Why Your Scratch Disk Fills Up Instantly When Using Generative Fill.
- High Document Bit Depth: Working in 16-bit or 32-bit color modes quadruples the memory required for every undo state compared to standard 8-bit mode. Learn more about color depth impact at Why “Bit Depth” is the Secret Culprit Behind Scratch Disk Crashes.
- Automatic Recovery Backups: Short auto-save recovery intervals continuously write project state snapshots into your temporary folder, increasing disk bloat during long sessions. See Why “Automatically Save Recovery Information” Bloats Your Scratch Disk.
The Cost of Delay: Immediate → Next Session
Leaving orphan temp files unaddressed creates compounding system performance problems:
[Session 1: Photoshop Crashes]
│
▼
[Orphan Temp Files Remain on Drive] ──► Storage drops below minimum OS threshold (10–20 GB)
│
▼
[Session 2: "Scratch Disk Full" Error] ──► Photoshop refuses to launch or initialize workspace
│
▼
[System OS Instability] ──► Pagefile swapping fails, leading to OS freezes or slow boot times
Diagnostic Contrast (Differential Diagnosis)
It is important to distinguish orphan temp files from other types of storage bloat:
- Orphan Photoshop Temp Files (This Scenario): Large files named
Photoshop TempXXXXXXXXlocated in%TEMP%or/tmpthat linger after Photoshop is fully closed. Safe to manually delete. - Active Scratch Disk Bloat: Large temp files that exist while Photoshop is actively running. Deleting these will instantly crash the app and corrupt your open work.
- Persistent Cache Files: Media Cache, Camera RAW cache, and Font caches stored in
AppData\Roaming\Adobeor~/Library/Caches/Adobe. These require separate purging routines. To identify specific file types, refer to How to Identify Which .tmp Files Belong to Photoshop. - General Scratch Disk Full Errors on Launch: If clearing temp files does not resolve launch failures, you may need to bypass startup checks using key commands. See The “Ctrl+Alt” Shortcut: Changing Scratch Disks During Launch.
What To Do Right Now
If Photoshop will not open and your drive is full, perform these three immediate steps:
- Verify Photoshop is Closed: Press
Ctrl+Shift+Esc(Windows) orCmd+Option+Esc(macOS) to ensure no instances of Photoshop are running in the background. - Open System Temp Directory: On Windows, press
Win+R, type%TEMP%, and press Enter. On macOS, open Finder, pressCmd+Shift+G, type/tmp, and press Enter. - Delete
Photoshop TempFiles: Look for files starting withPhotoshop Tempand delete them. Empty your Recycle Bin or Trash to immediately reclaim disk space.
Hard-Stop Failure Signals
Stop manual file deletion and run system diagnostics if you encounter these technical warning signs:
- Persistent “File in Use” Warnings After Rebooting: Indicates a deeper operating system file lock or corrupt drive index table.
- SSD Read/Write Errors During Deletion: File system corruption or SSD NAND controller failure blocking file deletion calls.
- Primary Drive Below 1 GB Available Space: Operating system services may fail to execute basic deletion commands due to virtual memory exhaustion.
The Professional Recovery Sequence
Follow this step-by-step procedure to safely locate, identify, and clear Photoshop temporary files without launching the application.
Step 1: Terminate All Adobe Background Services
Before deleting any temporary files, you must ensure that no Adobe background threads are holding active file handles.
- On Windows 11 / 10:
- Right-click the Taskbar and select Task Manager.
- Click the Details tab.
- Locate
Photoshop.exe. If present, select it and click End Task. - End any instances of
Adobe IPC Broker.exe,CCXProcess.exe, orCoreSync.exe.
- On macOS (Sequoia / Sonoma):
- Open Activity Monitor from Applications > Utilities.
- Search for
Photoshopin the top-right search box. - Select any running processes, click the X button in the top toolbar, and choose Force Quit.
Step 2: Navigate to the Temporary Directory
For Windows Users:
- Press
Win + Ron your keyboard to open the Run dialog box. - Type
%TEMP%and hit Enter. This opens your local user temporary folder (typically located atC:\Users\<Username>\AppData\Local\Temp). - Sort the folder contents by Name or Size.
For macOS Users:
- Open Finder.
- Press
Cmd + Shift + Gto bring up the Go to Folder window. - Type
/tmpand press Enter. (If no files appear here, repeat the step and navigate to/private/var/folders/or~/Library/Caches/TemporaryItems/).
Step 3: Identify and Delete Photoshop Temp Files
- Look for files using the standard Photoshop naming pattern:
Photoshop TempXXXXXXXX(whereXis a random sequence of numbers and letters)PSTempXXXXXXXXPhotoshop AutoRecoverfolders containing orphaned session backups
- Verify the Date Modified timestamp. If the timestamp corresponds to a past session or crash, the file is orphaned.
- Select the files and press
Shift + Delete(Windows) orCmd + Delete(macOS) to remove them. For more details on safely removing these files, check How to Safely Delete Photoshop TempXXXXXXXX Files.
Step 4: Empty System Trash and Restart
- Right-click your Recycle Bin or Trash and select Empty. Space is not reclaimed by the operating system until this step is completed.
- Relaunch Photoshop. The application should now initialize normally without displaying the “Scratch Disk is Full” prompt.
- If errors persist after clearing temp files, you may need to reset application preferences as outlined in How to Reset Photoshop Preferences to Fix Persistent Disk Errors.
Required Resource Allocation
To prevent temporary files from locking up your operating system in future sessions, ensure your hardware meets these storage parameters:
- Primary System Drive Overhead: Maintain a minimum of 20% free space (or 50–100 GB absolute minimum) on your operating system drive at all times.
- Secondary Scratch Drive: Assign a dedicated secondary high-speed NVMe SSD exclusively for Photoshop scratch space to prevent OS drive overflow. Read more on secondary drive setups at Using an External Thunderbolt 5 SSD as a Scratch Disk.
- Automated Cleanup Scripts: Workstations prone to frequent crashes can use automated scripts to clear stale temp files on system startup. Learn how to set this up at How to Auto-Purge Photoshop Cache Using a Custom Script.
Combined Symptom Escalators
If clearing temp files does not fully restore application functionality, review these related troubleshooting guides:
- Temp Files Cleared + Scratch Disk Still Full: If your drive shows hundreds of gigabytes free but Photoshop still reports full disks, see Why “Scratch Disk is Full” Appears Even with 500GB Free Space.
- Temp Files Cleared + App Fails to Initialize: If Photoshop displays initialization errors immediately after splash screen loading, consult Fixing Photoshop Error: Could Not Initialize Because Scratch Disks are Full.
Final Render
Clearing Photoshop temp files without opening the application is a safe and effective way to recover lost disk space after a crash. By closing all background Adobe processes, navigating directly to your operating system’s temporary directory (%TEMP% on Windows or /tmp on macOS), and purging orphaned Photoshop TempXXXXXXXX files, you eliminate the storage block preventing the app from launching. Clear your temp files, empty your system Trash, and set up a secondary scratch disk to keep your Photoshop workflow fast and stable.