How to make a video file smaller to send

By Hein de Wilde··4 min read

The setting that actually shrinks a video is bitrate, not resolution — and the honest first question is whether you should be compressing at all. If this is a deliverable someone is paying for, send it at full quality by another route. If it is a preview so someone can give you notes, compress it hard and do not think twice.

What makes a video file big

File size is roughly bitrate multiplied by duration. Everything else is a lever on bitrate.

  • Bitrate — data per second. The direct control, and the one that matters.
  • Codec — how efficiently that data is used. H.265 gets roughly the same quality as H.264 at about half the bitrate. ProRes and camera RAW are enormous by design, because they are made for editing rather than viewing.
  • Resolution — 4K needs more bitrate than 1080p for the same apparent quality, but dropping resolution while leaving bitrate alone saves nothing.
  • Frame rate — 60fps needs more than 24fps.

The practical consequence: exporting at a lower resolution is not how you make a file smaller. Lowering the bitrate is. Resolution matters because it lets you lower the bitrate without it looking bad.

~700 MB

A ten-minute 1080p H.264 export at 8–10 Mbps — plenty for someone to give notes on, from a ProRes master that might be 50 GB.

What actually works

Re-encode to H.264 at a viewing bitrate. For 1080p, something in the range of 8–12 Mbps looks good on any screen someone will review it on. For a ten-minute cut that is roughly 600–900 MB — down from perhaps 50 GB of ProRes.

Use H.265 if you know the recipient can play it. Roughly half the size for the same quality. The catch is compatibility: it is widely supported now but not universally, and a client who cannot open your file has cost you more than the bandwidth saved.

Drop to 1080p if the review does not need 4K. Nobody spotting a timing issue needs 4K. This is the biggest single saving available and it costs nothing that matters for the purpose.

Trim. Obvious and routinely forgotten. If the note is about the middle third, send the middle third.

What does not work

Zipping. Video is already compressed. A zip saves a percent or two and adds a step. Same for JPEG, MP3 and most PDFs.

Lowering resolution but keeping the original bitrate. No saving, and now it is soft as well.

Re-encoding something that is already compressed, repeatedly. Each generation loses quality permanently and the losses stack. A file that has been through three "make it smaller" passes looks visibly worse than one that went through one, at the same final size.

When not to compress

If the file is the thing you are being paid for, do not compress it to fit under a free tier's limit. You are damaging a deliverable to avoid using a different service, and the damage is permanent and most visible exactly where clients notice — gradients, skin tones, motion.

Send the master at full quality. Under 50 GB that is genuinely easy: SwissTransfer takes 50 GB free with no account (checked 1 August 2026), and several other services will handle it too. Above that, sending 4K and RAW covers the workflow.

The two-file habit

Worth stating as a rule, because it removes the compression question from delivery entirely:

Compress the preview. Deliver the original.

Export a small H.264 review copy, send it, collect notes, make the fix once. Then send the master a single time. The upload time saved is much larger than anything you gain from choosing a better transfer service.

Practical settings

For a review copy that will be watched in a browser:

  • Codec: H.264
  • Resolution: 1080p
  • Bitrate: 8–10 Mbps, or a quality-based setting around the middle of the range
  • Audio: AAC, 192 kbps

Any editor and most free tools will do this. Handbrake's "Fast 1080p30" preset is close enough for review purposes and requires no decisions.

For something being published rather than reviewed, follow the target platform's own recommendations — they all re-encode on upload anyway, so uploading a high-quality master and letting them compress it is better than compressing it twice.

Checking before you send

Look at the exported file size and ask whether it is now in a bracket where sending it is easy. If a ten-minute cut came out at 700 MB, every free service handles it. If it came out at 6 GB, you have not compressed for review — you have made a second master, and the size ranges are worth a look before you decide how to send it.

And if you find yourself compressing every delivery because links keep expiring and you keep re-uploading, that is a different problem wearing a compression costume. Expiry is the thing to fix.

Hein de Wilde

I build and run Yungle, and I write everything here. Comparisons name competitors and credit them, every claim about another company comes from that company’s own documentation, and where we fall short it says so. More about who is behind this.

Read next