An 8K scene that stutters is either arriving too slowly or being decoded too slowly. Those are different problems with different fixes, and the test that separates them takes one download.
What you see, and what it means
- The test: download the scene and play it from local storage.
- Smooth locally: a bandwidth problem. Fix the network.
- Still stutters: a decode problem. Take a lower tier or a different codec.
- Published ceilings: 8192 x 4096 at 60 fps on a Quest 3, 7680 x 4320 at 60 on a Galaxy XR. Nobody else publishes one.
Run the test first
- Download the same scene you were streaming, at the same tier.
- Copy it to the headset or play it from a local network share.
- Watch the part that stuttered.
- If it is smooth, the decoder is fine and the problem is delivery. If it still stutters, the decoder is the limit.
If it is the network
The only published bitrate estimates in this market come from SexBabesVR: roughly 120 Mbps and up at 8K, 80 at 6K and 40 at 4K. Sustained, to a headset, over Wi-Fi.
Three things help, in order of effect. Move the headset onto a 6 GHz band if it has one: the Quest 3, Quest 3S and PICO 4 Ultra are Wi-Fi 6E or better, while the Apple Vision Pro is Wi-Fi 6 and cannot. Get closer to the access point, since 6 GHz does not travel through walls well. And make sure any server you are streaming from is wired, because two wireless hops is the worst case.
If it is the decoder
Meta documents 8192 x 4096 at 60 frames per second for 180 3D side-by-side on the Quest 3, and Samsung documents 7680 x 4320 at 60 for the Galaxy XR. For the Quest 3S, PICO, Vision Pro and PSVR2 nothing is published, so the limit is whatever testing reveals.
Two fixes. Take the tier below, which is usually 6K and almost always enough. Or take a different codec: if the studio offers H.264 as well as HEVC, the H.264 file is a lighter decode path even at the same resolution.
The ten-bit trap
VirtualTaboo and Dark Room VR encode their 5K, 6K and 7K tiers as ten-bit HEVC. Ten-bit at 7K is a heavier decode than eight-bit at 8K, so a file with a smaller number can be the one that stutters. If that is your situation, the H.264 version of the same scene is the fix rather than a lower HEVC tier.
Frame rate
Meta's decode figures are stated at 60 frames per second. SexLikeReal advertises many scenes at 90 or 120, which trades against resolution inside the same budget. If a high frame rate scene stutters where a normal one does not, that is why, and the fix is the 60 fps version if the platform offers one.
Other fixes are in the fixes section.
Why does 8K VR stutter on my Quest 3?
Almost always bandwidth rather than decode: Meta documents 8192 x 4096 at 60 frames per second, which covers a normal 8K scene. Test with a local file.
Can the Quest 3S handle 8K?
Meta publishes no decode ceiling for it, so there is no documented answer. Start at 6K and work up.
Why does a 7K file stutter when 8K plays?
Ten-bit HEVC, used by two studios at their top tiers. It is a heavier decode than eight-bit at a higher resolution.
Will a better router fix it?
If the local file plays smoothly, yes, and specifically one that gives you a clean 6 GHz band for the headset.