Diagnosing Photoshop Stalls, Beach-Balling, and Scratch Disk Errors in Large-File Editing

The Problem: Large Files Stop Responding

When Photoshop freezes, shows a spinning beach ball (the macOS pinwheel cursor) or an hourglass on Windows, or displays a "Scratch disks are full" message during large-file editing, the cause is usually a resource bottleneck rather than a broken file. The useful takeaway is to check scratch disk space and graphics processor settings before assuming the workstation lacks power. These symptoms often appear when opening or saving high-resolution PSD or PSB files, applying filters, or running transforms on layered composites.

Recognizable Condition

The stall typically occurs during specific actions: opening or saving a large document, using brush tools, applying filters, or performing transforms. Performance degrades further as History States accumulate—each state stores a snapshot of pixels in RAM or on the scratch disk. If the primary scratch volume runs low on free space, Photoshop may pause or refuse to save. Random crashes with particular tools suggest a third-party plug-in conflict rather than a core resource issue.

Cause and Diagnostic Table

Condition	Likely Cause	How to Confirm
"Scratch disks are full" on open or save	Primary scratch volume lacks free space	Preferences > Scratch Disks shows a checked volume with low free space; save errors appear immediately
Slow filters, transforms, or brush strokes	GPU or graphics-processor acceleration issue	Responsiveness changes when "Use Graphics Processor" is toggled off and on
Gradual slowdown after edits	RAM, history, or cache pressure	System monitor shows high memory use and many History States
Random crashes with certain tools	Third-party plug-ins or extensions	Disabling plug-ins or launching in Safe Mode removes the crash

Ordered Checks

1. Reproduce on a copy. Duplicate the document and note its pixel dimensions, bit depth, and color mode. Large-file diagnostics consume significant time and disk I/O, so work on copies to avoid risking the original.
2. Check free space on every scratch volume. Open Preferences > Scratch Disks and confirm which volumes are checked. Compare the free space on each with the document's estimated size. If the startup disk is the only option and it is nearly full, that is the first constraint to relieve.
3. Review Preferences > Performance. Examine the RAM allocation, History & Cache settings, and Graphics Processor section. Note how much RAM is reserved for Photoshop and how many History States are configured.
4. Toggle "Use Graphics Processor" off and on. In Preferences > Performance, disable the option, restart Photoshop, and time the same operation on the same document copy. Re-enable it and repeat. A significant difference points to a GPU or driver issue.
5. Launch with plug-ins disabled or in Safe Mode. If the symptom disappears, a third-party plug-in or extension is implicated.
6. Test reset preferences only after backing up settings. Resetting removes custom workspaces, shortcuts, and presets. Export or back them up first, then reset and reapply settings incrementally to identify the corrupt preference.

Fixes Tied to Findings

Scratch Disk Space

If the scratch disk is full, free space on the volume or add a dedicated fast disk as a scratch volume and reorder the scratch disks so the fastest non-system disk is first. Do not delete scratch files while Photoshop is running; quit the application first, then remove only Photoshop temporary files from the scratch volume.

Graphics Processor Acceleration

If GPU acceleration is the cause, update to a certified GPU driver for your installed Photoshop version. If instability remains, disable "Use Graphics Processor" for stability. GPU acceleration can help some operations but may destabilize specific drivers, so test before enforcing it in a production pipeline.

RAM, History, and Cache

If RAM or history pressure is the issue, lower the number of History States and choose cache levels and tile size appropriate for the document type. Avoid allocating all available RAM to Photoshop; leave headroom for the operating system and other applications.

Plug-ins and Preferences

If a plug-in is implicated, remove or update the offending item. If preferences are corrupt, reset them and reapply settings incrementally. Because resetting preferences changes state, back them up before proceeding.

Concrete Diagnostic Decision

When comparing two documents, use this decision point: if the same filter operation stalls on a layered 4 GB PSD but completes quickly on a flattened copy of identical pixel dimensions, the bottleneck is likely history states and layer data rather than GPU compute. Conversely, if the flattened copy also stalls, suspect scratch disk space or GPU acceleration first.

Escalation Criteria

Escalate the issue when it persists after scratch disk, GPU, plug-in, and preference-reset checks; when it reproduces across multiple documents or machines; when it involves file corruption or data loss; or when it starts after a specific Photoshop, OS, or GPU driver update. When escalating, include the exact Photoshop build, OS build, GPU model and driver version, file characteristics, and reproduction steps.

Limitations and Verification

Menu names and defaults vary by Photoshop version and operating system. GPU APIs and driver requirements change between releases, and scratch-disk behavior differs for very large documents and PSB files. Verify settings against the installed version's Help documentation before changing production workflows.

To check the result after making changes, save and reopen a test PSD or PSB file. Confirm that layer and filter rendering appear as expected and that the previously stalling operation completes without the scratch disk error or unresponsive interface.