Roadtovr iconRoadtovrAug 31, 2026 ~5 min source read

Meta’s Quest 3 Gains Extended Refresh Rates: Up to 207Hz at Full Resolution, 240Hz in Dev Mode

Horizon OS 2.7 adds ‘Extended Refresh Rates’ for Quest 3. The hardware can now drive the panel to 207Hz at full resolution and 240Hz when developer mode and display scaling are used, but software and decoding limits will constrain real-world use.

Share this story

Send the public story page.

Useful takeaways from this story.

The update applies only to Quest 3 (not Quest 3S or Quest 2). Quest 3S is limited to 120Hz by its panel.

Many apps won’t immediately benefit: native titles rarely target these frame rates and Quest’s Application Spacewarp struggles above 120 FPS on Quest 3’s SoC.

PC-streaming apps have made progress (Virtual Desktop added 144 FPS support), but video decoders and streaming pipelines face trouble beyond 144 FPS.

# What changed Meta rolled out Horizon OS 2.7, which adds support for "Extended Refresh Rates" on the Quest 3 headset. At full resolution the headset can now run up to 207Hz. A higher 240Hz mode exists but requires developer mode and display scaling, which reduces the rendered resolution before upscaling to the panel.

# What it means technically The update unlocks the display's capability to present much higher frame rates than were previously available on Quest 3. The 207Hz figure is the maximum at native resolution. Pushing to 240Hz uses display scaling in developer mode, so the image sent to the panel is lower resolution and then upscaled, trading pixel fidelity for frame-rate headroom.

Quest 3S and Quest 2 are unaffected. Quest 3S uses a different panel that is limited to 120Hz.

# Software limits and compatibility

PC-side streaming has made some headway: Virtual Desktop's developer reported adding 144 FPS support for wireless PC VR streaming to Quest 3. However, video decoders and streaming pipelines show trouble beyond 144 FPS, suggesting practical limits for wireless PC streaming at those higher refresh rates.

# What developers must do Developers must explicitly support the extended refresh rates in their apps. Enabling 240Hz requires developer mode and display scaling, so developers who want to reach that mode must design for lower render resolution or provide scalable rendering paths. Expect most standalone titles to remain at 72–120Hz unless developers prioritize ultra-high-frame-rate support.

# What users can expect

  • If you use standalone Quest apps: most titles will not immediately benefit. Few native apps currently target rates above 120Hz. 207Hz at full resolution is available but only when an app renders to match it.
  • To access 240Hz you need developer mode and display scaling, which reduces rendered resolution.

# Market context (as presented by the Road to VR author) The author suggests Meta may be using software updates to showcase Quest 3 hardware capability ahead of competing devices. The update highlights that Quest 3's hardware had unused headroom and that unlocking it could affect consumer comparisons with upcoming headsets that target premium price points.

# Bottom line Horizon OS 2.7 makes high refresh rates technically available on Quest 3, but practical benefits depend on developer adoption, Spacewarp limitations on the SoC, and streaming/decoder constraints. For most users, the change is promising but incremental until more apps and streaming tools explicitly support 144–207+ FPS workflows.

More context around this story.

Loading more related stories...

Keep reading in the app

Open the app view to save this story, compare related coverage, and continue from the same source.

Open in app