120Hz Animation: Designing for High Refresh Rate Screens
What high refresh rate screens mean for UI animation: time-based motion, requestAnimationFrame, ProMotion and Android frame rates, and battery trade-offs.
Core Takeaway
Many phones, tablets and monitors now refresh at 90, 120 Hz or more, which makes motion look smoother but halves the time available to draw each frame. Write animation that is time-based, not frame-based, let the platform choose the rate, keep per-frame work small, and do not force high rates for content that does not need them.
Time-based, not frame-based
Code that moves an element a fixed number of pixels per frame runs twice as fast on a 120 Hz screen. Use the timestamp that requestAnimationFrame provides, as MDN explains, and compute positions from elapsed time. Springs and CSS animations already work this way.
A tighter frame budget
At 60 Hz each frame has about 16.7 ms; at 120 Hz, about 8.3 ms, shared with everything else the app does.
- Animate transform and opacity where possible
- Avoid layout and paint work during animations
- Move heavy calculation off the main thread
- Profile on the actual high refresh rate device
Let the platform choose
Apple's documentation on ProMotion explains that iPhone and iPad displays adapt their refresh rate, and that apps can hint preferred frame rates for their animations. Android lets apps express a preferred frame rate as well. In most cases the default behaviour is right: high rates during interaction and fast motion, lower rates when idle.
Battery trade-offs
Higher refresh rates use more power. Do not request 120 Hz for slow, ambient loops where the difference is invisible. Pause animations off screen, and let idle screens drop to a lower rate.
Building this in ExodeUI
ExodeUI, which we make, computes spring motion from time and velocity in its runtime, so motion speed does not change with the display's refresh rate. Profile on the device you target, since the frame budget at 120 Hz is half that at 60 Hz.
Key Principles to Remember
- Base motion on elapsed time, not frame count
- At 120 Hz the frame budget is about 8.3 ms
- Let the platform choose rates; hint only when needed
- Avoid high rates for slow or ambient motion
Frequently Asked Questions
Sources
- Optimizing ProMotion refresh rates for iPhone 13 Pro and iPad Pro — Apple Developer
- Window: requestAnimationFrame() — MDN Web Docs
- Frame rate — Android Developers