How to Reduce Video File Size: Compressed Size Explained
How to Reduce Video File Size (and Predict the Compressed Size)
Last updated: November 2026
To reduce a video's file size, open the Shimga Video Compressor, load the video, choose a target size or a quality preset, and download the smaller MP4. The compressed size is set mainly by bitrate multiplied by duration, so you can predict it before you start: a 60-second clip at 4 Mbps video plus 128 kbps audio comes out at about 31 MB. Lowering the resolution (for example 4K to 1080p) lets you use a lower bitrate without the picture breaking up. The video is processed in your browser and is not uploaded.
Photo: Moises Caro on Pexels
Key facts
- Compressed video size (MB) = (video kbps + audio kbps) x seconds / 8 / 1000.
- Bitrate is the main dial. Resolution and frame rate decide how much bitrate you need to look good.
- Phone videos are often oversized. Phones record at high bitrates so you can edit later; a sharing copy can often be much smaller with little visible change.
- Two biggest levers: lower the resolution, and lower the frame rate if the clip was shot at 60 fps but doesn't need it.
- Re-compressing a compressed video adds blur and blocks. Start from the original whenever you can.
- Privacy: Shimga's compressor works locally in your browser.
- Output: always an H.264 MP4 with AAC audio. It needs a browser with WebCodecs (recent Chrome, Edge, Safari or Firefox).
Compressed video size explained, with real numbers
A video file is mostly two streams: video and audio. Each has a bitrate in kilobits per second. Multiply by length, divide by 8 to get bytes, and you have the size.
Example: a 2-minute (120 s) clip at 5,000 kbps video and 128 kbps audio: (5,000 + 128) x 120 / 8 / 1000 = 76.9 MB.
The table shows what common bitrates produce per minute:
| Total bitrate | Per minute | 30 s | 5 min | Looks good for (H.264, typical footage) |
|---|---|---|---|---|
| 1 Mbps | 7.5 MB | 3.8 MB | 38 MB | 480p, or 720p talking head |
| 2.5 Mbps | 19 MB | 9.4 MB | 94 MB | 720p |
| 5 Mbps | 38 MB | 19 MB | 188 MB | 1080p at 30 fps, simple scenes |
| 8 Mbps | 60 MB | 30 MB | 300 MB | 1080p at 30 fps (YouTube's upload guide) |
| 12 Mbps | 90 MB | 45 MB | 450 MB | 1080p at 60 fps |
| 35 Mbps | 263 MB | 131 MB | 1.3 GB | 4K at 30 fps |
"Looks good" depends on the footage. A static screen recording or a person talking compresses very well. Confetti, rain, fast sports, water and grainy low-light footage need much more bitrate to avoid blocky artifacts.
How to hit an upload limit
Flip the formula to find the bitrate you can afford:
total kbps = target MB x 8000 / seconds
Then subtract the audio bitrate to get the video bitrate.
Example: you need a 90-second clip under 10 MB. 10 x 8000 / 90 = 889 kbps total. Minus 96 kbps audio leaves about 790 kbps video. That is too little for clean 1080p, so lower the resolution to 720p or 480p as well. A small sharp video looks better than a big blocky one.
Aim 5 to 10 percent below the limit, because containers add a little overhead. Upload limits change, so check the current figure for your app; Gmail attachments, for instance, are capped at 25 MB, and above that Gmail offers a Drive link instead.
Compress a video in 6 steps
- Open shimga.app/video-compressor on a laptop or desktop if possible. Phones can do it but take longer and get warm.
- Load the original video (MP4, MOV or WebM).
- Pick a target. Enter a target file size in MB, or choose a quality preset (Smallest, Balanced or High). Target-size mode aims slightly under your number, but short or very busy clips can land a little over.
- Lower the resolution and frame rate if needed. Cap the height at 1080p, 720p, 480p or 360p, and the frame rate at 60, 30, 24 or 15 fps. For a tight size limit, 720p at 30 fps is usually the best compromise. Untick Keep audio for silent clips. The video resizer changes the shape for vertical or square posts.
- Compress and download the MP4. The tool shows the original size next to the new one.
- Play a busy section of the new file. Check fast motion and dark areas, where compression shows first, and confirm the size before you send it.
Photo: Efrem Efre on Pexels
What actually reduces size (and what doesn't)
| Change | Size effect | Visible quality effect |
|---|---|---|
| Lower bitrate | Direct and predictable | Blockiness and smearing if pushed too far |
| 4K to 1080p | Quarter of the pixels, so a much lower bitrate looks clean | Barely noticeable on phones |
| 1080p to 720p | Less than half the pixels, so roughly half the bitrate | Slight softness on large screens |
| 60 fps to 30 fps | Saves bitrate on motion-heavy clips | Motion looks less smooth |
| Trim the start and end | Proportional to the time removed | None |
| Lower audio from 320 to 128 kbps | Small (about 1.4 MB per minute) | Usually none for speech |
| Remove the audio track | Small | Obviously, no sound |
| Change MP4 to MOV | None by itself | None |
Changing the container (MP4, MOV, MKV) does almost nothing on its own; the codec and bitrate inside are what matter. Newer codecs such as H.265/HEVC and AV1 reach the same quality at lower bitrates than H.264, but some older devices and editors play them poorly. H.264 MP4 is still the safest choice for sharing.
Platform targets
| Destination | Practical target |
|---|---|
| Under 25 MB total, or share a link | |
| Chat apps | Check the app's current limit; send as a file/document if it re-compresses heavily |
| YouTube | Don't over-compress; upload a high-quality file and let YouTube encode it |
| Instagram / TikTok | 1080x1920 vertical, a moderate bitrate; the platform re-encodes anyway |
| Website background video | 720p or 1080p, 1 to 3 Mbps, no audio, short loop |
For platform dimensions, see our video resizer guide for social media and the article on music video aspect ratios.
Photo: Caleb Oquendo on Pexels
Honest limits and alternatives
Browser compression uses your device's processor, so long 4K files can take a while, and very large files may run out of memory on phones. For long or batch jobs, free desktop tools are a good choice:
- HandBrake (free, Windows/macOS/Linux): presets for every device and a constant-quality mode (RF) that is easier than guessing bitrates.
- ffmpeg (free, command line): for example
ffmpeg -i in.mp4 -vf scale=-2:720 -c:v libx264 -crf 26 -c:a aac -b:a 128k out.mp4. Higher CRF means a smaller file. - Your editor's export settings: if you are still editing, export smaller in the first place rather than compressing afterwards.
If you are exporting a music visualizer from Shimga's studio, pick the resolution you actually need at export time. Our guide to exporting 1080p and 4K from the browser explains the trade-offs.
FAQ
How can I tell what size my compressed video will be? Add the video and audio bitrates, multiply by the length in seconds, divide by 8,000. That gives megabytes. A 3-minute video at 3 Mbps total is 3,000 x 180 / 8,000 = 67.5 MB.
Does compressing a video always reduce quality? Technically yes, because it throws data away, but at sensible settings the change is hard to see on a phone. Problems appear when you squeeze a long, high-motion video into a very small size.
Why is my phone video so large? Phones record at high bitrates (and often 4K or 60 fps) to keep detail for editing. A sharing copy rarely needs that much.
Is it better to lower the resolution or the bitrate? For tight limits, do both. A 720p video at a fitting bitrate looks cleaner than a 1080p video starved of bitrate.
Is my video uploaded when I use the Shimga compressor? No. Processing happens in your browser and the file stays on your device.
Can I compress only the audio? Yes. Extract it with video to audio and use the audio compressor; see how to compress audio files.
More free audio and video tools are on the Shimga tools page.