
Video is where file sizes stop being polite. A phone clip is a few hundred megabytes, a wedding highlight export is 2 GB, and raw footage from a mirrorless camera eats a gigabyte a minute without trying. Every easy sending route, iMessage, WhatsApp, email, exists to move small things and will re-encode or refuse anything this size. Moving big video cleanly needs a route that treats the file as bytes to deliver rather than media to shrink.
Video size is bitrate times duration, and bitrate is where the quality lives. A 4K delivery export at 50 megabits per second comes to about 22 GB an hour, or roughly 375 MB a minute. A 1080p export at 10 megabits per second is still 75 MB a minute. Camera originals sit far above both: many mirrorless bodies record 4K at 100 to 400 megabits per second, which is 45 to 180 GB an hour.
This is why the tricks that work for photos fail for video. You cannot resize your way out of it without changing what the file is, and zipping does almost nothing because the codec has already squeezed the redundancy out. A ZIP of a 2 GB MP4 is a 2 GB ZIP.
So the question is how to move the file you made, rather than how to make it small enough for a chat app. Once you accept that, the options get simple: physical media, cloud storage, or a transfer link.
Chat and social apps re-encode video on principle, because their job is to deliver something watchable over a phone connection right now.
The damage compounds when the recipient is an editor. Footage that has been through a chat app has lost the very information grading and stabilization need. Whatever route you choose for client viewing, the handoff between working professionals has to carry the original file, byte for byte.
A transfer link moves the exact file without asking the recipient to install anything or sign up for anything. With Kepla File Transfer it goes like this.
For footage beyond 10 GB, split by scene or camera into multiple transfers, or fall back to a drive in the mail, which is still the right answer for a 500 GB raw dump. For everything under that, the link is faster than driving anywhere.
Most large video handoffs fail on the recipient’s side. Three habits prevent nearly all of it.
Say the size before they click. One line, the film is 3.8 GB, download on wifi. A client who starts a 4 GB download on a phone plan will blame the link.
Name files like a professional. A download called final_v3_FINAL2.mp4 invites questions. Something like Rivera_Wedding_Film_4K.mp4 answers them before they are asked.
Tell them it expires. The link living 3 days is a feature, since it keeps your delivery from floating around forever, but only if you say so: the download link expires Thursday, save the file somewhere permanent. With per recipient links and receipts you can see who has not downloaded yet and nudge that one person before the window closes.
Do these three things and the whole delivery is two short emails and zero support questions, at full quality.
Upload it to a transfer service and email the link. Kepla File Transfer takes files up to 4 GB each, 10 GB per transfer, with no account, and the recipient downloads the original file unchanged.
Avoid chat apps and social platforms, which re-encode. Send the exported file itself through a transfer link or cloud storage. The bytes that arrive should be the bytes you exported.
Yes, both downscale and recompress video substantially so it sends quickly. They are built for conversation, not delivery.
For batches under 10 GB, a transfer link with a 3 day expiry works well. For full shoot dumps in the hundreds of gigabytes, a physical drive is still the practical route.
Video codecs already remove nearly all redundancy. ZIP finds nothing left to squeeze, so the archive is about the same size as the original file.
Yes. Every video in a Kepla File Transfer shows a preview frame taken from a second or so in, with its running time, and plays in the browser with normal scrubbing · the player reads just the part it needs. Download is one tap and gives the original file, byte for byte, with no re-encoding.
No. Each file in the transfer has its own Download button, streamed straight from storage without passing through the browser’s memory, so a 5 GB clip downloads the same way on a phone as on a desktop. Download all is still there for the whole set.
Drag the footage in and send. The recipient sees a preview frame on every clip, can play it in the browser, and downloads the original bytes with one tap · nothing re-encoded, no account on either end.
It stays in your saved guides on this browser. Want it in your inbox too? One email with the link now, and the next guide when it is out. No pitches, unsubscribe with a reply.