Why Wireless VR Is the Hardest Thing Your Wi-Fi Will Ever Do
A wireless VR headset can demand more than ten times the bandwidth of a 4K Netflix stream — and it is far less forgiving about delay. When you stream a movie, the app buffers seconds ahead, so a momentary dip in Wi-Fi speed goes unnoticed. Wireless VR cannot do that. Every frame, for each eye, must be encoded and delivered fresh 72 to 120 times per second, and any hiccup arrives as visible stutter or, worse, motion sickness. That is why a Wi-Fi network that feels perfectly fast for laptops and phones can fall apart the moment a headset connects.
In practice, a wireless VR session needs roughly 150 to 450 Mbps of sustained throughput from the local network. That number surprises people who own gigabit internet plans, because the internet plan is not the part that matters. What matters is the Wi-Fi link between the gaming PC and the headset.
How VR Bandwidth Is Calculated
The math starts with the raw image data. Take a Quest 3-class headset running at 90 Hz: two eyes, 4,665,600 pixels each, 24 bits of colour per pixel, refreshed 90 times a second. That works out to:
Raw data = 2 eyes × 4,665,600 pixels × 24 bits × 90 Hz ÷ 1,000,000 ≈ 20,157 Mbps of raw image data
Your Wi-Fi never sees that raw stream. Compression shrinks it dramatically before transmission. The tool behind this guide uses compression ratios of about 50× for H.264, 80× for H.265 (HEVC), and 100× for AV1. Divide the raw figure by the codec's ratio and you get the recommended bitrate — the sustained speed your Wi-Fi must carry.
With AV1, the most efficient option, that works out to about 201.6 Mbps — roughly 40 percent of a measured 500 Mbps Wi-Fi link. On H.264, the same session needs more than double that, because H.264 only compresses the raw data about 50×.
Codec Choice: H.264 vs H.265 vs AV1
The codec is the single biggest lever on bandwidth demand. Headsets and streaming software (Steam Link, Virtual Desktop, Air Link) typically offer a choice between three options:
| Codec | Compression | Support | Best for |
|---|---|---|---|
| H.264 | ~50× | Widely supported | Older headsets and routers; lowest compatibility risk |
| H.265 / HEVC | ~80× | Broad on modern headsets | A solid middle ground of bandwidth and support |
| AV1 | ~100× | Newer headsets and GPUs | The lowest bandwidth demand, if your hardware encodes it |
If your PC's GPU can encode AV1 in real time and your headset can decode it, AV1 roughly halves the Wi-Fi demand compared with H.264. That alone can be the difference between smooth play and constant stutter on a busy network.
What the Numbers Look Like for Real Headsets
For a Quest 3-class headset at 90 Hz, the estimator lands near 201.6 Mbps with AV1 on a 500 Mbps measured Wi-Fi link — meaning the headset consumes about 40 percent of the link's headroom. Step up to 120 Hz and the raw data climbs proportionally, pushing the recommended bitrate higher. Stay on H.264 at 90 Hz and the demand roughly doubles, since compression is only about 50×.
The headroom number is the one to watch. A headset consuming 40 percent of a link has plenty of margin for interference, a partner's phone uploading photos, or the microwave oven firing up. The same headset on a congested 2.4 GHz link may consume nearly all of it, leaving no room for error.
Your Internet Plan Speed Is Irrelevant Here
This is the most misunderstood part of wireless VR networking. The VR stream travels only your local network between the PC and the headset. It never goes out to the internet. A 100 Mbps broadband plan with a great dedicated Wi-Fi 6 router will outperform a gigabit plan running through a congested all-in-one router three rooms away.
What actually matters is the local link: the Wi-Fi standard, the band (5 GHz or 6 GHz beats 2.4 GHz), the distance and walls between the PC and headset, and how many other devices share the airtime. Optimise the local network, not the broadband plan.
The Latency Budget Nobody Talks About
Bandwidth is only half the story. Motion-to-photon latency — the delay between moving your head and seeing the updated image — must stay low or VR feels wrong. The estimator breaks latency into three parts: an 8 ms tracking-and-display pipeline, your Wi-Fi standard's typical delay (about 15 ms on Wi-Fi 5, about 10 ms on Wi-Fi 6), and the codec's encoding delay.
A typical example: 8 ms pipeline + 10 ms Wi-Fi 6 + 18 ms AV1 = 36 ms, which is playable — fine for casual games, slightly noticeable in competitive ones. Wi-Fi 7 and a wired-access-point setup can shave the network portion further.
Fixes When Wireless VR Stutters
- Put the PC and headset on a dedicated 5 GHz or 6 GHz band — keep other devices on a separate network.
- Move the router into the same room, ideally line of sight, a few metres from the play area.
- Switch the codec to AV1 or HEVC if your GPU and headset support it — bandwidth demand drops immediately.
- Use a wired connection from the PC to the router; Wi-Fi on both ends doubles the interference.
- Drop the refresh rate from 120 Hz to 90 Hz if stutter persists — the raw data falls proportionally.
- Update the headset firmware and GPU drivers; encoding improvements land in updates regularly.
- As a last resort, switch to a USB-C link cable for the most demanding games — zero wireless compromise.
Try the Tool
Try it now: VR Wireless Streaming Bandwidth Checker — estimates the bitrate, latency, and network headroom your headset needs.
Frequently Asked Questions
How much bandwidth does wireless VR really need?
Most wireless VR sessions need 150 to 450 Mbps of sustained Wi-Fi throughput. The exact figure depends on resolution, refresh rate, and codec — a Quest 3-class headset at 90 Hz with AV1 needs about 200 Mbps, while H.264 at 120 Hz can need several times that.
Does wireless VR use my internet connection?
No. The stream travels only over your local network between the PC and the headset. Your broadband plan's speed is irrelevant to VR quality; what matters is the speed and stability of your local Wi-Fi link.
Why does my VR stutter even though my Wi-Fi speed test looks fast?
Speed tests measure one-off bursts to the internet, but VR needs sustained local throughput with low latency. Congestion, distance, walls, and other devices sharing the same band can all cause momentary drops that a speed test never shows. A dedicated 5 GHz or 6 GHz band close to the play area fixes most cases.