Initializing... drag & drop files here
Supports: HEVC, MOV, MP4, M4V, MKV
HEVC (H.265) and AV1 are both modern, highly efficient codecs from the same generation, so this is a lateral move, not an upgrade — you won't gain quality, and AV1 isn't dramatically smaller than HEVC at the same quality. The real reason to convert is licensing and web reach: AV1 is royalty-free and has broad native browser support, while HEVC carries patent-royalty baggage and patchy web playback. If your video lives in a web, streaming, or open-source pipeline, convert to AV1. If you mainly need playback on Apple devices and the file is already small, staying on HEVC is fine.
| Property | HEVC (H.265) | AV1 |
|---|---|---|
| Full name | High Efficiency Video Coding | AOMedia Video 1 |
| Standardized by | ITU-T / ISO-IEC (MPEG) | Alliance for Open Media |
| Released | Approved January 2013 | Bitstream spec March 28, 2018 |
| Licensing | Patent-encumbered, multiple royalty pools | Royalty-free and open |
| Efficiency | ~50% smaller than H.264 at equal quality | ~30% smaller than HEVC at equal quality |
| Encode speed | Slow | Very slow (commonly several times slower than HEVC) |
| Hardware decode | iPhone 6+, Apple Silicon, Intel 7th gen+ | Mainstream silicon from ~2022 (Intel Arc, RTX 30/40, Apple M3, Snapdragon 8 Gen 2) |
| Browser playback | Safari and Edge with hardware; Chrome 107+ hardware-only; not in Firefox | Chrome 70+, Firefox 67+, Edge 121+, Safari 17+ (partial), ~93% global |
| Best for | Apple-ecosystem capture, 4K/HDR originals | Web video, YouTube, open and royalty-free pipelines |
.hevc raw H.265 stream or an HEVC clip in MP4/MOV/MKV. Batch conversion is supported.The advanced panel exposes several ways to control the AV1 encode. Pick one based on whether you care more about a size ceiling or a quality floor:
| Output mode | What it controls | Best for |
|---|---|---|
| Quality Preset (Very High default) | A named quality target the encoder maps to an internal level | Most conversions — set it and go |
| Constant Quality | A fixed perceptual-quality level via CRF (AV1's CRF runs 16–63; lower means higher quality) | Archival or when quality matters more than exact size |
| Specific file size | An exact MB target the encoder scales bitrate to hit | Fitting an upload cap or storage budget |
| Constant Bitrate | A steady Kbps/Mbps rate across the whole clip | Streaming with a fixed bandwidth budget |
| Variable Bitrate | Target/min/max bitrate that flexes with scene complexity | Best quality-per-byte when size can vary |
| Constraint Quality | CRF combined with a maximum-bitrate ceiling | Capping bitrate peaks while staying quality-locked |
No. Both are modern lossy codecs, and re-encoding cannot recover detail that HEVC already discarded — every lossy-to-lossy pass can only lose a little more, never add quality. At best, a high-quality AV1 encode looks visually indistinguishable from the HEVC source. Convert for licensing and web compatibility, not for a quality boost.
Not dramatically. AV1 is roughly 30% more efficient than HEVC at equal quality, so at the same visual quality you may see a modest reduction, not a half-sized file. If you push quality lower you will get a smaller file, but you trade away detail. The headline reason to convert is that AV1 is royalty-free and web-native, not that it shrinks an already-efficient HEVC file by a lot.
AV1 encoding is computationally heavy and commonly runs several times slower than HEVC encoding, which is itself slow. A large or high-resolution HEVC file can take a long time to re-encode to AV1. This is a known tradeoff of the codec, not a problem with the file — using a Quality Preset rather than a very low bitrate target keeps encode times more predictable.
A raw .hevc file is a video-only elementary stream — it holds H.265 picture data with no audio track and no container metadata. Because there is no source audio to transcode, the AV1 output is silent by design, even though an audio codec (Opus by default) is listed in the options. If your footage originally had sound, that audio lives in the container that wrapped the stream — an .mp4, .mov, or .mkv — so convert that file instead, for example MP4 to AV1, and the audio track comes across with the video.
AV1 supports HDR10 and HLG, so standard HDR can survive a careful re-encode. Dolby Vision is more fragile across a codec change and may be dropped or flattened to standard HDR. If preserving Dolby Vision exactly matters, keep the original HEVC stream rather than re-encoding to AV1.
For browsers, yes. AV1 plays natively in Chrome 70+, Firefox 67+, Edge 121+, and Safari 17+ (partial), reaching roughly 93% of global users, and YouTube serves AV1. HEVC playback in browsers is limited to Safari and Edge with hardware support and Chrome 107+ hardware-only, and Firefox does not play it at all. That web-reach gap, plus AV1 being royalty-free, is the main reason to convert.
Not necessarily. Any modern browser decodes AV1 in software, and recent silicon (Intel Arc, NVIDIA RTX 30/40, Apple M3, Snapdragon 8 Gen 2) adds hardware decode for smooth high-resolution playback. On older devices without that chip, AV1 falls back to CPU decoding, which can stutter above 1080p — in that case an HEVC to MP4 H.264 conversion is the safer target.
Files are uploaded over an encrypted connection, processed on our servers, and deleted automatically a few hours after conversion. There is no sign-up, no watermark, and your files are never shared or made public. In our testing, a 1080p HEVC clip re-encoded to AV1 at the Very High preset stayed close to the source size while producing a clean, license-free output ready for web embedding.