Initializing... drag & drop files here
Supports: 3G2, 3GP, 3GPP, ASF, AV1, AVCHD +31 more
To reduce video file size, upload your MP4, MOV, MKV, WebM, AVI, or any of 35+ formats to our servers, then pick a target size (a percentage or an exact MB figure) or a CRF quality level — optionally switching to H.265 or a lower resolution to shrink further. No sign-up, no watermark.
Real result: In our production data the median video drops about 45% (a 34 MB clip becomes roughly 19 MB); switching to H.265 reaches about 50% at the same quality.
Modern phones shoot at bitrates that overflow nearly every sharing channel. A minute of iPhone 4K at 60 fps is around 400 MB; one minute of 1080p at 30 fps from a recent Android is around 130 MB. Compression rewrites the same footage at a lower bitrate (and optionally a lower resolution) so the file shrinks without re-recording.
<video> will tank a page; the same clip at 720p VP9 plays smoothly under 5 MB.| Codec | File size vs H.264 | Browser playback | Hardware decode | Pick when |
|---|---|---|---|---|
| H.264 (AVC) | baseline | Every browser since 2011 | Universal — every phone, tablet, TV | You need it to "just play" anywhere |
| H.265 (HEVC) | ~40-50% smaller | Safari 11+, Edge, Chrome (limited) | iPhone 7+, modern Macs, most Android since 2017 | iPhone / iCloud / 4K archival |
| AV1 | ~50-60% smaller | Chrome 70+, Firefox 67+, Edge 121+, Safari 17+ | iPhone 15 Pro+, Pixel 7+, Snapdragon 8 Gen 1+, M3+ Macs | Streaming, future-proofing, royalty-free distribution |
| VP9 | ~30-40% smaller | Chrome, Firefox, Edge, Android, Safari 14+ | Most devices since 2018 | YouTube-style web embeds, WebM output |
H.264 is still the right default for files you'll text to family or post to older platforms. H.265 is the right default for iPhone/iPad libraries and any 4K source. AV1 wins when both ends are recent (2023+) hardware.
Lower CRF = higher quality + larger file. CRF ±6 roughly doubles or halves the bitrate.
| CRF | x264 (H.264) | x265 (H.265) | Looks like |
|---|---|---|---|
| 18 | Visually lossless | n/a | Master / archive |
| 20-22 | High quality | n/a | Streaming master, YouTube upload |
| 23 | x264 default | — | Good general-purpose |
| 24-26 | Noticeable on still frames | High quality | Web delivery, smaller archive |
| 27-28 | Visible softness | x265 default | Mobile messaging, social |
| 30+ | Heavy compression artifacts | Lower-quality streaming | Tiny preview / GIF replacement |
Recommended starting points: CRF 23 (x264) or CRF 28 (x265) for general use; CRF 20 if quality is critical; CRF 30+ when you must hit a hard size cap. For 4K sources, you can push CRF 2-3 higher than the equivalent 1080p value before quality degradation is visible.
| Destination | Cap | Suggested target |
|---|---|---|
| WhatsApp (in-chat) | 16 MB | 15 MB at 720p H.264 |
| Gmail / Outlook attachment | 25 MB | 20 MB |
| Discord free | 10 MB | 9 MB at 480-720p |
| Discord Nitro Basic | 50 MB | 45 MB |
| Slack workspace | 1 GB | n/a (no compression needed) |
| Twitter/X video post | 512 MB / 2:20 | 200 MB at 1080p |
| Instagram Reels upload | 4 GB / 90 s | re-encoded by Instagram anyway |
| Reddit video post | 1 GB / 15 min | 100-200 MB at 1080p |
If your target isn't listed, use Specific file size mode and type the number — Auto Scale will pick a resolution and bitrate that lands close to it.
Re-encode the video at a smaller size using three levers: lower the bitrate or raise the CRF value, switch the codec to H.265 (about 40-50% smaller than H.264 at the same quality), and drop the resolution (4K to 1080p, or 1080p to 720p). Trimming unused footage is the single biggest win.
For most cellphone or screen-recorded footage, 50-75% reduction is achievable with no visible change — that's typical when re-encoding from a high-bitrate source (e.g., a 4K iPhone clip at ~50 Mbps) down to a normal streaming bitrate (8-12 Mbps for 1080p, CRF 20-22). Sources that are already heavily compressed (TikTok downloads, Zoom recordings) have less room to shrink before artifacts appear.
H.264 if the file will be texted, emailed, or played on a TV older than 2018 — it plays everywhere. H.265 if you're archiving, sending to another iPhone/Mac, or working with 4K — same quality at roughly half the size. iPhones since the 7 (2016) record in H.265 by default and decode it in hardware; modern Android phones decode it; the gap is older Windows browsers, where you may need to ship H.264.
For private archives and YouTube uploads, yes — AV1 is around 30% smaller than H.265 at the same quality. For files you'll share to specific people, only if you know both ends have AV1 hardware decode (iPhone 15 Pro and later, Pixel 7 and later, Snapdragon 8 Gen 1 and later, M3 Macs and later, Chrome/Firefox/Edge desktop). On older hardware AV1 will fall back to software decode and drain battery.
Target file size % scales the output as a fraction of the input (50% of a 200 MB file = 100 MB). Specific file size lets you type an exact number ("9.5 MB") and Auto Scale picks bitrate and resolution to land there. Use % when you want a predictable proportional shrink; use specific size when you have a hard cap (Discord 10 MB, WhatsApp ~16 MB inline, Gmail 25 MB).
Almost always a variable-frame-rate (VFR) source — screen recordings, Discord captures, and some webcam recordings store frames at irregular intervals. Switch to Constant Bitrate or Constant Quality mode and explicitly set a frame rate (24, 30, or 60 fps) under the advanced options. If that doesn't help, try a different container (MKV handles VFR better than MP4).
Yes. Drop multiple files (or a folder) onto the upload area. Each file gets its own compression settings panel — you can change codec or target size per-file, or apply the same preset to all. There's no cap on number of files per session.
By default, the primary video and audio stream are preserved. If your source is an MKV with subtitles or multiple audio tracks (e.g., commentary, dub languages), keep MKV as the output container — subtitle and additional audio streams are passed through. MP4 strips most subtitle formats and only keeps one audio track; switch to MKV to preserve everything.
Yes — use Trim → Time Range and enter start and end timestamps. Trimming a 20-minute clip to the 3 important minutes is the single biggest compression win available. For trim-only without re-encoding, use the dedicated Video Trimmer instead, which is faster because it doesn't re-encode.
Free sessions handle videos up to 1 GB per file. There's no limit on the number of files. All uploads use TLS; files are deleted automatically a few hours later, and we don't store, share, or access your videos.
Yes — any modern browser (Chrome, Safari, Firefox, Edge) on iOS, Android, Windows, macOS, ChromeOS, or Linux. No app install required. For format-specific workflows, see Compress MP4, Compress MOV, Compress MKV, or Compress WebM.