Initializing... drag & drop files here
Supports: MP4, M4V
MP4 is the most widely used video container on the open web — phone cameras, screen recorders, editing apps, and streaming exports all default to it. The flip side is size: a 1-minute 1080p H.264 clip at typical phone bitrates lands around 100-200 MB; a 4K clip from a recent iPhone or Android can easily clear 400 MB per minute. Common reasons people compress MP4:
| Mode | What it does | Best for |
|---|---|---|
| Target file size (%) | Output ≈ N % of input | Predictable batch shrinkage |
| Specific file size | Output ≤ X MB exactly | Hitting WhatsApp 16 MB, Discord 10 MB, Gmail 25 MB |
| Constant Bitrate (CBR) | Fixed bits-per-second throughout | Streaming, fixed-budget delivery |
| Variable Bitrate (VBR) | Bits flex with scene complexity | Best size-to-quality ratio for stored files |
| Constant Quality (CRF) | One quality target, size flexes | Maximum efficiency, identical look across a batch |
| Constraint Quality | CRF capped at a max bitrate | Quality-first encoding with a streaming ceiling |
x264 / H.264 uses a CRF range of 0-51 with default 23; x265 / H.265 uses the same 0-51 range but a default of 28 that produces equivalent visual quality. Practical "sane" range for both is 18-28.
| CRF (H.264) | Equivalent (H.265) | Visible loss | Best for |
|---|---|---|---|
| 17-18 | 22-23 | None — visually transparent | Archival masters, color-graded edits |
| 20-22 | 25-27 | Imperceptible on TV / monitor | YouTube uploads, client deliveries |
| 23 (default) | 28 (default) | Subtle on critical content | General-purpose web video |
| 25-26 | 30-31 | Visible on contrast / motion | Phone playback, social uploads |
| 28+ | 33+ | Aggressive — visible artifacts | Last-resort fit-to-cap targets |
| Property | MP4 (H.264) | MP4 (H.265 / HEVC) | WebM (VP9 / AV1) | MOV (ProRes / H.264) |
|---|---|---|---|---|
| Relative size at same quality | 100% (baseline) | ~55-60% | ~50-55% (AV1) | 300-1000% (ProRes is intermediate) |
| Browser playback | Universal | Safari, Edge; Chrome 105+ | Chrome, Firefox; Safari 14.1+ | Safari only |
| Mobile / TV playback | Universal since 2010 | iPhone 6+, modern Android, 2017+ TVs | Android, Chrome OS | Apple devices |
| Hardware decoder | Everywhere | Most chips since 2017 | Newer chips, AV1 in 2022+ devices | Apple Silicon, T-series chips |
| Best use case | Maximum reach | Smaller files, modern audience | Open-web embed, smallest size | Editing source, Final Cut / iMovie |
| Platform | Free tier cap | Paid / workaround |
|---|---|---|
| WhatsApp (in-chat video) | 16 MB | Send as document → 2 GB |
| Discord | 10 MB | Nitro Basic 50 MB, Nitro 500 MB, Boost-Tier-3 server 100 MB |
| Telegram | 2 GB per file | Premium 4 GB |
| Signal | 100 MB | — |
| Gmail attachment | 25 MB | Pushes to Drive automatically |
| Outlook attachment | 20 MB | Pushes to OneDrive |
| Reddit native video | 1 GB | — |
| Twitter / X video | 512 MB (Premium 8 GB) | 2:20 free, 3 hrs Premium |
| Slack free workspace | 1 GB per file | 90-day file retention on free plan |
Typical results: 30-50% with default settings on the same codec (H.264 → H.264 at CRF 23), 50-70% when re-encoding H.264 → H.265 at equivalent quality (CRF 23 → 28), and 80%+ when also downscaling resolution (e.g., 4K → 1080p) or trimming unused footage. A 200 MB phone clip routinely lands at 30-60 MB without visible quality loss. A 4K drone shot at 400 MB / minute can drop to under 100 MB / minute as a 1080p H.265 file.
H.264 for maximum compatibility — every browser, phone, and TV made in the last 15 years plays it. H.265 / HEVC for the best size-to-quality ratio on modern audiences — Safari and Edge play it natively, Chrome added support in version 105 (Sept 2022), and every iPhone since the 6, every modern Android, and every TV made since 2017 has hardware decode. AV1 for the smallest possible files and future-proofing, but encode time is 5-10× longer than H.265 and only devices from 2022+ decode smoothly. For a single deliverable that has to play everywhere with no surprises, H.264 is still the safe pick.
Pick "Specific file size" and enter 16 MB for WhatsApp in-chat video or 10 MB for Discord free. Smart Auto Scale will rebalance bitrate and resolution to land under the cap. For best results on tight targets, also drop resolution to 720p (or 480p for very short clips on Discord free) and switch the codec to H.265 — you'll get noticeably better quality at the same file size. WhatsApp also accepts videos up to 2 GB if you send them as documents (the recipient downloads instead of inline play).
It depends on the settings. At CRF 17-22 (H.264) or CRF 22-27 (H.265), most viewers cannot tell the compressed file apart from the source on a normal screen — verified in bit-blind tests. At CRF 23-25 H.264 / 28-30 H.265, quality loss is subtle and only visible on critical content (skin texture, fine grain). At CRF 28+ H.264 you'll see banding and blocking on dark gradients and fast motion. Pick CRF based on viewing target: 17-22 for archival or critical work, 23 for general web, 25-28 for phone-only social uploads.
Yes. Use Constant Quality (CRF), Constant Bitrate, or Variable Bitrate with the resolution left at "Original". The encoder re-evaluates each frame and discards redundancy without rescaling — typical savings of 30-50% on the same codec, more if you also switch to H.265. Resolution downscaling is an additional lever you can apply on top when you need to hit a small cap.
Three usual causes. (1) The source was already heavily compressed — re-encoding a 5 Mbps social-media download at CRF 23 just preserves the existing artifacts; you cannot recover detail that's already gone. (2) Resolution was scaled down too far for the bitrate budget — a 4K source forced into 360p will look soft regardless. (3) The original had heavy film grain or noise; CRF spends bits encoding the noise pattern, so dropping CRF to 20 or applying a light denoise before compression usually fixes it.
Yes. Drop in a whole folder of recordings or exports and they process in parallel with the same settings, then download individually or as a ZIP. Each file auto-scales independently to hit your target — useful when batch-compressing a mix of 4K and 1080p clips with one "fit under 25 MB" rule.
Audio re-encodes by default with sane AAC settings (typically 128 kbps stereo at 48 kHz). For voice-only screen recordings or podcasts inside MP4, you can drop audio bitrate to 64-96 kbps with no noticeable loss and save several MB on long files. Music and ambient audio benefit from keeping 128-192 kbps. Audio bitrate, sample rate, and channel count are exposed in Advanced Options.
MP4 is the universal container — every device, every browser, every editor. MOV is Apple's container (Final Cut, iMovie, QuickTime); the codec inside (H.264 or HEVC) is the same as MP4 but the file extension and metadata differ. WebM is the open-web container for VP9 / AV1, plays in Chrome / Firefox but not Safari natively until 14.1+. For sharing and uploading, MP4 wins. See MOV to MP4, MP4 to WebM, and MP4 to MP3 for related conversions. To trim before compressing, use Trim MP4.