Video & Audio
What actually decides video file size
One minute of phone video can weigh 60 MB or 6 MB and look nearly identical on a phone screen. The difference is three settings - bitrate, resolution and codec - and once you understand them, any MB target becomes a calculation instead of a gamble.
Key takeaways
- File size = bitrate x duration. Everything else - resolution, codec, frame rate - works by influencing the bitrate you need.
- For sharing on phone screens, 1080p at 4-6 Mbit/s looks great; 720p at 2.5-4 Mbit/s is still perfectly watchable.
- Modern codecs (HEVC, AV1) halve the bitrate needed for the same quality compared to classic H.264 - but H.264 plays everywhere.
- Trimming dead seconds at the start and end is free compression: 20% shorter is 20% smaller.
The only formula that matters
A video file is essentially bitrate multiplied by duration. A 3-minute clip at 8 Mbit/s is 8 x 180 / 8 = 180 megabytes. The same clip at 4 Mbit/s is 90 MB. That is the whole game - every quality decision funnels into that one number.
This also explains why megapixels do not decide size the way people expect: a 4K video at a starved bitrate is both large and ugly, while a well-encoded 1080p video can be smaller and look better. Resolution only sets how many pixels the bitrate must feed.
Bitrates that actually look good
Screen recordings and static scenes need far less than the table suggests; fast sports footage and confetti need more. When a tool asks you for a target size in MB instead, it derives the bitrate from your duration automatically - which is usually the more intuitive way to think about it.
| Use case | Resolution | Bitrate (H.264) | 1 minute is roughly |
|---|---|---|---|
| Archive / editing master | 4K | 35-60 Mbit/s | 260-450 MB |
| Nice sharing quality | 1080p | 4-6 Mbit/s | 30-45 MB |
| Messenger-friendly | 720p | 2.5-4 Mbit/s | 19-30 MB |
| Small preview | 480p | 1-1.5 Mbit/s | 8-11 MB |
Codecs: H.264 for compatibility, HEVC and AV1 for size
H.264 (AVC) is the universally-playable workhorse: every phone, browser, TV and portal understands it. HEVC (H.265) reaches the same quality at roughly half the bitrate but still hits licensing and playback gaps outside Apple hardware. AV1 is the modern open contender with excellent compression, supported by current browsers and newer phones.
Practical rule: if the video leaves your ecosystem - job application, web form, mixed group chat - encode H.264 in an MP4 container. If it stays between modern devices and size matters, HEVC or AV1 buy you half the megabytes.
Hitting an exact MB limit
The FileSizeFix video converter does all of this in the browser using a local ffmpeg engine: pick MP4 or WebM, enter a target size in MB, optionally trim and cap the width - the video itself never leaves your device.
- Trim first. Cutting dead seconds at both ends is lossless size reduction and nobody misses them.
- Choose the resolution the audience actually sees: 1080p for screens, 720p for chat apps.
- Set the target size directly. A tool that accepts a MB target computes the right bitrate for your clip length automatically.
- Strip the audio track if the clip does not need sound - that saves another 1-2 MB per minute.
Frequently asked questions
How many MB is one minute of video?
Depends entirely on bitrate: about 30-45 MB at good 1080p sharing quality (4-6 Mbit/s), roughly 19-30 MB at 720p, and up to hundreds of MB for 4K camera footage.
Can I compress a video without losing quality?
Strictly lossless recompression barely shrinks video. What works is re-encoding at a lower bitrate or resolution - done moderately, the difference on a phone screen is invisible while the file drops by half or more.
Which format should I choose for uploads - MP4 or WebM?
MP4 with H.264 is the compatibility king and the safe pick for portals and mixed recipients. WebM (VP9/AV1) often compresses better and suits the web, but not every portal accepts it.
Does converting a video in the browser upload it somewhere?
Not with FileSizeFix: the browser downloads a conversion engine once and then processes your video locally on your device. The file is never sent to a server.