Essentials

Quality fallbacks

Updated: Oct 23, 2026
A quality fallback is a reversible change your app makes to reduce the CPU or GPU work that limits the frame.

Plan quality fallbacks

A fallback helps only if it reduces the work that limits the frame. Lowering render resolution reduces GPU pixel work, not CPU work, so it does not help a CPU-bound scene. First determine whether a scene is GPU-bound, CPU-bound, or both. See Profile and debug performance to capture traces on a device.
Keep GPU actions and CPU actions separate, and match each to what you measured. When a scene is both GPU-bound and CPU-bound, use actions from both lists.
GPU actions include:
  • Lowering the fixed render scale, if your app does not use dynamic resolution
  • Raising the foveation level
  • Reducing the cost of shadows, post-processing, particles, shaders, or transparency
Lowering the fixed render scale and raising the foveation level apply where your development environment supports them. See Render scale and Foveated rendering.
CPU actions include:
  • Reducing simulation, animation, or physics detail
  • Deferring background work

Protect core behavior

Whatever your app lowers, it must still:
  • Accept input
  • Show the UI required to continue
  • Preserve task or session progress
Make each fallback reversible. Record each value your app changes, and restore it when measurements show headroom (spare CPU or GPU time) has returned. Do not rely on the runtime to restore changes your app made.