You hit Save. Photoshop tells you the file is too large to save. You didn't just add a layer — what changed? And what do you actually do?
What the error means
The error is real, and it's not Photoshop being vague. It means you've hit a hard limit built into the PSD format itself: a PSD can't store a file larger than 2 GB, and it can't exceed 30,000 pixels on either side. That's the format ceiling, not a setting you've accidentally turned on.
The file can be "too large" even when it looks small. A document that's only a few hundred megabytes can still trip the limit if a single side is over 30,000 pixels, or if layers, masks, and channels push the stored data past 2 GB. So the size you see in the file browser and the size Photoshop is refusing to save are sometimes two different numbers.
It bites at the worst moment
It usually happens at the end of a project, not the beginning. You've been working, adding layers, refining masks, and the file quietly crossed the line. Now you can't save, you can't close without losing work, and the client is expecting the file today. The panic is real, because the fix isn't "just make it smaller" — it's understanding which limit you hit, and that takes a minute.
Four ways under the limit
Try them in roughly this order:
1. Turn off Maximize Compatibility. In Preferences → File Handling, set Maximize PSD and PSB File Compatibility to Never. This stops Photoshop writing a full flattened composite into the file on every save, which can shave meaningful space off large documents. It's the cheapest fix to try first.
2. Save as PSB (Large Document). This is the real fix for the 2 GB wall. PSB is the "large document" format — it keeps the same layers and features but lifts the size ceiling dramatically (the 30,000 px limit also relaxes for PSB). If your file is over 2 GB, save as .psb and the error goes away. The catch: some older tools and plug-ins don't read PSB, so keep a flattened export around for anyone who needs it.
3. Use smart objects. If a layer is a huge placed image or a complex group, wrap it in a smart object. The heavy data is stored once and referenced, rather than re-rendered into every dependent layer, which keeps the stored size down.
4. Split the document. If it's genuinely a very large composite, break it into multiple linked PSDs or split the layers across files. It's more work, but it's the honest answer for documents that have outgrown a single file.
When the file is fine but the delivery is the problem
Sometimes the file saves perfectly, but getting it to the client is what fails. A 3 GB PSB or PSD that saved without a hitch still can't go through email's 25 MB ceiling. If the error was about delivery and not about saving — "the file is too large to send" — then the fix isn't any of the four above. It's a transfer link.
A no-expiry, branded delivery link moves the multi-gigabyte master without an account, without a drive quota, and without the link dying before the client gets to it. That's what FileSplash is built for: no-expiry delivery, up to 1 TB per send. The file stays the file; the link just carries it.
Save it, then send it
"File too large to save" means you hit the PSD format's 2 GB / 30,000 px ceiling. Turn off Maximize Compatibility, save as PSB for the size wall, use smart objects or split layers to keep the stored data down. And if the file actually saved and it's the sending that's failing, skip the format fixes entirely and use a transfer link.
See the sizing math that explains why these files get so big in why are PSD files so big, or start free with a no-expiry link for the master. The short version of the reasoning is at why FileSplash.
