You save the file and it's 3 GB. You didn't add much. So why is the PSD so big, and how do you actually get it to the client?
Resolution × colour depth × layers
A PSD isn't one image. It's a stack of them, plus the metadata that says how they combine. Three things multiply the size:
Resolution. The pixel count. A 6000 × 4000 image is 24 million pixels. Every pixel carries colour data, and the file has to store it.
Colour depth. How many bits per pixel. 8-bit stores 256 levels per channel; 16-bit stores 65,536. A 16-bit file is roughly double the pixel data of an 8-bit one at the same resolution, because each channel holds twice the information.
Layers. This is the big one. A PSD stores every layer as its own full-size image plane, plus masks and channels. A document with 8 layers at 6000 × 4000, 8-bit, RGB, isn't one 24-megapixel image — it's up to eight, plus the layer masks and blending information. Add 16-bit colour and a few dozen layers, and a layered master can easily land in the 2–5 GB range: you're storing the whole stack, not just what the client sees.
A quick way to sanity-check your own file: in Photoshop, Image → Image Size shows the document size as a single layer, while the Status bar shows the size accounting for layers, channels, and masks. The gap between those two numbers is essentially your layer overhead — and it's where multi-gigabyte files come from.
What the client needs vs what you keep
Most "can you send me the file" threads come down to this:
What the client usually needs is a flattened export. They want the finished image — a JPG, PNG, or flattened PDF for print. One layer, small, opens anywhere. That's often a few MB.
What you keep is the layered master. The 3 GB PSD with every layer, mask, and adjustment intact. It's yours, it's the source of truth, and it's what you'll reopen in six months when the client asks for one change.
So the question is never "can I send the client the PSD?" The question is "does the client need the master, or just the result?" Nine times out of ten it's the result, and a flattened export solves it. But when they genuinely do need the layered master — a collaborator, a second designer, a future edit — you have to move the multi-gigabyte file, and that's where email fails.
How to send one
Email's ceiling is 25 MB. A 2–5 GB PSD isn't close. You have two honest options:
A transfer link. This is the right tool. One link, the full layered master, the client downloads it without an account. The only thing that matters is that the link is still there when they get to it — which rules out the free tiers that die in a few days. A no-expiry link means the master is there a month later, when the collaborator actually opens it.
A cloud drive. It works, but a shared drive file can hit "download quota exceeded" if a lot of people pull it in a day, and the recipient needs to be in your drive. For a one-off master hand-off, it's more friction than a flat link.
FileSplash gives you a no-expiry, branded delivery link, up to 1 TB per send. You send the 4 GB layered master, the client gets one clean link with the file name, and it's still there when they need it — without you managing a drive.
Big by design
A PSD is big because it stores every layer, at full resolution, at full colour depth. The client usually wants the flattened result; occasionally they want the master. When it's the master, a no-expiry transfer link is the only clean way to move a multi-gigabyte file — not email, and usually not a shared drive.
See how this fits the wider designer workflow in file transfer for designers (PSD, 3D, CAD), or start free with a no-expiry link for your next master. The short version of the reasoning is at why FileSplash.
