Frame rate, 120Hz and why players feel the difference

Frame rate is a time budget

Frames per second is easier to understand as time per frame:

• 30 fps gives you 33.3 milliseconds per frame.
• 60 fps gives you 16.7 milliseconds.
• 120 fps gives you 8.3 milliseconds.

Everything — gameplay logic, physics, animation, rendering — has to fit inside that window, every single frame. Going from 60 to 120 does not double the work. It halves the time you have to do the same work.

What players actually notice: consistency

A game averaging 58 fps with occasional long frames feels worse than one locked at a steady 30. Players do not perceive averages. They perceive hitches: the single frame that takes 60 milliseconds while everything around it takes 16.

This is frame pacing, and it is the most under-discussed thing in mobile game performance. Before chasing a higher frame rate, make the frame rate you have consistent. Look at your worst frames, not your average.

Where 120Hz genuinely helps

Higher refresh rates reduce the time between a player's input and what they see, and make motion look smoother. That matters most when:

• The game is fast and reactive: shooters, racing, action, rhythm games.
• The player is tracking moving objects with their eyes.
• The game uses a lot of scrolling or camera movement.

Where it is wasted

A turn-based puzzle game, a card game or a slow strategy game gains very little from 120 frames per second, and pays for it. The extra frames cost battery and generate heat, and heat leads to throttling, which leads to exactly the hitches players hate.

Adaptive refresh displays like Apple's ProMotion can lower the rate when little is moving. Let your game take advantage of that rather than forcing maximum frame rate on a static screen.

Thermals decide the real frame rate

A phone that holds 120 fps for two minutes and then throttles to 40 delivers a worse experience than one that holds a steady 60 for an hour. Premium phones increasingly include cooling hardware — Apple describes vapor chambers in its latest models — but no phone escapes physics. Test twenty-minute sessions, not thirty-second benchmarks.

A practical approach

• Target 60 by default on most games, and make it rock solid.
• Offer 120 as an option for fast genres on devices that can sustain it.
• Measure worst-frame times, not averages.
• Test long sessions on real, mid-range hardware.
• Let the frame rate drop when nothing is moving.

Common questions

Is 120 fps better than 60 fps for mobile games?

For fast, reactive games it can feel noticeably better because it lowers input latency and smooths motion. For slow or turn-based games the benefit is small and the cost in battery and heat is real.

What is frame pacing?

How consistent the time between frames is. A game with an occasional very long frame feels stuttery even if its average frame rate is high. Players notice hitches far more than averages.

How many milliseconds is 120 fps?

About 8.3 milliseconds per frame, compared with 16.7 at 60 fps and 33.3 at 30 fps. Going to 120 halves the time available to do the same work.

Why does my game slow down after a few minutes?

Usually thermal throttling. The device heats up and reduces performance to protect itself. Test long sessions on real devices, and avoid running at maximum frame rate when it is not needed.

Keep reading

iPhone 18 Pro for game developers →Making games for iPhone Duo →Unity performance and optimisation →Discuss performance in APGS Community →