Photoshop crashes always feel sudden.

One second you’re retouching a product shot, cleaning up a mask, or trying to save a layered PSD. The next second Photoshop freezes, disappears, throws a scratch disk warning, or gives you that awful feeling that the last ten minutes of work may or may not still exist.

But most Photoshop crashes aren’t as random as they look. The cause usually leaves clues.

“Photoshop crashed” can mean a lot of different things. Maybe the app crashes on startup. Maybe it opens fine, then freezes when you use the Type Tool. Maybe the canvas turns black, the file won’t save, Generative Fill stalls, or Photoshop gets slower and slower until it finally gives up. Those are different problems, and they usually need different fixes.

That’s why I don’t think the best answer is just “restart Photoshop” or “purge everything” and hope for the best. Sometimes that works. Often, it only buys you another 20 minutes before the same issue comes back.

This guide is a practical troubleshooting path for common Photoshop problems and crashes. We’ll look at updates, GPU issues, scratch disks, preferences, fonts, plugins, file pressure, and the point where your local machine may simply be the wrong place to keep pushing a heavy Photoshop project.

And yes, we’ll also talk about when Vagon Cloud Computer makes sense. Not as a magic fix for every Photoshop problem, because it isn’t. But when crashes are tied to hardware limits, slow storage, weak GPUs, or large files that keep outgrowing your setup, moving the work to a stronger cloud computer can be the cleanest fix.

#1. Start with the crash pattern

Before changing settings, uninstalling plugins, or blaming your computer, try to answer one boring question:

When does Photoshop actually crash?

I know. Not exciting. But this is the part people skip, and it’s usually the part that saves the most time.

A Photoshop crash on startup is not the same as a crash while saving a 4 GB PSD. A freeze when you open the Type Tool points in a different direction than a black canvas after switching to GPU-accelerated features. If Photoshop crashes only when you use Generative Fill, that’s another clue. If it only happens with one file, that’s a very different story from every file crashing.

I’d start with a small crash note. Nothing fancy. Just write down:

• Your Photoshop version

• Your operating system version

• Whether the crash happens on launch, open, save, export, or while using a specific tool

• The file size and file type

• Whether the issue happens with one file or every file

• Any recent changes, like a new plugin, font, GPU driver, OS update, or Photoshop update

This gives you a pattern instead of a panic.

For example, if Photoshop crashes every time you open one specific PSD, the file may be damaged, too heavy, or full of problem layers. If Photoshop crashes when you select text, fonts become suspicious. If the canvas flickers, goes black, or tools lag visually, the GPU moves higher on the list. If the error mentions scratch disks, don’t waste an hour reinstalling Photoshop before checking storage.

A useful quick test is to create a new blank Photoshop file and do a few basic actions: paint, add text, save, export, open Camera Raw if you use it, and try the tool that usually causes trouble.

If the blank file works fine, the issue may be tied to the original file, its assets, its fonts, or its size. If even the blank file crashes, the problem is probably broader: preferences, GPU, plugins, disk space, system permissions, or the Photoshop install itself.

Also pay attention to slowdowns before the crash. Photoshop often gives warnings before it fails. Brushes lag. Zooming stutters. The cursor hangs. Saving takes longer than usual. Smart Objects open slowly. A plugin panel stops responding. These little signs matter.

The goal here is not to diagnose everything in one minute. The goal is to stop treating every crash like the same problem.

Once you know the pattern, the fixes become much less random.

#2. Update Photoshop and your system

Updates are boring until they fix the exact crash you’ve been fighting for two days.

Photoshop crashes can come from bugs in the app itself, bugs in your operating system, GPU driver conflicts, Camera Raw issues, or weird behavior between Photoshop and another Adobe component. So yes, checking for updates is a reasonable early step.

But I’d add one warning: don’t treat updates like a magic button.

If you’re in the middle of a client delivery, a campaign deadline, or a production file that already behaves strangely, updating everything five minutes before export can create a new problem. I’ve seen people “fix” one crash and then discover that a plugin no longer works, a panel changed, or a file behaves differently in the new version.

Here’s the practical version.

Open the Creative Cloud app and check whether Photoshop has an update available. Also check whether Camera Raw needs an update, especially if your crashes happen around RAW files, smart filters, or photography workflows.

Then check your operating system updates. You don’t always need to install every major OS upgrade immediately, but security patches and compatibility updates can matter. Photoshop leans on system-level graphics, storage, permissions, fonts, and file handling more than people realize.

If Photoshop started crashing right after an update, don’t assume the update was “bad” right away. First test a blank file, then test an older file, then test the exact file that crashed. If only one file breaks, the file may be the issue. If everything breaks after the update, the new version, preferences, GPU driver, or plugin compatibility becomes more suspicious.

One habit I like: keep the previous Photoshop version installed for a little while if your workflow is important.

Creative Cloud usually lets you manage installed versions, and having the last stable version available can save you when a new build doesn’t play nicely with your files, plugins, or machine. This is especially useful for studios, freelancers, and anyone working with repeatable production workflows.

A clean update check should cover:

• Photoshop version

• Camera Raw version

• Creative Cloud app version

• Operating system updates

• GPU driver updates

• Plugin compatibility

• Whether the crash started before or after the update

If updating fixes the crash, great. Take the win.

If it doesn’t, at least you’ve removed one of the obvious variables. That makes the next checks much cleaner, especially GPU and scratch disk troubleshooting.

#3. Fix GPU and driver issues

Photoshop uses the GPU for more than people think.

Zooming, panning, canvas display, some filters, Camera Raw features, Neural Filters, certain 3D or perspective workflows, and newer AI-assisted features can all lean on graphics acceleration in different ways. So when the GPU setup gets messy, Photoshop may not always crash in a clear, dramatic way.

Sometimes you get a black canvas. Sometimes the image flickers. Sometimes tools lag even though the file is not that large. Sometimes Photoshop freezes when you open a specific panel or use a GPU-heavy feature. And sometimes it just closes.

Very helpful. Thanks, Photoshop.

The first thing I’d check is whether the problem looks visual. If the file opens but the canvas is black, transparent areas render strangely, zooming feels broken, or brush strokes appear late, the GPU should be near the top of your list.

Start with the simple test inside Photoshop:

Go to Preferences > Performance and look for Use Graphics Processor.

Turn it off temporarily, restart Photoshop, and test the same file again. If the crash or black canvas disappears, you’ve probably found a GPU-related issue. That doesn’t always mean your GPU is bad. It might mean the driver is outdated, the GPU is unsupported, Photoshop is using the wrong graphics device, or a recent driver update created a conflict.

If turning off the GPU helps, update your graphics driver next.

On Windows, don’t rely only on the generic driver that Windows installs automatically. Get the current driver from NVIDIA, AMD, or Intel, depending on your GPU. For NVIDIA cards, Studio Drivers are often a better choice for creative apps than Game Ready Drivers. Not always, but often.

On macOS, GPU drivers come through system updates, so your update path is different. You’re usually looking at macOS updates, Photoshop updates, and whether your Mac has enough graphics memory for the kind of work you’re doing.

After updating, turn Use Graphics Processor back on and test again. If Photoshop behaves, keep it on. If the crash returns, you may need to leave it off for that project or reduce GPU-heavy features until you can solve the driver or hardware issue.

Also check whether Photoshop is using the GPU you expect. This matters on laptops with integrated and dedicated graphics. If Photoshop is stuck on a weaker integrated GPU, heavy files, high-resolution displays, and AI features can feel much worse than they should.

Common GPU-related Photoshop symptoms include:

• Black or blank canvas

• Flickering image area

• Slow zooming and panning

• Brush lag that feels visual, not file-size related

• Crashes when using Camera Raw or Neural Filters

• Crashes after enabling GPU-heavy features

• Strange artifacts after moving or transforming layers

One thing I wouldn’t do too early is start flattening the PSD just because Photoshop is acting weird. If the crash is GPU-related, destroying your layer structure may not fix anything. You’ll just end up with a less editable file and the same unstable setup.

Test the graphics path first.

If Photoshop works with GPU acceleration off, you’ve learned something important. If it still crashes, move on. The next suspect is often much less glamorous: scratch disk space.

#4. Clear scratch disk problems

Scratch disk errors are Photoshop’s way of saying, “I need room to think.”

When Photoshop runs out of usable memory, it uses storage space as temporary working space. That storage is the scratch disk. Large PSDs, Smart Objects, high-resolution images, huge history states, AI-generated variations, and multiple open files can all push Photoshop into scratch disk territory very quickly.

And when that space runs out, Photoshop can slow down, freeze, fail to save, refuse to open files, or crash.

The classic error is scratch disks are full, but you won’t always get that exact message. Sometimes Photoshop just becomes painfully slow before the crash. Sometimes saving takes forever. Sometimes filters hang. Sometimes the file opens, but every action feels like it’s dragging a heavy bag behind it.

First, check how much free space you have on your main drive.

As a rough rule, I don’t like running Photoshop on a drive that’s nearly full. If your system drive has only a few gigabytes free, you’re asking for trouble. Heavy Photoshop projects can chew through temporary space much faster than expected, especially when you’re working with large canvases or layered files.

Then check Photoshop’s scratch disk settings:

Go to Preferences > Scratch Disks and see which drive Photoshop is using.

Ideally, use a fast internal SSD with plenty of free space. A slow external drive, almost-full system disk, network location, or cheap USB drive can make Photoshop feel unstable even when your CPU and GPU are fine.

A few practical fixes:

• Free up space on the scratch disk

• Empty trash or recycle bin

• Move old exports, downloads, and duplicate assets off the drive

• Restart Photoshop after clearing space

• Assign a faster drive as the scratch disk if you have one

• Avoid using slow removable drives for active scratch disk work

• Keep big project assets organized instead of scattered across random folders

Also look at file behavior.

If Photoshop only struggles with one huge PSD, the scratch disk may be reacting to file pressure, not causing it alone. A 12,000 px canvas with dozens of Smart Objects, high bit depth, linked files, masks, adjustment layers, and AI variations can create a lot of temporary data. Even if the saved PSD is “only” a few gigabytes, Photoshop may need much more working space while editing.

This is why scratch disk problems often feel confusing. The file opens yesterday. Today it crashes. Nothing changed, except now you have five more exported versions, more browser downloads, a nearly full drive, and a Photoshop temp file sitting somewhere quietly eating space.

Not dramatic. Just annoying.

If you’re on a laptop with limited storage, this becomes a regular maintenance problem. You can keep clearing space, but eventually you may hit a ceiling where the project is simply too heavy for the machine to handle comfortably.

That doesn’t mean you need to panic-buy new hardware. But it does mean scratch disk problems are a sign to look at the whole working setup: storage, RAM, file size, history states, Smart Objects, and whether the project should stay on that machine at all.

#5. Reset preferences carefully

Resetting preferences is one of those fixes that sounds too simple to be real.

And then, sometimes, it works.

Photoshop stores a lot of behavior in preference files: tool settings, panel positions, performance options, file handling choices, scratch disk behavior, type settings, plugin-related settings, and small bits of app state that most users never think about. When those preferences get corrupted, Photoshop can start acting strange in ways that don’t make much sense.

It might crash on launch. It might freeze when opening certain panels. Tools may behave oddly. Performance settings may not stick. A feature that worked yesterday may suddenly fail today for no clear reason.

Before you reset everything, though, slow down for a second.

If you have a carefully customized workspace, actions, brushes, presets, shortcuts, or color settings, don’t treat reset preferences like a harmless button. It can help, but it can also wipe out a setup you actually rely on. That’s especially annoying in production environments where the “little settings” are part of your muscle memory.

A cleaner approach is this:

• Save or export important presets first

• Note your current performance settings

• Take a screenshot of custom workspace layouts if needed

• Close Photoshop

• Reset preferences using Photoshop’s built-in reset option

• Reopen Photoshop and test the crash with a simple file first

• Then test the original file

In recent versions, you can usually reset preferences from Preferences > General > Reset Preferences On Quit. After you quit and reopen Photoshop, it starts with fresh preference files.

If Photoshop crashes on startup and you can’t reach preferences, you can use the keyboard shortcut method during launch. On many setups, holding Alt + Control + Shift on Windows or Option + Command + Shift on macOS while starting Photoshop prompts you to delete the settings file.

I’d use that method only when needed, because it’s easy to forget what settings you had before.

After the reset, don’t immediately reinstall every panel, load every old preset, and open the heaviest file you have. Test in layers. First a blank document. Then a normal file. Then the file that caused trouble. Then your plugins and presets.

That sequence matters.

If Photoshop works fine after resetting preferences, but starts crashing again after you reload a specific workspace, plugin, brush pack, or font setup, you’ve found a stronger clue. The problem probably wasn’t “Photoshop” in general. It was something inside the environment around Photoshop.

Preference resets are not glamorous, but they’re useful when the crash feels random, especially after updates, plugin changes, or long periods of carrying the same settings across versions.

If the crash survives a preference reset, the next suspects are often outside Photoshop itself: fonts and plugins.

#6. Check fonts and plugins

Fonts can crash Photoshop in surprisingly ugly ways.

That sounds dramatic, but if you’ve ever had Photoshop freeze when selecting the Type Tool, opening the Character panel, scrolling through fonts, or loading a PSD with missing typefaces, you know what I mean. A damaged font, a messy font cache, or a conflict with a font manager can make Photoshop feel broken even when the app itself is fine.

The clue is usually timing.

If Photoshop crashes when you touch text, change fonts, open a file with lots of type layers, or activate a new font family, start there. Don’t spend an hour adjusting GPU settings if the crash only happens around typography.

A practical font check looks like this:

• Disable recently installed fonts

• Test the same file again

• Clear or rebuild the font cache if needed

• Turn off third-party font managers temporarily

• Open Photoshop with only system fonts active

• Test the Type Tool in a blank document

If the crash disappears, bring fonts back slowly. Not all at once. I know that’s annoying, but adding 900 fonts back in one click tells you almost nothing.

Plugins are similar.

A plugin can be useful for years and then suddenly become the reason Photoshop won’t launch after an update. Retouching panels, export tools, old filters, color tools, AI extensions, asset managers, and automation scripts can all create instability if they’re outdated or poorly matched to your Photoshop version.

If Photoshop crashes on launch, try starting it without optional third-party plugins. If it becomes stable, add plugins back one by one until the crash returns.

This is tedious, yes. But it’s better than reinstalling Photoshop three times and still having the same plugin break it again.

Watch especially for plugins that:

• Haven’t been updated in a long time

• Were installed manually instead of through Creative Cloud or the developer’s installer

• Modify export, save, or file-open behavior

• Add panels that load automatically at startup

• Depend on older Photoshop APIs

• Create background sync or cloud asset behavior

The same logic applies to scripts, extensions, and old automation setups. If Photoshop crashes at the exact moment a panel loads, that’s not subtle. It’s telling you where to look.

I’d also be careful with “free plugin packs” from random places. Some are fine. Some are abandoned. Some work beautifully until a Photoshop update changes something small, then they become the mystery problem nobody remembers installing.

Fonts and plugins are easy to overlook because they don’t feel like part of Photoshop. But they live close enough to the app to cause real trouble.

If Photoshop still crashes after fonts and plugins are cleaned up, the issue may be less about the app environment and more about the file itself. That’s where file pressure comes in.

#7. Reduce file and memory pressure

Some Photoshop files don’t crash because Photoshop is broken.

They crash because the file is asking too much from the machine.

This usually happens slowly. You start with a normal PSD, then add a few Smart Objects, a couple of high-resolution product shots, some masks, adjustment layers, text, generated variations, maybe a few linked files, maybe three different “final” groups because nobody wants to delete anything yet. Suddenly the file is 3 GB, the history panel is packed, and saving feels like a small event.

At that point, every action costs more.

A large Photoshop file can pressure RAM, GPU memory, scratch disk space, storage speed, and save performance at the same time. So if Photoshop crashes only with one heavy project, don’t treat that the same as a clean startup crash.

Look for the usual file-pressure suspects:

• Oversized canvas dimensions

• Too many high-resolution Smart Objects

• Large linked files stored in slow locations

• Hidden layers that are no longer needed

• Dozens of unused AI-generated variations

• Too many open Photoshop documents

• Very high bit depth when the project doesn’t need it

• Huge history states

• Complex masks, filters, and adjustment stacks

I’d start by duplicating the file before cleaning anything. Never do file surgery on the only copy. Save a new version, then test what actually helps.

A few low-risk fixes:

• Close other open PSDs

• Save a separate cleanup copy

• Delete unused hidden layers

• Move old experiments into an archive PSD instead of keeping everything live

• Rasterize only the Smart Objects you truly don’t need to edit

• Reduce unnecessary history states

• Keep AI variations outside the main PSD when they’re just references

• Check whether the canvas size is much larger than the final output needs

This is where people sometimes go too far. They flatten everything, shrink the file, and technically solve the crash, but now the project is hard to revise. That’s not a great trade if the client asks for changes tomorrow.

The better goal is to reduce pressure without destroying editability.

For example, if you have 40 generated background options, you probably don’t need all 40 living as full layers inside the working PSD. Export the rejects or near-misses to a separate folder. Keep the original image. Keep the strongest options. Name the group clearly. Your future self will be less angry.

Smart Objects deserve the same kind of judgment. They’re useful, but they can make files heavy fast, especially when they contain large embedded images or nested PSDs. If a Smart Object is still part of the design system, keep it. If it’s just an old test layer nobody will edit again, archive or simplify it.

Also watch the save location.

A heavy PSD saved to a cloud-synced folder, network drive, external disk, or nearly full internal drive can behave worse than the same file saved to a fast local SSD. If Photoshop crashes during save, test a local save with a new filename. That one small test can separate a file problem from a storage or sync problem.

Memory pressure is not always visible until it becomes painful. Photoshop may still technically run, but every click gets slower. Then a filter hangs. Then the file won’t save. Then the app disappears.

That pattern usually means the project needs cleanup, more headroom, or both.

#8. Use Vagon Cloud Computer

Not every Photoshop crash means you need a stronger computer.

If Photoshop crashes because of a damaged font, a broken plugin, corrupted preferences, or one bad file, moving to another machine may only move the headache somewhere else. You still need to fix the actual cause.

But sometimes the cause is much simpler: the project has outgrown the computer.

You can feel it when it happens. The file opens, but slowly. Zooming and panning stutter. Saving takes forever. The scratch disk keeps filling up. GPU-heavy features behave inconsistently. AI-assisted edits create more variations than your laptop wants to carry. You spend more time managing the machine than working on the image.

That’s the point where Vagon Cloud Computer starts to make sense.

Instead of forcing a heavy Photoshop workflow through a lightweight laptop, Chromebook, older desktop, or storage-limited device, you can run Photoshop on a high-performance cloud computer and stream the workspace from your own device. The project gets more headroom for RAM, GPU power, and storage speed, while you keep working from wherever you are.

The best use cases are pretty clear:

• Large PSD files with many layers

• High-resolution retouching or compositing

• Heavy Smart Object workflows

• AI-assisted Photoshop projects with many generated variations

• Workflows that keep hitting scratch disk limits

• Projects that feel unstable on a lightweight laptop

• Remote work where you need the same Photoshop setup across devices

• Situations where buying a new workstation does not make sense yet

I’d think of Vagon Cloud Computer as a better working environment, not a crash repair button.

If your PSD is messy, it’ll still be messy. If a plugin is broken, it may still be broken. If a font file is damaged, you still need to replace it. But if the real problem is that your local machine doesn’t have enough performance headroom, moving the work to Vagon can remove a lot of friction at once.

It can also help before things get bad.

That’s the part people underestimate. You don’t need to wait until Photoshop crashes five times in an afternoon. If you already know the project will involve large files, lots of layers, client revisions, AI variations, or heavy exports, starting on Vagon Cloud Computer can be cleaner than moving everything later.

The practical test is simple:

Ask yourself whether the same file would behave better with more RAM, stronger GPU resources, faster storage, and a stable workspace. If the answer is probably yes, Vagon is worth considering.

If the answer is no, keep troubleshooting the software side first.

Photoshop crashes are frustrating because they interrupt the creative part of the work. But when the machine is the limit, the fix isn’t always another preference reset or another round of file cleanup. Sometimes the better move is to give the project a workspace that can actually keep up.

Photoshop crash checklist

You don’t need to run every fix every time Photoshop acts weird.

If the app crashes once after a long session, save what you can, restart, and keep an eye on it. But if the same problem repeats, use the crash pattern to choose the right fix instead of trying random settings.

Here’s a cleaner way to think through it:

The main idea is simple: don’t treat every Photoshop crash like the same crash.

A startup crash points in one direction. A Type Tool crash points in another. A scratch disk warning is practically waving a sign at you. A black canvas usually deserves a GPU check before you start tearing the file apart.

The faster you identify the pattern, the faster you can stop guessing.

FAQs

1. Why does Photoshop keep crashing?
Photoshop usually keeps crashing because the same underlying issue is still there. Common causes include GPU driver problems, full scratch disks, corrupted preferences, damaged fonts, outdated plugins, huge PSD files, or not enough RAM and storage headroom for the project. The important part is the pattern. If it crashes on launch, look at preferences, plugins, fonts, and updates. If it crashes while editing one file, look at file size, Smart Objects, linked assets, and scratch disk pressure.

2. Why does Photoshop crash on startup?
Startup crashes are often tied to corrupted preferences, incompatible plugins, damaged fonts, or a problem introduced after an update. Try launching Photoshop without third-party plugins if possible, reset preferences carefully, disable recently installed fonts, and check whether Photoshop and Creative Cloud are up to date. If the crash started right after installing a plugin or font pack, start there first. It’s usually faster than reinstalling everything.

3. How do I fix “scratch disks are full” in Photoshop?
Free up space on the drive Photoshop uses as its scratch disk, then restart Photoshop. You can also choose a different scratch disk from Preferences > Scratch Disks, ideally a fast SSD with plenty of free space. For large Photoshop projects, don’t run your system drive near full. Heavy PSDs, Smart Objects, high-resolution assets, history states, and AI-generated variations can require far more temporary space than the saved file size suggests.

4. Can GPU drivers make Photoshop crash?
Yes. GPU driver problems can cause Photoshop crashes, black canvas issues, flickering, display glitches, slow zooming, and problems with GPU-accelerated features. A quick test is to turn off Use Graphics Processor in Preferences > Performance, restart Photoshop, and test the same file again. If that helps, update your GPU driver. On Windows, use the latest driver from NVIDIA, AMD, or Intel. On macOS, GPU updates usually come through macOS updates.

5. Why does Photoshop crash when I use text?
Text-related crashes often point to fonts. A damaged font, messy font cache, or conflict with a font manager can make Photoshop freeze when using the Type Tool, opening the Character panel, scrolling fonts, or loading a file with specific typefaces. Disable recently installed fonts, test with system fonts only, and clear or rebuild the font cache if needed.

6. Should I reset Photoshop preferences?
Reset preferences if Photoshop behaves strangely, crashes randomly, won’t remember settings, or started acting unstable after an update. But do it carefully. If you use custom workspaces, shortcuts, actions, brushes, or presets, save what matters before resetting. Then test Photoshop with a blank file before reopening the problem file.

7. Can large PSD files make Photoshop crash?
Yes. Large PSD files can push Photoshop into RAM, GPU, scratch disk, and storage limits at the same time. Smart Objects, hidden layers, high-resolution assets, masks, high bit depth, linked files, and AI variations can all add pressure. Before flattening everything, duplicate the file and clean a copy. Remove unused hidden layers, archive old experiments, reduce unnecessary history states, and move unused AI variations outside the main PSD.

8. When should I use Vagon Cloud Computer for Photoshop?
Use Vagon Cloud Computer when the main problem is your local machine’s performance limit. If Photoshop keeps slowing down or crashing because of large PSDs, weak GPU resources, limited RAM, scratch disk pressure, or working from a lightweight device, Vagon can give the project a stronger cloud-based workspace. It won’t fix a damaged font or broken plugin by itself. But for heavy Photoshop workflows that have outgrown your laptop or desktop, it can make the editing environment much smoother.