How to reduce MP4 file size｜Video compression settings and size estimates
If your MP4 is too large, it can be hard to know which setting to change first. Start with its duration and where it will be watched; those two details help you avoid sacrificing more quality than necessary.
Open tool →Steps
- Check the destination's size and playback requirements and keep your original.
- Choose ClipForge local conversion up to 512MB per video, or server conversion up to 64GB combined.
- Compare 720p or 1080p and the quality settings; trim unwanted time. Use H.264 in MP4 when compatibility matters.
- Save the output and verify size, full duration and audio synchronization before sharing.
File selection screen
Prepare a copy for its destination
A phone screen and a large display do not need the same resolution. Try a short section, compare the appearance and play the saved clip through to the end before processing the full video.
Bitrate, resolution, fps and codecs
Lower bitrate can reduce size but may damage detail or motion. ClipForge exposes quality choices, not a direct numeric video-bitrate or fps field in the current UI.
Compare 720p for phone sharing and 1080p for finer text or larger screens; keep 4K only when needed. A lower fps can change motion smoothness, while reducing resolution does not guarantee a fixed size reduction. Removing unnecessary duration can help.
H.264 is a compatibility candidate; H.265 and AV1 can be compared where supported. They are not always faster or smaller. Current local ClipForge conversion outputs H.264 video and AAC audio regardless of the codec selector; server choices are separate.
Calculated size for 1, 5 and 10 minutes
Approximate size is total video-and-audio bitrate multiplied by duration, divided by eight. These are calculations, not measured conversions.
| Video + audio total | 1 minute | 5 minutes | 10 minutes |
|---|---|---|---|
| 2 Mbps | 15 MB | 75 MB | 150 MB |
| 5 Mbps | 37.5 MB | 187.5 MB | 375 MB |
| 10 Mbps | 75 MB | 375 MB | 750 MB |
Decimal MB: 1 MB = 1,000,000 bytes, excluding container overhead. The tool's size values use a 1024-based calculation. Constant-quality encoding can produce variable bitrates.
Settings for social sharing and email
Check the current destination limits for the actual account and upload method. Leave headroom and compare a short 720p H.264 MP4 with 1080p if details are insufficient. A named preset is not a guarantee of acceptance.
For email, consider the total attachment limit. Trim unnecessary time when resolution changes alone are insufficient. The current local target-size implementation applies a size cap and can stop output early; check the entire duration as well as bytes.
Local and server processing
Local conversion is free and unlimited up to 512MB per video without video uploads for conversion. Server conversion uploads videos and accepts a combined selection up to 64GB, charging one ticket per 2048MB rounded up; sign in and check your balance.
Memory and input codecs can still cause failure below the limits. Initial engine loading requires a connection. Try a short file and close busy tabs, or check server connectivity and upload progress.
User-reported test
86.4MB MOV, 35-second duration. Local 720p H.264 MP4 at high quality: 25 minutes 40 seconds, 46.9MB output. Server conversion: 40 seconds, 61.5MB.
Firefox · Windows 11 · Ryzen 7 2700X · 32GB
Input video fixtures
| Fixture | Resolution | fps | Duration (seconds) | Video / audio codec | Video / audio bitrate (bps) | Bytes |
|---|---|---|---|---|---|---|
| video-a.mp4 | 1920×1080 | 30/1 | 30.000000 | h264 / aac | 19921558 / 128008 | 75213524 |
| video-b.mp4 | 1920×1080 | 60/1 | 60.000000 | h264 / aac | 36092666 / 128175 | 271725181 |
| video-c.mp4 | 3840×2160 | 30/1 | 30.000000 | h264 / aac | 80647218 / 128008 | 302934749 |
One trial per condition, using self-generated fixtures. Timing varies with the device, browser, content and initial engine loading. These results do not guarantee processing time for real photographs or recordings.
Synthetic-fixture measurements on 14 October 2026
One trial per condition, using self-generated fixtures. Timing varies with the device, browser, content and initial engine loading. These results do not guarantee processing time for real photographs or recordings.
Browser/local: Windows 11, Ryzen 7 2700X, RTX 2070 SUPER, 32 GB, Chrome 155.0.8059.40 (headless). Timing runs from starting conversion to completion, excluding selection and download. Browser video encoding uses CPU WebAssembly.
Server: Ubuntu, Core i7-7700HQ, GTX 1060 Max-Q, approximately 16 GB, FFmpeg 6.1.1, NVENC. The production encoder was exercised with isolated fixtures. This is not an end-to-end public API measurement including upload, download, Google login or payment.
AV1 could not run because it is absent from the current backend codec list. H.265 was run with the HEVC setting and its output was independently confirmed as HEVC.
| Input / settings | Processing mode | Input bytes | Output bytes | Seconds | Verification | Size reduction |
|---|---|---|---|---|---|---|
| video-a.mp4 · 1080p · h264 | Browser/local | 75213524 | 22078848 | 238.672 | Verified · h264 · 1920×1080 · 30/1 fps | 70.65% |
| video-a.mp4 · 720p · h264 | Browser/local | 75213524 | 5581529 | 127.67 | Verified · h264 · 1280×720 · 30/1 fps | 92.58% |
| video-a-h264-1080p · 1080p · h264 | Isolated server | 75213524 | 39162469 | 3.606 | Verified · h264 · 1920×1080 · 30/1 fps | 47.93% |
| video-a-h264-720p · 720p · h264 | Isolated server | 75213524 | 16392197 | 3.617 | Verified · h264 · 1280×720 · 30/1 fps | 78.21% |
| video-a-hevc-1080p · 1080p · hevc | Isolated server | 75213524 | 36761227 | 3.095 | Verified · hevc · 1920×1080 · 30/1 fps | 51.12% |
| video-a-av1-1080p · 1080p · av1 | Isolated server | 75213524 | — | 0.0 | Unsupported | —% |
| video-b-h264-720p · 720p · h264 | Isolated server | 271725181 | 60617878 | 10.516 | Verified · h264 · 1280×720 · 60/1 fps | 77.69% |
| video-c-h264-1080p · 1080p · h264 | Isolated server | 302934749 | 34510828 | 7.446 | Verified · h264 · 1920×1080 · 30/1 fps | 88.61% |
One trial per condition, using self-generated fixtures. Timing varies with the device, browser, content and initial engine loading. These results do not guarantee processing time for real photographs or recordings.
Video size calculator (estimate)
Estimated size:
Size (MB) ≈ seconds × (video Mbps + audio kbps ÷ 1000) ÷ 8. 1 MB = 1,000,000 bytes. Container overhead is excluded and variable bitrate changes the actual size. This is a calculation, not a measurement.
Frequently asked questions
Does compression affect quality?
Re-encoding and quality or resolution changes can lose details. Keep originals and inspect motion and text.
Does MOV to MP4 always reduce size?
No. Changing the container without recompressing its media can leave the size nearly unchanged.
How much does lower bitrate save?
At the same duration, size roughly follows total video and audio bitrate, with overhead and variable-rate differences.
Does a 100MB target preserve the entire video?
It is not guaranteed. Current local size capping can stop output early; check size and duration.
Can local mode select fps or H.265?
There is currently no direct fps field, and local output is H.264. Distinguish this from server codec choices.