Initializing... drag & drop files here
Supports: HEVC
HEVC (H.265) — standardized by ITU-T in April 2013 — is already one of the most efficient mainstream video codecs, roughly half the bitrate of H.264 / AVC at equivalent visual quality. But HEVC source files from modern cameras are still huge: a single minute of 4K 60fps iPhone footage is 400-600 MB, a ten-minute drone clip can top 4 GB. Common reasons to re-compress an existing HEVC file:
| Mode | What it does | Best for |
|---|---|---|
| Target file size (%) | Output ≈ N % of original | Predictable shrinkage across batch (default) |
| Specific file size (MB) | Hits an exact size cap | Squeezing under email / messaging limits |
| Constant Bitrate (CBR) | Locks bitrate to a fixed kbps / Mbps | Streaming where bandwidth is fixed |
| Variable Bitrate (VBR) | Spends bits where the scene needs them | Best size / quality at a target average |
| Constant Quality (CRF) | One quality factor, output size varies | Library re-encoding — same look across mixed sources |
| Constraint Quality | CRF + min/max bitrate bounds | Streaming with quality floor |
CRF on the x265 encoder uses a slightly different scale than x264 — at the same CRF value, x265 produces a smaller file at comparable perceived quality. The defaults differ accordingly:
| CRF (x265) | Visible loss | Typical 4K 30fps minute | Typical 1080p 30fps minute | Best for |
|---|---|---|---|---|
| 18 | None — bit-perfect to eye | 200-280 MB | 60-90 MB | Archival, masters |
| 22 | Imperceptible on TV | 90-140 MB | 25-45 MB | Default for libraries |
| 24-26 | Subtle on critical content | 50-90 MB | 15-25 MB | Phone / tablet copies |
| 28 | Visible on motion / gradients | 30-50 MB | 8-15 MB | Discord / messaging |
| 32+ | Aggressive — visible artifacts | <25 MB | <8 MB | Preview / low-bandwidth |
| Codec | Year standardized | Output size (vs H.264 baseline) | Encode speed | Decoding support |
|---|---|---|---|---|
| H.264 / AVC | 2003 | 100% | Fastest | Universal — every device since ~2005 |
| H.265 / HEVC | 2013 | ~50% (BD-rate vs H.264) | 2-5× slower than H.264 | Apple full; Windows via extension; Chrome 107+ partial; Safari 13+ full |
| AV1 | 2018 (AOMedia) | ~30-50% smaller than HEVC | 5-10× slower | Modern browsers; phones / TVs from ~2022; partial hardware decode below that |
Yes, a little — every lossy re-encode introduces some loss. In practice, going from CRF 22 source HEVC to CRF 24-26 output is imperceptible on phones, tablets, and most TVs. The visible drop starts around CRF 28 on smooth gradients (sky, skin) and fast motion. Pick CRF based on viewing setup: 22-24 for living-room TV, 24-26 for laptop / tablet, 26-28 for messaging where the recipient watches on a phone.
Partially. The Windows playback problem has two parts: (1) Windows 10 / 11 don't include HEVC by default — install the HEVC Video Extensions from the Microsoft Store ($0.99), or check whether your PC vendor (Intel, AMD, NVIDIA driver bundles) ships a free OEM extension. (2) iPhone clips use the hvc1 codec tag; some older players prefer hev1. If you can't install the extension, convert to MP4 / H.264 via HEVC to MP4 instead of just compressing.
Only if the target device truly can't play HEVC. Converting to H.264 typically doubles file size at the same visual quality (HEVC is roughly 50% more efficient than H.264 per the H.265 standard's design goals). If the device supports HEVC, stay in HEVC and compress within the codec. Use HEVC to H.264 only when you need to send a clip to a 2015-era TV, older Android phone, or a Windows PC without the extension installed.
x265 (the standard HEVC encoder) uses a CRF scale where the "same number" produces a smaller file than x264 at comparable perceived quality — the x265 documentation positions CRF 28 in x265 as roughly equivalent to CRF 23 in x264. Defaults: 22 for archival, 24-26 for sharing, 28 for aggressive shrink. Each +6 CRF roughly halves the bitrate.
Yes. Leave the resolution preset on Original (or 2160p) and choose a higher CRF (24-26) or lower target percentage (40-50%) instead. A typical 4K iPhone clip of 250 MB drops to 80-120 MB at CRF 24 / 2160p — still 4K, much smaller.
It depends on browser and OS. Chrome 107+ supports HEVC on platforms with hardware decode (most macOS, recent Windows with HEVC extension installed, Android with HEVC silicon). Firefox 137+ added partial support; older Firefox builds don't decode HEVC. Safari 13+ on macOS and iOS plays HEVC natively. If you need a file that plays everywhere in-browser, the codec choice is H.264 — see HEVC to MP4 for that conversion.
HDR10 static metadata generally survives standard HEVC re-encoding. Dolby Vision and HDR10+ dynamic metadata depend on encoder support — most free / open-source encoders (including x265 in default builds) don't preserve Dolby Vision layers. If you have a Dolby Vision iPhone clip and need that metadata intact, keep the file untouched or use Apple's own export tools rather than re-encoding.
Yes — drop a full Camera Roll export folder in and each file processes with the same settings (CRF, resolution preset, trim). Files download individually or as a ZIP. For typical iPhone 4K clips, expect 60-90% size reduction at CRF 26 / 1080p, which is the most popular setting for social-sharing batches.
The audio track is preserved at its source bitrate by default; an iPhone HEVC clip's AAC audio (typically ~128 kbps) is tiny compared to the video track and isn't a meaningful size contributor. If you have a standalone AAC file you also want to shrink, see Compress AAC.