FFmpeg H.265 Vulkan Encoding Optimization Achieves Parity with H.264 Speed

FFmpeg’s video encoding performance has been significantly improved. Optimization patches applied to the Vulkan encoding path for the H.265 (HEVC) codec were merged into the FFmpeg Git repository on August 17, 2026. This change has brought the Vulkan encoding speed of H.265 to a level nearly equivalent to that of H.264.

According to a report by Michael Larabel of Phoronix, this patch fundamentally improves the performance of the hevc_vulkan encoder. Previously, at common quality levels, hevc_vulkan used much heavier encoding settings than h264_vulkan, resulting in a notable performance gap.

Traditional Challenges and Technical Background

Vulkan Video is an API that provides low-level access to GPU hardware encoders and decoders. The implementation of the Vulkan encoding path in FFmpeg is a key effort towards standardizing hardware encoding performance across platforms.

H.265 can reduce bitrates by up to 50% compared to H.264, but its encoding computational cost was high. This cost disparity remained a challenge and a barrier to adoption even in the Vulkan path. Specifically, there were issues with minimum CU (Coding Unit) settings and transform hierarchy processing, leading to some implementations producing undecodable HEVC bitstreams.

Specific Optimizations Applied

The commit message for the merged patch details the technical changes. The ALLOW_ENCODE_PARAMETER_OPTIMIZATIONS session flag was set, and changes were made to use a minimum CU of 16x16 when the CTB (Coding Tree Block) size is 32 or larger. The assignment of max_transform_hierarchy_depth_inter was also corrected.

During the application of the GetEncoded SPS feedback, synchronization of overwritten fields was added. This includes extent, conf_win, min/diff CU and TB sizes, and the transform hierarchy. Previously, only log2_diff was copied, which caused CtbLog2SizeY to become 7, leading to a problem where some implementations would generate undecodable HEVC after overwriting the minimum CU.

Performance Measurement Results and Comparison

The test environment used the testsrc2 sequence at 1080p resolution with quality setting 1 and 1000 frames. Before optimization, the performance of hevc_vulkan was approximately 200 to 317 fps, with h264_vulkan being faster.

After optimization, hevc_vulkan achieved 289/325/358 fps. This performance is virtually identical to h264_vulkan’s 288/317/359 fps. These results demonstrate that H.265 encoding can now compete with H.264 in the Vulkan path.

Phoronix’s article assessed this by stating, “HEVC Vulkan encoding performance has become faster than before and is now on par with H.264 encoding speed.”

Impact on the Open-Source Ecosystem

FFmpeg is foundational software for video processing, used widely from delivery platforms and game streaming to video editing tools. The acceleration of H.265 Vulkan encoding could speed up the movement towards leveraging hardware acceleration in more applications.

For GPU vendors with proprietary Vulkan video implementations, improved support in FFmpeg also leads to ecosystem expansion. As mentioned in the article Mesa Rusticl Enables Mali Panfrost by Default, the maturity of open-source graphics drivers is also proving effective here.

Industry Implications and Future Outlook

For video streaming services and video delivery platforms, this optimization holds significant meaning. H.265 excels in bandwidth efficiency, but its encoding cost was an adoption barrier. Achieving H.264-equivalent speed in the Vulkan path allows for simultaneous cost reduction and quality improvement on the service side.

In the fields of cloud gaming and real-time streaming, combining the low latency of Vulkan encoding with the high compression ratio of H.265 could enable high-quality streaming even under network bandwidth constraints. However, the adoption status of decoders and platform support remain challenges.

Editorial Opinion

In the short term, this optimization will have a concrete impact on the video streaming industry. H.265 excels in bandwidth efficiency, but its encoding cost was an adoption barrier. Achieving H.264-equivalent speed in the Vulkan path allows for simultaneous cost reduction and quality improvement on the service side. We may see more services accelerating their migration to H.265 in the coming months. In the long term, the maturity of the Vulkan Video API and the adoption of hardware encoders will accelerate. GPU vendors will work to enhance the implementation quality of Vulkan video extensions and strengthen collaboration with the open-source ecosystem. Over a 1 to 3-year span, H.265 is likely to solidify its position as the standard codec for the streaming industry, while the practical use of H.266 (VVC) is also coming into view, further intensifying the competition in encoding performance.

The question posed by the editorial team is what impact this optimization will have on cloud gaming and real-time streaming. Combining the low latency of Vulkan encoding with the high compression ratio of H.265 could enable high-quality streaming even under network bandwidth constraints.

References

• “FFmpeg Lands H.265 Vulkan Encode Performance Optimizations”, by Michael Larabel — Phoronix, 2026-08-17T20:14:03.000Z (ARR)
• Source URL: https://www.phoronix.com/news/FFmpeg-Faster-HEVC-Encode