Email is the wrong pipe for a video: a personal Gmail attachment stops at 25 MB, which a ninety-second phone clip clears without trying. The route that works is a download link — and when the file is heading to whoever will cut it into clips, the cheapest transfer is often no transfer at all. Here is what each option really costs, how long the upload takes, and how to keep the file intact on the way.
Why a video file hits a wall that a contract never hits
An invoice of 2 MB, a signed contract of 12 MB — both cross an inbox without a second thought. A video is measured in minutes, and a minute of 1080p carries tens of megabytes of bitrate. YouTube's own encoder guidance for 1080p sits in the thousands of kilobits per second, so a two-hour recording lands in the gigabytes. Nothing about the file is exotic: it is simply too heavy for the pipe people reach for by reflex.
Google states the limit and the workaround in the same paragraph: on a personal Gmail account the attachment ceiling is 25 MB, and to send files above it — videos named first — Google's own answer is a download link rather than an attachment. That one sentence is the whole problem.
The reflex, then, is to shrink the file, and that is where most handoffs are ruined. The 'send in lower quality' option your phone offers is a silent re-encode: it throws picture detail away before anyone has cut a frame, and no later step puts it back. A clip cut from that copy inherits the damage — soft edges under the captions, banding in the gradients, audio squeezed twice. You will not see it on a phone screen. You will see it on the vertical screen, after publishing.
25 MBthe attachment ceiling on a personal Gmail account — the number that decides between an email and a download link. Source: Gmail Help.
Four ways to move a large video, and what each one costs you
A download link from a transfer service. The shortest path for a one-off: you drop the file, you get a URL, you send the URL. Free tiers cap the size of a single transfer, so read the cap before launching a 9 GB upload — WeTransfer documents the limit on a free transfer. The link expires, so the person on the other end has a window to download it.
A cloud drive link. Google Drive, Dropbox, OneDrive. You upload once, and the same file can be re-shared a dozen times without being uploaded again; Google documents the upload and share steps. Two frictions: the sharing permission has to be set so the other person can actually open the file, and every gigabyte is deducted from your storage.
An upload straight into the tool that will cut it. Some tools take the file themselves. That is the shortest chain there is: the source goes from your machine to the place the work happens, in one move, and nobody has to download, rename or re-upload anything afterwards.
A physical drive. Still the honest answer above a few hundred gigabytes: a shoot that fills two 4 TB drives does not travel by upload. Slow, traceable, and it needs a postal address.
Don't damage the file on the way
The transfer is not what kills quality — the re-encode before it is. Three habits, in this order.
Keep the original file. Never 'optimise' a recording you are about to hand over: converting it into a friendlier format re-encodes it once more, and the receiver's tool will re-encode it again on export. Zipping changes nothing, because the streams inside a video are already compressed; you add a step and gain almost nothing.
Name it so the receiver knows what it is. A file called final_final_2.mp4 costs a message; 2026-09-29_podcast-ep12_camera-A.mp4 costs nothing and survives every folder it lands in. It is the same discipline as sorting your footage before anyone opens an editor.
Send the context with it. Two lines: what the recording is, whether it is one camera or four, and what you want out of it — a batch of vertical clips, one long edit, or just a cut. The handoff is finished when the person can start without asking you a question; that second message is what your turnaround is really losing.
How long the upload will actually take
Upload time is arithmetic, and it is worth doing before you promise anyone a delivery hour.
A 5 GB file is 40 000 megabits (5 × 8 000). On a 10 Mbit/s upstream that is about 4 000 seconds — 67 minutes. On a 50 Mbit/s upstream, about 13 minutes. On the 5 Mbit/s that plenty of home connections really deliver on the way out, over an hour and forty.
The asymmetry is the trap: consumer connections are built for download. You can stream 4K without a hiccup and still need ten minutes to push a gigabyte out. Check the upstream figure rather than the headline number on the plan — and if the same file is going to two people, upload it once to a link and send the link twice.
If the destination is clips, skip the transfer
Look at the real chain when the goal is a batch of Shorts. You send an 8 GB source to an editor. They download it, cut it, upload twelve clips back. You watch twelve clips, ask for four fixes, they re-cut and upload again. Two large transfers and a revision loop, for clips — the same clips a pass over the transcript would have picked with you in the room.
The alternative is to remove the transfer instead of speeding it up: the ClipFinish clip production line takes one long source — up to two hours per pass — hands you back the transcript, and you tick the moments in the text. You set one framing and one caption style for the whole batch, and you collect vertical MP4s, captioned word by word, framed clear of the platform's interface, no watermark. Five minutes of finished clips a month are free, without a card.
State the limits plainly, because they decide whether this is your tool. It is not a frame-accurate editor: inside a clip you do not trim, mix or repair. One framing and one caption style per batch, so a client who wants three looks changes the batch, not the clip. And it does not pick the moment for you — that decision is the part worth keeping. If you are still weighing the two paths, briefing an editor so the handoff does not come back is the part that decides the revision loop, and how many finished clips a person really produces in a day is the number that settles the volume question.
FAQ: sending large video files
- What is the largest file I can email?
- 25 MB on a personal Gmail account, and Google's own answer above that is a Drive link. Treat anything bigger than a ninety-second phone clip as link material, not attachment material.
- How do I send a two-hour video to an editor?
- Upload it once to a cloud drive or a transfer service, then send the link with the permission set to anyone-with-the-link if the receiver is not on your account. Send the original file: a re-compressed copy costs the edit its detail and cannot be repaired afterwards.
- Is a Google Drive link good enough for video?
- For a single file, yes. Watch the storage quota, which is shared across Drive, Photos and Gmail, and expect the receiver to wait for a full download before they can start.
- How long does a 5 GB upload take?
- About 67 minutes on a 10 Mbit/s upstream, about 13 minutes at 50 Mbit/s. Home connections upload far more slowly than they download, so measure the upstream figure before promising a delivery time.
- Can I just send it on WhatsApp?
- Not at full quality. Messaging apps re-encode video to keep it small, and that re-encode happens before the cut. Keep them for previews, never for the master.
Pick the pipe according to the destination. A 25 MB ceiling settles the email question for you; above it, one upload and one link beat any chain of re-sends. Keep the original file intact — the re-encode you do on the way is the one you cannot undo. And when the destination is a batch of vertical clips rather than a full edit, the cheapest transfer is the one you never make: upload the source once to the ClipFinish production line, tick the moments in the transcript, and collect the batch.