Modern phones shoot 4K video at 60 fps by default, which is beautiful, and roughly 400 MB per minute, which is not. Add HDR and it's more. A short clip of your kid's birthday party is now larger than the entire Windows 95 install disc, and every attempt to share it hits an upload limit — email cuts you off at 25 MB, WhatsApp at 16 MB in most regions, Slack at 1 GB but painfully slow past 100.
You can fix this in about a minute per video, and the result almost always looks the same on the screens people actually watch it on. The trick is understanding which two settings do 90% of the work.
The two settings that decide everything
1. Resolution — the pixel dimensions. 4K is 3840×2160, 1080p is 1920×1080, 720p is 1280×720. Every step down cuts the pixel count by about 2.25×. Your phone screen is roughly 1080p; a laptop screen is 1080p or 1440p; a TV is 1080p or 4K. If the video is going to be watched on phones and laptops (which is almost all video, almost always), 1080p is the ceiling worth keeping. 720p is fine for chat and social.
2. Bitrate — how many bits per second of video data. This is the knob most people don't touch and should. A 4K video from a phone is often shot at 100 Mbps. Netflix streams 4K at 15–20 Mbps and it looks great — because a good encoder makes better use of the bits. A 1080p video can look excellent at 3–5 Mbps; a 720p at 1.5–2.5. Lowering the bitrate is what actually shrinks the file.
Framerate matters less than people think: cutting from 60 fps to 30 fps saves roughly 20–30% for content where nothing is moving fast (talking head, casual clip). For sports and action, keep the framerate high and lower resolution instead.
A cheat sheet for common targets
Email attachment (~25 MB cap): 720p, 2 Mbps, 30 fps. Roughly one minute per 15 MB.
WhatsApp / iMessage (compressed on their side anyway): 720p, 2.5 Mbps. Sending pre-compressed avoids their much worse in-app compression.
Slack / Discord (100 MB soft target): 1080p, 4 Mbps, 30 fps. Roughly one minute per 30 MB.
Google Drive / Dropbox share where the recipient will watch it inline: 1080p, 5 Mbps. Trades a bit more size for noticeably better quality.
Long-term storage of family videos: 1080p, 6–8 Mbps. Small enough to actually back up; sharp enough to still enjoy on a laptop in 10 years.
4K keepers (weddings, once-in-a-lifetime): keep the original, but also make a 1080p 5 Mbps copy for daily use. Streaming the small one is what you'll actually do 99% of the time.
H.264 vs H.265 vs AV1 — the practical answer
H.264 is the safe default. Every device made since 2010 plays it. Files are a bit bigger than they need to be but nothing ever fails to open.
H.265 (also called HEVC) makes files roughly 30–50% smaller at the same quality. Modern iPhones and Macs love it. Older Androids, older Windows machines, and older browsers sometimes don't play it. Great for personal storage; risky for a video you're about to send to someone whose device you don't know.
AV1 is the newest and squeezes even more, but encoding is slow and support outside Chrome/YouTube is patchy in 2026. Worth using for videos you'll upload to platforms that transcode anyway (YouTube, TikTok); overkill for a one-off share.
The one-line rule: sending to someone else → H.264. Storing for yourself → H.265.
The single biggest mistake people make
Re-encoding a video twice. Every time a file goes through compression, it loses quality — not much per pass, but noticeably over three or four. If WhatsApp is already going to compress your file on send, and you compressed it once yourself first, that's two passes. If you then forward it, that's three. By pass four, everyone looks like they're behind frosted glass.
The right workflow: compress once, to the target you actually need, and send the compressed file directly. Bluebird's Video Compressor lets you pick resolution and bitrate explicitly instead of guessing, so you can hit the target in one pass. If in doubt, err on the side of a slightly bigger file — you can always compress again later; you can't get quality back.
Two shortcuts worth remembering
Trim first, compress second. Cutting three seconds of dead air off the start and end of a clip saves more space than the smartest bitrate choice. Bluebird's Video Trimmer runs in the browser and doesn't re-encode when you trim on keyframes — the fastest possible quality-preserving cut.
Silence is compressible; audio quality rarely is the bottleneck. If your video is a screen recording, dropping the audio bitrate to 96 kbps mono is invisible and saves a surprising amount over a long clip.
