When a client asks for a full video project, high-quality final films, short versions, per-format cutdowns, you cross a threshold where the logistics become their own subject. At 100GB, it's not an attachment anymore: it's a transfer that has to be built so it doesn't break midway or bury the client.
Why consumer links stall at this volume
Plenty of consumer transfer tools are built for light payloads: size caps, very short expiry, an upload that starts over from zero at the first drop. On 100GB, a disconnection at 80% makes you restart everything, and a link that expires in three days pressures the client who never asked for it.
The problem isn't the size itself, big volumes transfer fine with the right tool, it's the fragility of the channel. A transfer that resumes exactly where it stopped changes everything at this weight.
Separate the footage from the exports before you send
A final client almost always wants the exports, not the raw material. Only deliver the footage if the contract calls for it: it's a different volume and a different use, handled as its own project. Mixing the two into one giant delivery puts a weight on the client that isn't theirs to carry and blurs what they actually need to grab.
If raw footage is part of the deliverable, treat it separately. Our guide on delivering raw footage to an agency covers that organisation, distinct from a finished edit.
Compress with judgement, never at the expense of the deliverable
Sensible compression cuts the volume without hurting what matters. Keep your final exports at their delivery quality, but avoid stacking intermediate versions or redundant exports that inflate the total without serving the client. A well-chosen delivery codec already weighs far less than a master, with no visible loss for the intended use.
Above all, don't crush everything into a single 100GB ZIP: a client who has to unzip a huge block just to find one file hits pointless friction, and a ZIP that corrupts at the end of the download means redoing the whole batch.
Deliver on a page, not a bare link
At this volume, a delivery page beats an anonymous link every time. It carries your brand, a note for the client, and above all a clear layout: chaptering by deliverable (main film, short versions, social formats), readable names, and downloads file by file or in bulk at the client's choice.
A client landing on a structured page instantly knows what they received and where each version lives. That's the difference between a delivery that inspires trust and a dump you'll have to explain over messages.
Confirm the client got everything, then expire cleanly
On a large volume, the real risk isn't the send, it's the doubt: did the client actually download everything, with no missing file? Tracking that shows you what was opened and pulled lets you confirm receipt instead of following up blind.
Once the download is done, let the delivery expire: it isn't meant to stay online forever, and your internal archive stays separate, on your own storage. On xFer you send large volumes in parallel over a private link that resumes after a drop, structure the page by deliverable, see who downloaded, and set the expiry on each delivery.
In short
At 100GB, pick a channel that handles the volume and resumes after a drop, separate footage from exports, compress without touching the deliverable, deliver on a chaptered page rather than a bare link, and confirm receipt through tracking before you expire it. A big video project gets delivered like a project, not an attachment.