The upload limit that ruins your afternoon
A few minutes of 4K footage from a modern phone routinely lands in the hundreds of megabytes, and a longer clip can easily cross a gigabyte. That's invisible until you try to email it, message it, or upload it somewhere with a size cap — most platforms and inboxes reject files well before you'd expect, often around 25-100MB.
The frustrating part is that most of that size isn't buying you visible quality on the screen it'll actually be watched on. A phone recording shot for a quick share doesn't need the same bitrate as footage headed for a cinema screen.
Bitrate is the dial that actually matters
Video file size comes down almost entirely to bitrate — how much data is used per second of footage. Resolution and length matter too, but bitrate is what you control most directly, and cutting it is where the real size savings live. Dropping bitrate moderately on a phone-shot clip is usually invisible on the screen most people will watch it on; dropping it aggressively starts to show as blocky artifacts in busy, high-motion scenes.
This is why two videos of identical length and resolution can differ in size by 5x or more — the one with lower bitrate simply allocated fewer bits to describe each frame, and if that number wasn't chosen carefully, quality suffers exactly where you'd notice it: fast motion and fine detail.
Resolution downscaling is the other big lever
If a video is destined for a phone screen or a small embedded player, keeping it at its original 4K or even 1080p resolution is often wasted data — nobody's screen or eyes are resolving that much detail at typical viewing sizes. Downscaling to 720p or even 480p before compressing can cut file size dramatically on top of whatever bitrate reduction you apply, often with no perceptible loss for casual viewing.
The two levers work together: a lower resolution needs less bitrate to look sharp at that size, so combining both gets you further than either alone.
When compression genuinely isn't the right fix
If a video is headed for professional editing, archival, or any pipeline where quality is paramount and file size is a secondary concern, aggressive compression is the wrong move — you'll want to preserve the original as your source and only compress a final delivery copy. Compression is also a one-way trip: you can't recover quality that's been discarded, so it's worth keeping an original copy anywhere storage allows.
For everyday sharing, messaging, and uploading, though, a reasonably aggressive compression pass is almost always the right call — the size savings are large and the visible cost is small.