VRHow / XR Technology / Refresh rates in VR

Refresh rates in VR

Short answer: Refresh rate is how often a headset updates its displays, measured in hertz (Hz). A higher number can make head and hand motion look smoother and reduce the time each image is held, but it also gives the game or app less time to render every frame. In VR, a steady lower rate is usually better than an ambitious rate that repeatedly misses its deadline.

Last checked October 11, 2026. This is an evidence-led explainer, not a hands-on headset review: VRHow has not independently tested the devices discussed here, and settings, firmware and regional product availability can change.

What the number actually measures

At 90 Hz, the display presents a new refresh opportunity every 11.1 milliseconds. At 120 Hz, the interval is 8.3 ms. That is a display schedule, not a promise that a game is producing 90 or 120 genuinely new frames every second. Unity describes VR as synchronized to the active XR runtime rather than benefiting from rendering faster than the display can refresh; its runtime can also predict head pose to reduce latency before a frame arrives. Unity’s frame-timing documentation explains the prediction and synchronization model.

The practical distinction is between refresh rate (the panel’s cadence), render frame rate (how fast the application produces images), and motion-to-photon latency (how long an input or head movement takes to affect what you see). They interact, but they are not interchangeable. A 120 Hz headset does not turn a poorly optimized scene into a 120-fps experience.

Why missed frames feel worse in VR

Every refresh is a deadline. If an app misses it, the runtime may show the previous frame, rotate that frame to match the latest head pose, or use a more involved reprojection technique. Unity notes that the first fallback looks like judder, while rotational reprojection can work for static content but does not correctly represent animated or positionally moving objects. Read the documented dropped-frame behavior.

This is why “highest Hz” is a poor buying or settings rule. At 72 Hz the frame budget is about 13.9 ms; at 90 Hz it is 11.1 ms; at 120 Hz it is only 8.3 ms. Meta’s current developer table makes the same trade-off explicit, listing budgets from 13.9 ms at 72 Hz down to 8.3 ms at 120 Hz, and warning that inconsistent performance can cause judder and peripheral artifacts. Meta’s refresh-rate guidance includes the budgets and failure modes.

Does higher refresh rate reduce motion sickness?

It can help some people, but it is not a cure and the evidence does not justify treating one setting as universally comfortable. A faster cadence can make head-controlled motion appear less stuttery and can reduce the display time per frame. Yet a high setting paired with missed frames, thermal throttling or unstable streaming can be more uncomfortable than a stable lower setting. Comfort also depends on camera movement, latency, tracking, optics, brightness and the individual user. For a broader explanation of how the headset’s tracking and display fit together, see how VR works and our VR tracking explainer (planned companion pages).

Do not confuse refresh rate with persistence or motion blur. A panel may update frequently while the rendered image, optical characteristics or software motion still produce blur. Meta specifically says the perceived blur change at its extended Quest 3 rates depends on scene contrast and motion speed, so a specification alone cannot predict what every application will look like. See Meta’s context and limitation for extended rates.

Common settings in context

Refresh rate	Time per display interval	What it demands
72 Hz	13.9 ms	More rendering headroom; a sensible stability target for demanding scenes
90 Hz	11.1 ms	A common middle ground for smoothness and workload
120 Hz	8.3 ms	More demanding; useful only if the app and device sustain it
144 Hz and above	6.9 ms or less	Specialized support; verify the exact headset, runtime and content path

These are timing examples, not a ranking. Device support differs: Meta’s April 2026 Unreal rendering page lists 72/80/90/120 Hz for Quest 2, Quest 3 and Quest 3S, and 72/80/90 Hz for Quest Pro, while its newer page documents additional Quest 3 rates under specific OpenXR and Horizon OS conditions. Check the baseline Meta table and the version-qualified extended-rate documentation rather than assuming a headset’s panel supports every advertised number.

How to choose a setting without guessing

Start with the application’s stable target. Use the headset’s performance overlay or the developer profiler to see frame rate and frame time during the busiest scene, not just a menu. Unity’s guidance gives a simple diagnostic: GPU-bound work appears as longer XR.WaitForGPU, while CPU-bound work can exceed the frame budget without the same GPU wait. Use the Unity diagnostic explanation if you are developing.
Prefer consistency over a peak number. If 120 Hz causes recurrent reprojection or judder, try 90 Hz and spend the recovered budget on resolution, shadows or fewer effects. Lowering graphics is not automatically a failure; it is a trade between image richness and timely delivery.
Test the workload that matters. A light rhythm game, competitive shooter or simple high-contrast scene may benefit more from high refresh than a dense simulation. Meta describes these as plausible candidates for extended rates, while dense scenes and heavy post-processing are poorer fits. That is platform guidance, not an independent performance ranking.
Check the entire path. On PC VR, the game, runtime, GPU, encoder, network and headset must all deliver on time. A wireless connection can add latency or variability even when the panel is set to 90 or 120 Hz. On standalone devices, heat can change the result: Meta documents dynamic throttling that can lower a higher rate when thermal conditions rise.

Questions worth asking before comparing headsets

Is the quoted rate a supported application mode, a media-only mode, a developer option, or merely a panel capability?
At that rate, what resolution and rendering scale are used? Meta documents 240 Hz Quest 3 operation with display scaling above 207 Hz, trading image quality for bandwidth.
Can the runtime report and select the rate at runtime? OpenXR’s specification includes an unsupported-rate error, and Unity’s Android XR utilities say a request fails when the value is not in the device-reported list. See the OpenXR specification and Unity’s display-utilities example.

The useful conclusion is not “buy the most Hz.” It is: choose the highest mode your real content can sustain with acceptable clarity, latency and thermals, then verify it after updates. Refresh rate is one part of the display experience alongside resolution and optics; it cannot compensate for a soft image, poor tracking or unstable frame delivery.

Sources

Meta Horizon OS Developers: Set Display Refresh Rates — definitions, device modes, frame budgets, throttling and Quest 3 caveats (updated October 1, 2026).
Meta Horizon OS Developers: Rendering — baseline Quest target rates and missed-frame implications (updated April 14, 2026).
Unity Manual: Virtual reality frame timing — frame synchronization, prediction, reprojection and profiling.
Khronos Group: OpenXR 1.1 Specification — standard runtime behavior and unsupported display-rate error.
Unity Android XR OpenXR: Display Utilities — enumerate supported rates and request a reported value.

Sources were opened and checked for the claims linked above. Documentation versions and headset firmware can change; this page does not independently verify device availability, thermal behavior or image quality in a physical test.