Profiles, levels and tiers
A decoder is built to limits: which coding tools it implements, how large and how fast a picture it can handle, how many bits per second it can take in. A stream declares the limits it stays within, which helps a device check before decoding whether its decoder supports them. Those declarations are the profile, the level and, in the newer formats, the tier.
Three kinds of limit
Find the level
Set a picture size, a frame rate and a bitrate to check. For each format the table gives the lowest level, in that format's encoder's level table, that passes the size, rate and bitrate checks used here: x264's table for H.264 in its High profile, x265's for High Efficiency Video Coding (HEVC), libaom's for AV1 in profile 0. H.264 counts in 16×16 macroblocks; the other two count pixels.
This is a partial check, not conformance: buffer limits and AV1's decode rate, among others, are left out. The bitrate is one assumed rate compared with each ceiling, not a model of bursts or of the decoder's buffer. The lowest level is taken first, High tier included, so a device limited to the Main tier may need a higher level than shown.
| Format | Level that passes | Tier | Its bitrate limit |
|---|---|---|---|
| H.264, High | |||
| HEVC | |||
| AV1, profile 0 |
For 1920×1080 at 30 frames a second and 8 Mbit/s:
- All three tables put it at level 4 (written 4.0 in AV1) by these checks. It is 8,160 macroblocks a frame and 244,800 a second, just under the 245,760 that x264's table allows at level 4.
- A limit left out can change the answer. x264's table lets level 4 hold 32,768 macroblocks of decoded pictures: four of these frames fit and five do not, and the demo has no input for how many a stream keeps.
- Doubling the frame rate raises the level: 4.2 in H.264, 4.1 in HEVC and AV1.
- Bitrate alone can raise it, or change the tier. At 20 Mbit/s HEVC and AV1 stay at level 4 and move to the High tier, with a limit of 30 Mbit/s; the Main tier of level 4.1, with a limit of 20 Mbit/s, passes too, and the demo shows level 4 because it takes the lowest level first. H.264 has no tiers: level 4 holds up to 25 Mbit/s, and at 30 Mbit/s the stream is level 4.1.
- 3840×2160 at 30 frames a second and 20 Mbit/s is level 5.1 in H.264, 5 in HEVC and 5.0 in AV1.
In the encoders
x264 and x265 name a profile and a level themselves unless you set them, and libaom checks the sample format against the AV1 profile. In x264, --profile restricts tools and refuses a request it cannot hold; it converts nothing.
How x264, x265 and libaom choose and check
- Profile from the tools in use, in x264. 4:4:4 or lossless coding gives High 4:4:4 Predictive; 4:2:2 gives High 4:2:2; more than 8 bits gives High 10; the 8×8 transform, a quantization matrix or monochrome gives High; binary arithmetic coding, B-frames, interlacing or weighted prediction give Main; otherwise Baseline. Given
--profile baseline, the 8×8 transform, arithmetic coding, B-frames and weighted prediction are switched off. Lossless coding, 4:4:4, 4:2:2, more than 8 bits or monochrome under a profile that lacks it stops x264 with an error. - The automatic level. With no
--level, x264 takes the first row of its table that passes its checks. x265 does the same, and moves to the High tier when the bitrate or the buffer size is over a level's Main limit and within its High limit, unless--no-high-tierforbids it. The bitrate each tests is the buffer model's maximum rate; without one, x265 uses the bitrate target, and x264's automatic choice in average bitrate mode uses twice the target. - Sample formats in libaom. Among its checks, it refuses 4:4:4 input in profile 0, monochrome in profile 1, 4:2:2 outside profile 2, and 12 bits below profile 2.
Trade-offs
- Compatibility can constrain coding choices. A profile that excludes a useful tool may cost compression efficiency. A lower level restricts resources such as picture size, processing rate and buffers; changing the level label alone changes neither the coded pictures nor their quality. Choose limits the intended decoders support.
- The level is a promise, not a setting that enforces itself. x264 warns when the stream it is asked to make exceeds the level requested; keeping within the bitrate limit is the job of the buffer model.
- A stated level can be higher than needed. A decoder that goes by the label may then refuse a stream it could have played.
Sources
Read 2026-11-15, at the commits linked. The buffer checks, the bitrate each encoder tests, the requests --profile refuses and libaom's profile factor were read 2026-11-16.
- x264 at commit c24e06c (GitHub mirror): the level table in
common/tables.c; inencoder/set.c, the profile chosen from the tools in use,x264_validate_levelsand its bitrate factor by profile, its decoded picture buffer check and its buffer size check; the automatic level and the doubled target it tests inencoder/encoder.c;x264_param_apply_profileand what Baseline switches off and the requests it refuses incommon/base.c;--profileand--levelin the option list. - x265 at commit 4191822: in
source/encoder/level.cpp, the level table, the loop that picks the level, the bitrate it tests and the choice of tier, which tests the buffer size too;high-tierinsource/common/param.cppand--no-high-tierin the option list. - libaom at commit 1b7f9ef (GitHub mirror): the level table in
av1/encoder/level.c, with the decode rates of levels 5.2 and 5.3, which the demo does not use, the bitrate factor by profile and the conformance check's test of average bitrate; the profile checks inav1/av1_cx_iface.cfor monochrome, 12 bits, 4:4:4 and 4:2:2. - Not checked: the specifications' own tables, which these three are taken to copy; HEVC's and AV1's profiles beyond what is listed; libaom's level conformance code beyond the two lines cited; any profile factor for HEVC, which x265's level search does not apply; profiles and levels of Versatile Video Coding; which devices support which level.