H.264 vs H.265 vs AV1: Video Codec Comparison (2026)
What These Three Codecs Actually Are
H.264, H.265, and AV1 are video compression standards. Think of them as algorithms that shrink enormous raw video files into something you can actually store and stream. A single minute of raw 1080p60 video is about 12 GB. A codec's entire purpose is to intelligently throw away visual information your eyes won't miss while keeping what they will. H.264, standardized way back in 2003, became the undisputed king of video. It powered everything from Blu-ray discs to the early days of YouTube. It's backed by a patent pool managed by Via LA, which meant commercial users often faced licensing fees, though enforcement was famously inconsistent over the years. H.265 (or HEVC) showed up in 2013 with a big promise: 40–50% better compression than H.264 for the same visual quality. But its royalty situation quickly devolved into a complete mess. Multiple, competing patent pools created so much legal fog that major players like Apple, Google, and Mozilla refused to support it in their web browsers for years. AV1 is the direct, royalty-free answer to that chaos. Developed by the Alliance for Open Media—a huge coalition including Google, Apple, Netflix, Amazon, and Intel—AV1 was finalized in 2018. It targets another 30% jump in efficiency over H.265. Because it's free for everyone to use, all major browsers now support it, and hardware decoding is standard on most devices sold since 2022. This history isn't just trivia. The right codec for a job isn't just about technical specs. Real-world factors like licensing costs, hardware support, and encoding speed are just as important as pure compression efficiency.
Compression Efficiency: The Numbers That Actually Matter
Codec comparisons can get hand-wavy about quality, so let's look at hard numbers from published research. Netflix ran a massive comparison in 2020, testing all three codecs at matched VMAF scores (a robust perceptual quality metric). For 1080p content at a high-quality VMAF 93, they found H.265 needed about 45% less bitrate than H.264. AV1, in turn, needed about 35% less bitrate than H.265. That puts AV1 at a 60–65% total reduction compared to the old H.264 standard. What does this mean for file sizes? A 90-minute movie that's 4 GB in H.264 might shrink to 2.2 GB in H.265, and drop to just 1.5 GB in AV1, all at an acceptable streaming quality (VMAF ~85). For a service like Netflix delivering millions of streams, that's a game-changing difference in bandwidth costs. For archiving your personal video collection, the savings are nice but maybe not as revolutionary. The catch is encoding speed. Those efficiency gains come at a steep computational cost, especially for AV1. Using the original libaom-av1 encoder at its default 'good' preset (cpu-used=4), a modern 8-core CPU might only churn through 1080p video at 15–25 fps. For comparison, H.264 using the classic libx264 encoder on 'medium' preset flies at 150–300 fps on the same machine. Thankfully, the SVT-AV1 encoder, developed by Intel and Netflix, dramatically closes that performance gap. At preset 6, SVT-AV1 can hit 80–120 fps for 1080p content while still handily beating H.265 on compression. This is the encoder CocoConvert uses for AV1 output, which is how we deliver finished files in minutes, not hours. H.265 encoding with libx265 sits right in the middle, typically running at 30–60 fps for 1080p at its medium preset. It's a noticeable step down from H.264's speed but still much faster than the original AV1 encoders.
Browser and Device Support in 2026
Device support has shifted so dramatically that the old advice—'just use H.264 for everything'—is now dangerously outdated. You need more nuance. H.264 is still the undisputed champion of compatibility. Every browser, smart TV, and phone from the last decade will play it without a problem. If you’re sending a video to a wide, unknown audience, H.264 remains the safest bet. It just works. H.265 is a different story. Hardware support is widespread, but software support is a minefield. iPhones have decoded HEVC in hardware since the iPhone 7 (2016). Android support depends on the chipset; a flagship Snapdragon 835 or later is fine, but budget MediaTek chips from 2019-2021 are a gamble. On desktop, Safari supports HEVC out of the box, but Chrome and Firefox only do if you have the right hardware and OS-level codecs. The real headache is Windows, where you might have to tell a user to buy the $0.99 HEVC Video Extensions from the Microsoft Store. This fragmentation makes H.265 a poor choice for general web delivery. AV1, meanwhile, has become the clear winner for modern web streaming. Chrome, Firefox, Edge, and even Safari (since 16.4) all support it. Hardware decoding is now common: it's in Apple Silicon Macs, Intel 11th-gen CPUs and later, AMD RDNA2 GPUs and later, Nvidia RTX 30-series GPUs and later, and almost any Android device with a 2022 or newer SoC. It's no surprise that YouTube and Netflix now default to AV1 for a huge portion of their streams. For CocoConvert users, the choice is clear. If your website analytics show a modern audience using up-to-date browsers, AV1 is an excellent choice. But if you're making files for a corporate intranet still running locked-down Windows 7 machines, H.264 isn't just a good idea—it's mandatory. A quick note for professionals: CocoConvert's AV1 output is tuned for web delivery. We don't currently support embedding Dolby Vision HDR metadata within AV1 in an MP4 container, a feature some high-end workflows require. For that specific use case, H.265 in an MKV or MP4 container is still the industry's go-to option.
Which Codec to Choose for Common Use Cases
Forget a single 'best' codec. The right choice depends entirely on what you're doing. Here’s a breakdown for common scenarios. **Uploading to YouTube or social platforms:** Don't overthink it. Encode your master file in H.264 at a very high bitrate (YouTube suggests 10–20 Mbps for 1080p, 35–68 Mbps for 4K) and upload that. The platform is going to re-encode it into multiple formats and qualities anyway, including AV1, VP9, and H.264. Sending them a pre-made AV1 file doesn't help you; they're just going to transcode it again. **Archiving raw footage:** H.265 is the workhorse here. It offers a fantastic balance of compression and quality, and it's supported by every major video editor like Premiere Pro, DaVinci Resolve, and Final Cut Pro. You get significant space savings over H.264 without AV1's extreme encode times. A 10-bit H.265 file in an MKV container at CRF 18 is a solid format for footage you want to preserve but aren't actively editing. **Self-hosted web video:** This is where you can be smart. Use AV1 at CRF 32–38 (SVT-AV1 scale) as your primary source, with an H.264 version as a fallback. The HTML5 `<video>` element makes this easy. This setup gives modern browsers a superior, low-bandwidth experience while ensuring near-100% compatibility for older devices. **Sharing with family or non-technical recipients:** H.264 in an MP4 container. No exceptions. It will play on their Samsung TV, their Windows laptop, their iPad, and their five-year-old Android phone without any codec installation prompts. You'll save yourself a support call. **4K HDR content:** H.265 with HDR10 metadata is the most reliable option today. While AV1 with HDR10 does work in Chrome and Firefox, support in standalone media players is still spotty. For Dolby Vision, you're pretty much locked into H.265 or H.264 in very specific container setups. AV1 with Dolby Vision is still a future-facing format that hardware hasn't fully caught up with. When you use CocoConvert, we've mapped these use cases to our output profiles. 'Web Compatible' gives you a universal H.264 file, 'Modern Web' uses our optimized AV1 pipeline, and 'Archive Quality' defaults to H.265 Main10 to preserve quality and HDR data.
Quality Settings That Actually Make a Difference
Codec choice is only half the battle. A poorly configured H.265 encode can easily look worse than a well-tuned H.264 encode at the exact same file size. The settings matter immensely. All three codecs use a rate control mode called CRF (Constant Rate Factor), where you pick a quality level and let the encoder figure out the bitrate. Lower numbers mean higher quality and bigger files, but the scales are different for each codec: - H.264 (libx264): CRF 18 is often considered visually lossless. CRF 23 is a great default for high quality, and CRF 28 is solid for low-bandwidth streaming. - H.265 (libx265): The scale is different. CRF 24 here is roughly equivalent to H.264's CRF 23 in perceived quality. CRF 28 is a common target for streaming. - AV1 (SVT-AV1): The scale is wider (0–63). A CRF of 35 is a good starting point, roughly equivalent to H.264 at CRF 23. Beyond CRF, the encoder preset has a huge impact on efficiency. Using the 'veryslow' preset with libx264 can shrink a file by 10–15% compared to 'medium' at the same CRF. It takes forever, but for a final archival encode, it's worth it. For batch jobs where time is money, 'fast' or 'faster' is a perfectly fine trade-off. Here's a critical tip for H.265: always add `-tag:v hvc1` when you're creating an MP4 file for Apple devices. Without this tag, QuickTime and iOS will simply refuse to play the video, even though the codec is supported. Anyone who has fought with video compatibility on Apple products knows this specific frustration. It's an easy-to-miss detail that CocoConvert handles automatically for all H.265 MP4 outputs. For AV1, the `--film-grain` parameter in the SVT-AV1 encoder is brilliant. It lets you synthesize film grain on the decoding side instead of trying to encode it, saving a ton of bitrate on noisy source material. A value of 8–12 works well for grainy film; for clean digital video, leave it at 0. Finally, don't overlook two-pass encoding. If you need to hit a specific bitrate target, a two-pass encode analyzes the video on the first pass to distribute bits more intelligently on the second. This almost always yields visibly better quality than a single-pass VBR encode at the same average bitrate. It's why CocoConvert's 'Streaming Optimized' profiles use this method.
Hardware Encoding: Speed vs. Quality Tradeoffs
Software encoders like libx264, libx265, and SVT-AV1 give you the absolute best quality for a given file size, but they can be painfully slow. The alternative is hardware encoding, which uses dedicated chips on your GPU or CPU. These are blazing fast—often 10-50x faster—but the tradeoff is a larger file, typically 20-40% bigger for the same visual quality. Nvidia's NVENC, AMD's AMF, and Intel's Quick Sync are the big three. NVENC supports H.264, H.265, and (on RTX 40-series and newer) AV1. AMF handles H.264 and H.265, with AV1 support arriving on RDNA3 GPUs. Intel's Quick Sync has supported all three since their 12th-gen CPUs. The quality gap between hardware and software encoding is also shrinking. For many types of content, the AV1 encoder on Nvidia's RTX 40-series GPUs is genuinely competitive with the software-based SVT-AV1 at its faster presets (6-8). For live streaming or screen recording where you need results in real-time, hardware AV1 is no longer a major compromise; it's a fantastic option. CocoConvert's conversion pipeline, however, uses software encoding exclusively for all formats. This is a deliberate design choice. As a cloud service, we prioritize consistent, reproducible quality regardless of the underlying server hardware. Software encoders deliver that reliability. The tradeoff is that processing very long files, like feature-length movies, can take longer than it would on your local desktop with a new GPU. A 2-hour 4K video being converted to AV1 might take 20-45 minutes depending on server load. We believe in being upfront about this, as it helps you decide if our service is the right tool for your specific job. If you're batch-converting a huge library, a local FFmpeg script using hardware encoding might be a more practical path.
The Practical Bottom Line
The codec landscape in 2026 has a much clearer hierarchy than it did just a few years ago. AV1 has decisively won the battle for web streaming; it’s royalty-free, widely supported, and offers superior compression. H.265 is the right tool for archival, professional workflows, and distributing 4K HDR content where AV1 support can still be shaky. H.264 is the universal fallback, the one you use when you have no idea what device will be playing the file. For most people using CocoConvert, this simplifies the decision nicely. Choose 'Web Compatible (H.264)' for maximum reach. Pick 'Modern Web (AV1)' for your own website or app if you know your users have modern devices. And use 'Archive (H.265)' to store high-quality footage for the long term. It's also important to know what CocoConvert is built for. We excel at converting between these three codecs for web and archival use, applying battle-tested quality settings automatically, and handling the tricky container details (like that `hvc1` tag) that often trip people up with manual FFmpeg commands. Where you'll want a different tool is for batch-processing massive libraries, professional mastering workflows that need frame-accurate metadata, or complex Dolby Vision HDR authoring. The best way to see the difference is to test it yourself. Don't just rely on benchmark charts. Upload a short, representative clip of your own content—30 to 60 seconds is plenty—and compare the outputs. The real-world differences in file size and visual quality on your own video will tell you everything you need to know.