Fixed foveated rendering (FFR)
Updated: Apr 8, 2026
Meta Quest devices support fixed foveated rendering (FFR). FFR renders the edges of an application-generated frame at a lower resolution than the center, reducing fidelity in the viewer’s peripheral vision where it is unlikely to be noticed.
- Improved frame rate in applications with GPU fill bottlenecks — up to 25% in pixel-intensive apps
- Reduced power consumption — lower heat and longer battery life
- Higher eye texture resolution — increase sharpness in the center while maintaining performance
Quest headsets use tiled rendering, where a frame is split into dozens of tiles of clustered pixels. FFR controls the resolution of individual render tiles — tiles closer to the edges of the eye buffer are rendered at lower resolution than those near the center.
The VR lenses already blur the edges of the field of view, so even though many pixels are rendered there in the standard pipeline, the sharpness is lost. FFR reclaims these wasted GPU resources.
FFR has multiple levels that trade image quality for performance:
- Low — Subtle reduction at the edges, minimal visual impact
- Medium — Moderate reduction, good balance of quality and performance
- High — Aggressive reduction, best performance gains but more noticeable at the edges
FFR does not rely on eye tracking — the high-resolution center (fovea) is fixed in the middle of the frame. Quest Pro and Quest 3 support eye-tracked foveated rendering as a separate feature that dynamically places the high-resolution area where the user is looking.
- FFR may not improve performance in applications with simple shaders — the fixed overhead of FFR can exceed the rendering savings
- Applications using FFR should place high-contrast items like text in the center of the frame
- Apps that encourage players to look at the screen edges (for example, by placing UI on the avatar’s belt) will make the reduced quality noticeable
Engine-specific implementation