In short
- What studios ship: HEVC at the top tiers, H.264 below. One platform mentions AV1 at all.
- Headsets naming AV1: Quest 3 and above, Apple Vision Pro, Samsung Galaxy XR and PICO 4 Ultra.
- Players naming AV1: DeoVR, SKYBOX and 4XVR. The other five say nothing.
- Practical answer: take HEVC. AV1 is a capability waiting for content.
What each codec is
HEVC, also written H.265, is the compression standard this market runs on. It roughly halves the file size of H.264 at the same quality and every current headset decodes it in hardware. When a studio sells an 8K scene, this is almost certainly the codec inside it.
AV1 is newer and more efficient again, typically another twenty to thirty per cent for the same picture, and it is royalty free, which is why the streaming industry adopted it quickly. In VR that efficiency matters more than elsewhere, because the files are enormous and the wireless link is usually the bottleneck.
Who supports AV1, in their own words
Meta states that AV1 works on Quest 3 and above, which includes the Quest 3 and the Quest 3S, and separately notes that AV1 is not hardware decoded on the Quest 2. Apple names AV1 in the Vision Pro playback list. Samsung names it in the Galaxy XR codec table. PICO names it for the PICO 4 Ultra, in a PC-streaming context rather than for local playback.
Sony publishes nothing about AV1 for PSVR2, and on PC VR the question belongs to the graphics card.
Among players, three document it: DeoVR, which repeats Meta's Quest 3 and above condition, SKYBOX, and 4XVR, whose FAQ says Quest 3 only. HereSphere, Moon VR Player, Pigasus, PLAY'A and Prism VR publish nothing.
And the studios
This is where the comparison ends. One platform of seventeen mentions AV1: SexLikeReal lists H.264, H.265 and AV1 on some scenes. Everyone else ships HEVC at the top and H.264 below, and several publish no codec information at all.
So the practical answer for almost everyone is HEVC, because that is what exists. AV1 support on a headset is worth having for the future rather than for this month's downloads.
The ten-bit complication
Codec is not the whole story about how heavy a file is. Two studios, VirtualTaboo and Dark Room VR, encode their top tiers as ten-bit HEVC, which is a heavier decode than eight-bit HEVC at a higher resolution. If a 7K file stutters where an 8K one plays, the bit depth is why, and the fix is the H.264 version of the same scene rather than a smaller HEVC file.
The Windows trap
On a PC, HEVC is not automatically available. HereSphere's Steam listing states that the Microsoft HEVC Video Extension must be installed before H.265 files will play, and without it the player shows a black screen that looks exactly like a corrupt download. It is a one-off install and it accounts for most of the reports that a particular studio's files are broken.
Why the market has not moved
Encoding is the reason. AV1 is considerably more expensive to encode than HEVC, and a studio producing several scenes a week at 8K is running a lot of compute through that step. The saving is on the viewer's bandwidth, not on the studio's costs, so the incentive is weak until enough viewers cannot play HEVC, which will never happen.
The second reason is the installed base. HEVC decodes in hardware on every headset in this guide, including devices several years old. AV1 is restricted on Meta's platform to Quest 3 and above, so a studio shipping AV1 only would cut off its own customers. Shipping both doubles the storage.
Where AV1 does make sense is streaming, where the platform pays for the bandwidth and can pick the codec per device. That is presumably why SexLikeReal, the largest streaming catalogue here, is the one platform that offers it at all.
What to choose
- If a studio offers both, take HEVC. It is the format the market tests against and every current headset decodes it.
- Keep H.264 in mind as the fallback. It is the one codec nothing has ever failed to open, and it is what you want on older hardware or when something refuses to play.
- Take AV1 only where it is offered and your headset names support, which today means a Quest 3 or above watching SexLikeReal.
- On Windows, install the HEVC extension before deciding a file is bad.
How to tell which codec a file uses
Only one platform makes it easy. Czech VR Network prints the codec next to every resolution on the download tab, so you choose H.265 or H.264 knowingly. A few others label their top tiers in the file name, which is the next best thing.
Everywhere else you are reading clues: file size relative to resolution, the tier label, and whether the platform has said anything at all about codecs. Nine of the seventeen publish no codec information, which means the honest answer to "is this HEVC" is often that nobody has said.
Our HEVC page and AV1 page carry the full device-by-device position, and the codec glossary entry is the short version for anyone who just wants the definition without the market context around it.
Is AV1 better than HEVC for VR porn?
More efficient, yes, so the same quality in a smaller file. It barely matters today because only one platform of seventeen publishes AV1 scenes.
Does my headset support AV1?
Quest 3 and Quest 3S do, in Meta's own wording. Apple Vision Pro, Galaxy XR and PICO 4 Ultra name it. PSVR2 publishes nothing, and Quest 2 does not decode it in hardware.
Which player handles AV1?
DeoVR, SKYBOX and 4XVR document it. The other five players in this guide publish no AV1 statement.
Why will my H.265 file not play on Windows?
The Microsoft HEVC extension is missing. It is required before HereSphere will play H.265.
Other head-to-heads are in the comparisons index.