The number nobody explains properly
You pick up a friend's phone to look at something and the scrolling feels different. Slicker, somehow. More like paper than glass. You hand it back and your own phone suddenly feels a little sluggish, even though nothing changed. That sensation is real. Refresh rate is the reason.
In plain terms: refresh rate controls how many times per second your screen redraws the image. A 60Hz display redraws 60 times a second. A 120Hz display redraws 120 times. That doubling cuts the time between each new frame from roughly 16.7 milliseconds down to 8.3 milliseconds. The gap sounds trivial. The perceptual difference is not.
The flip-book your brain is reading
Think of your screen as a flip-book. At 60Hz, the pages turn 60 times a second, fast enough that the brain reads it as continuous motion. At 120Hz, the pages turn twice as fast, and now there's less blur between each page, so edges stay sharper during movement and transitions feel less like animation and more like the physical world.
This matters most in three situations: scrolling through text, swiping between apps, and gaming. When you flick through a long article, each frame captures the text at a slightly different position. More frames per second means the text spends less time in any one blurred in-between state. At 60Hz, fast-moving text smears. At 120Hz, individual letters stay readable much further into a fast scroll.
The technical term for that smear is motion blur. It comes from your visual system averaging across frames, doing something similar to what a camera does with a slow shutter speed: blending motion across time. Fewer frames means more blending. More frames means crisper edges.
What people get wrong about this
Here's the part most guides skip: refresh rate and frame rate are not the same thing, and conflating them causes real confusion.
Refresh rate is a hardware property. It's how often the display is capable of showing a new image. Frame rate is a software property, specifically how many new images the phone's processor is actually sending. If an app is only rendering 40 frames per second, a 120Hz screen is mostly just repeating frames. You'll still see some benefit from smoother OS animations, but you won't get the full effect.
This is why gaming on a 120Hz screen is only noticeably better if the game itself runs at or near 120 frames per second. Some games are capped at 30 or 60 fps regardless of your hardware, in which case the high-refresh panel is running in overdrive for zero perceptual gain during gameplay. Zero.
The other thing people get wrong, and this one genuinely annoys me, is assuming 120Hz always looks better than 60Hz for every use case. For static content, reading a long document, watching a standard 24fps film, there is no visible difference at all. The display is just redrawing the same frame repeatedly. A 120Hz panel serving 24fps video is a sports car stuck in first gear.
The battery cost, and why variable rate changes everything
A 120Hz display running at peak will drain a battery noticeably faster than a 60Hz one showing identical content. Early high-refresh phones made this tradeoff bluntly: you got smooth scrolling, you paid for it in screen-on time.
The answer was variable refresh rate (sometimes called LTPO, after the transistor technology that enables it). The display dynamically drops its refresh rate when the content doesn't need it: down to 1Hz on a static lock screen, up to 120Hz the moment you start scrolling. Think of a car that idles low in traffic and only opens up on the highway. The engine isn't working harder than the road demands.
Here's a worked example. Two people, same phone, same day of use: same videos, same messages, same apps. One kept the display fixed at 120Hz because they liked the feel. The other let the adaptive setting manage it. By end of day, the fixed-rate user had meaningfully less battery left, roughly 15 to 20 percent during heavy use. The only difference was how often the display was told to redraw a frame that hadn't changed. That's a costly habit for a benefit you can't even see.
60Hz vs 90Hz vs 120Hz: does the jump get smaller?
It does. Honestly, 90Hz deserves more credit than it gets. The perceptual leap from 60Hz to 90Hz is large. Most people notice it within seconds. The leap from 90Hz to 120Hz is real but smaller, and some people genuinely can't tell the difference in everyday use without a side-by-side comparison.
Above 120Hz, the returns shrink further. Some gaming-focused phones ship 144Hz or even 165Hz panels. At those rates, you're mostly serving competitive gamers who need the lowest possible input latency, where even a few milliseconds of touch-to-display response time matters. For reading email on a commute? You'd never know.
The sweet spot for most people is 120Hz with a solid adaptive rate implementation. Smooth enough that the difference from 60Hz is immediately obvious, and the variable rate keeps it from punishing your battery.
The part that's actually about your nervous system
Here's what makes this genuinely interesting rather than just a spec-sheet argument. The reason higher refresh rates feel better isn't purely visual. It's partly proprioceptive.
When you drag a finger across a screen, your brain simultaneously tracks the position of your finger (through touch and muscle sense) and the position of the object on screen. At 60Hz, there's a small but real lag between where your finger is and where the display catches up. At 120Hz, that lag is halved. Your brain stops noticing a discrepancy between what your finger is doing and what the screen is showing.
The interface stops feeling like a window onto something. It starts feeling like you're directly touching it.
So here's the question worth sitting with: why does a phone feel "premium" the moment you pick it up, before you've checked a single spec? This is why. The number on the sheet is real, it's just that your nervous system figured it out before your brain did, and it's been judging every 60Hz screen you've touched ever since.