# 120Hz Animation: Designing for High Refresh Rate Screens

> 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.

Updated November 2026. Source: https://www.exodeui.com/learn/high-refresh-rate-animation/

## Key takeaways

- 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

## 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.

## Frequently asked questions

### Why does my animation run faster on a 120Hz screen?

It is probably frame-based. Calculate motion from elapsed time instead.

### Does requestAnimationFrame run at 120fps?

It usually follows the display refresh rate, so it can on 120 Hz screens.

### Do CSS animations support 120Hz?

Browsers can render CSS animations at the display's refresh rate when the work is cheap enough.

### Does 120Hz drain battery?

It uses more power, which is why platforms lower the rate when nothing is moving.

## Related

- [Fix mobile animation stutter](https://www.exodeui.com/learn/fix-mobile-animation-stutter/)
- [Spring animation explained](https://www.exodeui.com/learn/spring-animation/)
- [Battery-friendly animation](https://www.exodeui.com/learn/battery-friendly-animation/)
- [Best web performance animation tools](https://www.exodeui.com/best-web-performance-animation-tools/)
