Three Very Different Scenarios
- Wireless PCVR over local Wi-Fi (Virtual Desktop, Air Link, Steam Link VR) — PC and headset on your home network. Internet speed doesn't matter; your Wi-Fi does.
- USB-tethered PCVR (Quest Link via cable) — no network involved; cable bandwidth only.
- Cloud VR (Shadow PC, GeForce Now, Plutosphere) — rare but emerging. Your internet pipe matters here.
The first two cover 99% of users, and they're bound by Wi-Fi quality, not ISP speed.
Wireless PCVR: Minimum Wi-Fi Setup
| Requirement | Minimum | Recommended |
|---|---|---|
| Router | Wi-Fi 5 (802.11ac) dual-band | Wi-Fi 6 or Wi-Fi 6E, tri-band |
| Band | 5 GHz only (never 2.4 GHz) | 6 GHz if you have Wi-Fi 6E headset + router |
| Bandwidth to headset | ~150 Mbps sustained | 400+ Mbps sustained |
| Latency (headset to PC RTT) | <20 ms | <10 ms |
| PC connection | Ethernet to router | Ethernet, same router as headset |
| Distance | Same room as router | Within 15 ft line-of-sight |
Bitrate by Quality Level (Virtual Desktop, Air Link)
| Quality | Bitrate | What it looks like |
|---|---|---|
| Low | 50 Mbps | Visible compression, fine for seated games |
| Medium | 100 Mbps | Good for most games, minor artifacts on fast motion |
| High | 150 Mbps | Near-Link quality for most content |
| Ultra (Virtual Desktop Godlike) | 200-500 Mbps | Indistinguishable from wired Link; needs Wi-Fi 6E |
Quest 3 can decode up to ~500 Mbps H.264 or HEVC. Real-world sustainable rate depends on your Wi-Fi headroom.
Why ISP Speed Doesn't Matter for Wireless PCVR
The video stream is between your PC and your headset, both on your LAN. Traffic never leaves the router. You can run Virtual Desktop on a 25 Mbps home internet connection as long as your Wi-Fi handles the 100-400 Mbps LAN traffic. The only time ISP speed enters the picture is if your game also pulls from online servers (multiplayer, cloud saves), and those are small bandwidth users.
Router Placement and Network Rules for VR
- Headset and PC on the same router — don't bridge through a mesh node when possible. Each hop adds latency.
- PC connected via Ethernet — never put the PC on Wi-Fi if you can avoid it. A wired PC + wireless headset is the gold standard.
- Same room as the router — one wall cuts 5 GHz throughput 40-60%
- Turn off "band steering" — force the headset onto the 5 GHz SSID explicitly
- Dedicated SSID for VR (optional) — prevents interference from other devices' beaconing
- Use a channel with no overlap — 5 GHz 36-48 or 149-161 with 80 MHz width
- Disable QoS experiments — some routers' WMM Power Save logic breaks VR; turn it off if lag appears suddenly
Wi-Fi 6 vs Wi-Fi 6E vs Wi-Fi 7 for VR
- Wi-Fi 6 (5 GHz): 150-300 Mbps headset throughput in a quiet environment. Fine for high quality.
- Wi-Fi 6E (6 GHz): 400-800 Mbps, no competing devices on the 6 GHz band (yet). Enables Virtual Desktop Godlike.
- Wi-Fi 7 (with MLO): headset uses multiple bands simultaneously. 500+ Mbps stable even with other traffic. Overkill for most users today but future-proof.
Quest 2 supports Wi-Fi 6 (5 GHz only). Quest 3 supports Wi-Fi 6E. PSVR2 is wired.
USB Tethered Link
No network involved — the headset is a USB device to the PC. Requirements:
- USB 3 cable, at least 2.5 Gbps (USB 3.0). Not USB 2.0 — bandwidth is insufficient.
- USB-C port directly on motherboard — hub adapters sometimes cause frame drops
- Official Oculus Link cable or equivalent fiber-optic long cable (up to 16 ft) for room-scale
Cloud VR (Shadow PC, GeForce Now VR, Etc.)
This is where your internet speed matters. You need:
| Target | Required speed | Latency |
|---|---|---|
| Cloud-rendered VR, basic | 50 Mbps down | <30 ms to cloud server |
| Cloud-rendered VR, high quality | 100 Mbps down | <20 ms |
| Cloud-rendered VR, near-local | 150 Mbps down + 5G or fiber | <15 ms |
Cloud VR is extremely latency-sensitive because the frame path is: cloud renders → encodes → sends → headset decodes → display. Every millisecond beyond ~20 ms produces nausea. Shadow and similar services require being geographically close to a data center.
Fixing Stuttering and Lag
- Confirm Wi-Fi is 5 GHz or 6 GHz (not 2.4 GHz)
- Run a dedicated VR speed test from within Virtual Desktop — it tests LAN bitrate, not ISP
- Move closer to the router
- Wire the PC to the router
- Check for other high-bandwidth users on the same Wi-Fi (4K streams, downloads)
- Lower the bitrate one step and see if stability returns — that tells you if it's bandwidth or router CPU
- Update router firmware and headset firmware
- Consider a dedicated Wi-Fi 6 router just for VR if your main mesh isn't cutting it
Frequently Asked Questions
What internet speed do I need for Quest VR?
For PCVR over Wi-Fi (Virtual Desktop, Air Link), internet speed doesn't matter — the video streams locally between your PC and headset. You need strong 5 GHz or 6 GHz Wi-Fi delivering 150-400+ Mbps locally. For online multiplayer games the Quest plays natively, any modern home internet (25+ Mbps) is enough.
Why is my wireless VR stuttering?
Usually Wi-Fi, not internet. Move closer to the router, confirm you're on 5 GHz (not 2.4), wire your PC to the router, and check if other devices are saturating the Wi-Fi. Lowering the bitrate one step diagnoses whether bandwidth or latency is the bottleneck.
Is Wi-Fi 6E necessary for PCVR?
Not necessary — Wi-Fi 6 on 5 GHz handles Virtual Desktop at High quality (150 Mbps) cleanly in most homes. Wi-Fi 6E unlocks higher bitrates (200+ Mbps, Godlike quality in Virtual Desktop) and removes competition from other Wi-Fi devices. Worth upgrading if your current setup stutters at High quality.