HEVC launched in two stages: ratification in January 2013, publication in June 2013.
2:10
The Efficiency Claim
HEVC achieves 25–50% bitrate reduction over AVC—but only at the cost of higher complexity.
3:38
The Transform Shift
HEVC replaces fixed 4×4 and 8×8 DCT blocks with adaptive 4×4 to 32×32 blocks using both DCT and DST.
4:53
The Joint Standard
HEVC was built by the JCT-VC—a formal merger of MPEG and VCEG.
6:20
The Licensing Trap
Every HEVC implementation risks patent infringement—because core technologies are owned by JCT-VC participants.
Worth your time?
Yes. Study the whole thing.
3.5/ 5
What works
25–50% compression gain vs AVC
8K support
adaptive block transforms
What does not
delivers consistent 50% gain
reduces complexity
avoids licensing friction
Study it if
video platform engineers
broadcast infrastructure teams
hardware codec designers
Skip it if
small developers
open-source-only projects
low-power edge devices
The written brief1 min read
What it is and the problem it solves
HEVC is a 2013 video compression standard. It solves the problem of high bandwidth demand for HD and UHD video. It targets halving bitrate versus AVC HP at equivalent quality.
How it works
HEVC uses both integer DCT and DST with block sizes from 4×4 to 32×32. It was standardised by the JCT-VC, a joint body of ISO/IEC MPEG and ITU-T VCEG. It incorporates patented technologies owned by JCT-VC participants.
What works
HEVC delivers 25–50% better compression than AVC at the same quality. It supports resolutions up to 8K. The first version was ratified in January 2013 and published in June 2013.
What does not
HEVC does not deliver the promised 50% bitrate reduction across all content types or encoders. Its patent licensing regime fragmented adoption. It does not reduce complexity—it increases it.
What it changes
HEVC changes the cost structure of video delivery: lower bandwidth but higher CPU, memory, and legal overhead. It shifts engineering effort from transport to encoding and licensing.
Is it worth your time
Yes—if you encode at scale and need bitrate savings that justify doubling computational load. No—if you lack licensing capacity or cannot absorb the complexity penalty.