How to Send Large Photo Files to Clients
Email caps, expiring transfer links, and raw folder shares all break down on big deliveries. Here's what actually works for sending full-resolution photo and video sets to clients.
Every photographer hits the same wall eventually: the client needs the full-resolution files, the set is 40 GB, and the tool you reach for has a limit you only discover halfway through. Here's an honest look at the options and where each one breaks.
How do I send large photo files to a client?
For anything over a few hundred megabytes, put the files in cloud storage and send a link rather than attaching them. Email caps out around 25 MB, and transfer services expire after days. The most durable approach is to share a Google Drive folder and present it as a gallery, so the client sees the photos rather than a file manager, downloads originals on demand, and the link keeps working months later.
The options, honestly
| Method | Practical ceiling | Expires? | What the client sees |
|---|---|---|---|
| Email attachment | ~25 MB | No | Attachments, if it sends at all |
| WeTransfer-style link | 2 GB free, more paid | Days | A download page, often with an ad |
| Raw Drive/Dropbox folder link | Your storage | No | A file manager full of DSC_ filenames |
| Upload-based gallery platform | Your storage tier | No | A gallery — after you upload it all again |
| Gallery on top of your Drive folder | Your Drive | No | A gallery, with no second upload |
Why file size is the wrong thing to optimize
The instinct is to make the files smaller — export at 80% quality, resize to 3000px, zip everything. Sometimes that's right. But the client asking for "the high-res ones" wants files they can print or hand to a designer, and a zip is a worse experience than a gallery: they have to download all of it to see any of it, and they'll come back in six months asking you to send it again because the zip is gone.
The better move is to stop moving the bytes around. If the finished set is already in your Drive, every copy you make afterwards is duplicated storage and duplicated waiting.
Why raw folder links disappoint
Sharing the Drive folder itself is free and has no size ceiling, which makes it tempting. The problem is what the client sees: a grid of filenames in a file manager, sorted by whatever Drive feels like, with your naming scheme on display and no way to view the set as photographs. It works, but it doesn't look like the job you just did.
A gallery layer on top of that same folder fixes the presentation without touching the mechanics. The files stay where they are; the client gets a full-screen lightbox, a download button, and something worth forwarding.
What about video?
Video is where transfer tools get expensive fastest — a single 4K master can exceed a free tier's entire allowance. Streaming from cloud storage sidesteps it: clips play inline so the client can review on a phone, and they only pull down the full file when they actually need it. Because playback goes directly between the viewer and Google's servers, a heavily watched delivery doesn't generate a bandwidth bill for you. There's more on this on the videographers page.
Practical rules that hold up
- Never make the client create an account to receive files. Agents, couples, and marketing managers all abandon at that step.
- Avoid anything that expires if the work has a second life — listings relist, couples come back, brands reuse assets.
- Let them see before they download. A preview costs the client nothing; a 12 GB download to check one frame costs them their morning.
- Deliver once, not twice. If a sneak peek and the full set are the same link, you've halved the number of emails in the job.
- Keep one source of truth. When the delivery reads your working folder, there's no version where the client has the old edit.
The setup I'd recommend
Export into a per-job folder in Google Drive as you already do. Share the folder as "Anyone with the link", then publish it as a GalleryLink gallery: the client gets a browsable, downloadable gallery at a link that doesn't expire, and you skip the upload step entirely. Set a password when the work is private, and switch downloads off when the package is prints-only.
If you want the full mechanics, the docs walk through it end to end, and the delivery methods comparison covers when a hosted platform is still the better call.