You fly a half hour, land, and the card is already full. A single 20-minute flight is 22 GB before you've touched a single frame.
Drone footage is dense. Aerial 4K and 5.4K is shot at high bitrates to survive the motion — a moving camera needs more data per second to look clean. The result: one minute of 150 Mbps drone footage is about 1.1 GB. A 20-minute flight is roughly 22 GB. That's not a file you email, chat, or push through a free-tier link.
A clumsy send costs you in specific ways: the upload is long, home uplink is the slow side, and a dropped connection that restarts the upload from zero can turn a 20-minute flight into an all-afternoon upload you never finish. You end up re-sending, or — worse — quietly handing the client a version you re-encoded smaller so it would fit.
So build the send around two facts: the file is big, and your upload connection is the bottleneck.
The math you need before you send
- One minute of 150 Mbps drone footage: ~1.1 GB
- A 20-minute flight: ~22 GB
- The same flight uploaded on a 20 Mbps uplink: ~2 hours 27 minutes
That last number is the one that decides whether a service is actually usable for you. 22 GB over a 20 Mbps upload connection is not a few minutes — it's nearly two and a half hours. And that's the ideal case, on a steady connection. Real home uplinks wobble.
Why uplink is the bottleneck (and resumable uploads matter)
Most people think about download speed, because that's the number everyone sees. But you are the one uploading. Your uplink — the speed at which your home or office connection sends data out — is the number that matters for the send. It's often a tenth of your download speed, or less.
That's why the question to ask before you trust any service with a 22 GB flight is: does an interrupted upload resume, or start again? On a connection that will definitely wobble over two-plus hours, a service that restarts from zero is a non-starter — you'll never finish. A service that resumes where it left off turns a fragile two-hour upload into one that survives the router blip and the laptop sleep.
Test it once with a real file, before you need it.

Card, computer, link
- Card to computer. Copy the footage off the card first — don't work off the card itself. This is also your backup point.
- Send the real file, not a re-encode. Upload the actual footage to a link. No chat app, no re-compression. What the client gets is exactly what you flew.
- The client gets a no-account download. They open one link, no sign-up, and pull the 22 GB on their own connection — where download speeds are usually fast. The slow side (your upload) happens once; the fast side (their download) happens on their terms.
- No expiry, if the project runs. If the client is picking clips over a week or a month, the link should still be alive when they come back.
For the full method behind the size numbers and the delivery properties, see how to send large video files to clients. And the case for a no-account, no-expiry, branded link that can actually carry a 22 GB flight is in Beautifully Delivered.
Send the flight as you flew it — not a smaller version you had to shrink to fit. Start free →
