Performance for AR/VR Developers
XR performance optimisation keeps an app at the headset's required frame rate, commonly 72 to 120 Hz, since dropped frames cause discomfort. It means measuring with profilers, then reducing draw calls, polygon counts, overdraw and garbage collection, and using techniques like occlusion culling and foveated rendering.
Stage: Performance and Release · Part of the AR/VR Developer roadmap · Last reviewed 19 November 2026
What to learn in Performance
- Profile a build with the Unity Profiler and Frame Debugger to find the bottleneck
- Reduce draw calls through batching, atlases and GPU instancing
- Bake lighting and use light probes instead of many real-time lights
- Avoid per-frame allocations that trigger garbage collection spikes
- Apply foveated rendering and a fixed frame budget for standalone headsets
Performance interview questions
Why is frame rate more critical in VR than on a flat screen?
Low or unstable frame rates add latency between head movement and the image, which conflicts with what the inner ear expects and causes nausea. Headsets target a fixed refresh rate, so you budget about 11 ms per frame at 90 Hz and treat drops as bugs.
What is foveated rendering?
Foveated rendering draws the centre of the view at full resolution and the periphery at lower resolution, since the eye sees detail only in a small central area. Fixed foveation uses the lens centre, while eye-tracked foveation follows the gaze. It saves GPU work on standalone headsets.
Where Performance fits in the AR/VR Developer roadmap
Performance belongs to the Performance and Release stage (advanced level). Ship it.
Other units in this stage
Back to the full AR/VR Developer roadmap