A flat 720p webcam stream needs about 3 Mbps. A stereoscopic 360° stream at the same perceived sharpness needs 18 to 25 Mbps because it's painting the inside of a sphere twice - once per eye. Push for 4K-equivalent VR and the number jumps past 50.

Buffering happens when the pipe between your headset and the server can't keep up. But raw download speed is only one piece. Latency (how long the round-trip takes) and jitter (how much that round-trip varies) matter just as much. A 100 Mbps connection that swings between 5 ms and 80 ms of ping will stutter more than a steady 30 Mbps line at 12 ms.

Run a speed test from inside the headset's own browser. Your phone or laptop may be on a different Wi-Fi band, in a different part of the room, and the result won't represent what the headset is actually getting.

Targets:
▸ ≥ 25 Mbps down for comfortable 1080p stereo VR
▸ ≥ 50 Mbps down for 4K stereo VR
▸ ≤ 50 ms ping to a major data center
▸ Jitter ≤ 10 ms

If any of those fail, fix the network before fiddling with headset settings.

1. Force the headset onto 5 GHz, not 2.4 GHz. Your router broadcasts both as separate SSIDs (or as one with band steering - disable steering if you're troubleshooting). 2.4 is crowded with every microwave and IoT device in the neighborhood.

2. Replace any router older than 2022. Wi-Fi 6 (802.11ax) is the line in the sand. A $120 TP-Link Archer AX55 outperforms a five-year-old high-end Wi-Fi 5 box in every relevant metric.

3. Move closer. Every drywall partition between the router and the headset costs about 15 dBm. Two walls turn a great connection into a buffering one.

4. Kill the bandwidth competition. A Netflix tab on the TV, a PS5 downloading an update, and an iCloud backup running on a phone will collectively eat enough headroom to break the stream. Pause them, or use router QoS (see below) to deprioritize them.

5. Try a wired adapter. Most modern headsets accept a USB-C to Ethernet adapter. Plugging into the wall removes every Wi-Fi variable in one move and is the single most reliable improvement available.

Meta Quest 3:
▸ Settings → Display → Refresh rate to 90 Hz. 120 Hz looks smoother for games but eats compute that the browser needs.
▸ Settings → Apps → Meta Browser → Storage → Clear cache. Do it weekly. Old service-worker caches can stall WebXR sessions.
▸ Disable Guardian if you're seated and stationary. Saves a few CPU cycles for the decoder.
▸ Close every other open app from the dock - they keep running.

Apple Vision Pro:
▸ Safari is largely tuned for this out of the box.
▸ Turn off Low Power Mode if it's on. It throttles the GPU.
▸ Close other Spaces and apps; the system gets aggressive about memory pressure with several immersive windows open.

Pico 4 / 4 Ultra:
▸ Switch to the Wolvic browser if buffering is persistent - its WebXR pipeline is noticeably leaner than the default.
▸ Display refresh to 90 Hz for the same reason as Quest.

Across all headsets: update firmware on a regular cycle. Browser releases routinely improve the video decoder.

Auto. The platform watches your bandwidth and adapts. Best default. Occasional dips during network hiccups but never a hard stall.

720p VR (~12 Mbps). Visibly soft. The right answer on hotel Wi-Fi or a tethered 4G hotspot.

1080p VR (~22 Mbps). The sweet spot for almost everyone. Sharp enough that skin and fabric have real texture, light enough to ride out a passing dip.

4K VR (~55 Mbps). Spectacular when it works. Only attempt on a wired connection or a same-room 5 GHz Wi-Fi 6 link. On anything weaker you'll stall.

If the stream stalls: drop one tier, give it 60 seconds, see if it recovers. If you're still stalling at 720p, the problem is network, not the platform.

Quality of Service. Most decent routers let you tag a device by MAC address as "high priority." Tag the headset, demote everything else. The headset wins arbitration when bandwidth tightens.

Channel selection. Run a Wi-Fi analyzer (NetSpot on Mac, WiFiman on Android) to find an empty 5 GHz channel and manually set the router there. Auto-channel selection at peak hours picks the same crowded channel every neighbor's auto-selection picked.

DNS. Switch the router to 1.1.1.1 (Cloudflare) or 9.9.9.9 (Quad9). Won't increase throughput but cuts first-load latency and improves how quickly a stalled connection rediscovers a server.

Bandwidth floor. If your router supports it, reserve 30 Mbps minimum for the headset. Stops anyone else's traffic from starving the stream.

Stream loads then freezes a minute in - Wi-Fi drop. Move closer to the router, force 5 GHz, restart the router if it's been up for weeks.

Blurry/mushy picture - Auto quality has downgraded you. Check throughput, manually lift quality if the network has headroom.

Audio drifting from video - High latency or CPU under load. Close other headset apps, reboot, switch to a lower refresh rate.

Works on a phone in the same room but not the headset - Headset browser cache. Clear it, update firmware, try a fallback browser (Wolvic on Pico, Firefox Reality where available).

Picture is smooth but head movement jerks - Frame rate problem, not a streaming problem. Drop refresh to 72 Hz and close everything else.

Work through these in order. Nine out of ten buffering complaints are solved before you reach the router section.