Broken. You can count the steps.
FPS Comparison
Side by side
See the difference between frame rates
Each lane moves on its own clock, live on your screen. Not a video — which is exactly why every comparison video you have seen was misleading.
- 15 to 240 FPS
- Pick your own lanes
- Runs live on your display
- Your measured rate included
Your device
60 FPS · Measured
240 FPS
Ultra smooth · 4.17 ms
165 FPS
Very smooth · 6.06 ms
144 FPS
Very smooth · 6.94 ms
120 FPS
Very smooth · 8.33 ms
90 FPS
Smooth · 11.11 ms
60 FPS
Standard · 16.67 ms
30 FPS
Noticeable stutter · 33.33 ms
24 FPS
Choppy · 41.67 ms
15 FPS
Choppy · 66.67 ms
A display cannot show more frames than it refreshes. On a 60 Hz screen the 120 and 240 lanes look alike, and that is the honest result rather than a bug.
Only lanes at or below your refresh rate can look different from each other. If 240 and 120 are identical to you, you have just found your ceiling.
Your lane
Measure your own frame rate
Run this and the green lane switches to your real number instead of a guess.
Your frame rate
0
FPS
Not measured
Press start to begin measuring.
Moving blocks reveal judder. Watch the fastest one.
Average—
1% low—
Frame time—
Dropped0
Estimated refresh rate
— Hz
0%
How to watch it
How do I compare frame rates?
-
1
Watch one lane at a time
Follow a single block across with your eyes, then switch. Trying to take in five lanes at once is how people convince themselves they see nothing.
-
2
Look at the edges
Stepping is clearest at the leading edge of each block, and at the moment it turns around at the end of the track.
-
3
Turn off what you cannot see
On a 60 Hz screen the 120 and 240 lanes are lying to you. Switch them off with the chips and compare what your display can actually show.
Why do FPS comparison videos not work?
Because a video has one frame rate, and it is being played on your display at your refresh rate. A 60 FPS video cannot show you what 144 FPS looks like — the best it can do is make the low side worse by dropping frames.
This page has no recording. Each lane is drawn live and advances one step every 1/n of a second, so what you see is your own hardware on your own screen. The honest catch: if your panel refreshes 60 times a second, the 120 and 240 lanes genuinely cannot look different.
What does each frame rate look like?
Cinema. Works with motion blur and no fast pans.
Watchable, clearly stepped in fast motion.
Where motion stops calling attention to itself.
Motion holds together. Text stays readable while scrolling.
Small, real, mostly for competitive play.
Why do the jumps get smaller?
Because every doubling halves the frame time, and halving something small saves less than halving something big.
This is why 30 to 60 is transformative and 120 to 240 is a refinement. Each step costs about the same and delivers half the improvement of the one before.
| Upgrade | Before | After | Time saved |
|---|---|---|---|
| 30 → 60 | 33.3 ms | 16.7 ms | 16.6 ms |
| 60 → 120 | 16.7 ms | 8.3 ms | 8.4 ms |
| 120 → 240 | 8.3 ms | 4.2 ms | 4.1 ms |
Where do you actually notice it?
- Fast horizontal motion. Panning, scrolling, tracking something across the screen. Low rates fall apart here first.
- Small high-contrast detail. Text and thin lines in motion. At 30 FPS moving text is unreadable.
- Response to input. Higher rates shorten the wait between doing and seeing.
- Not still images. A static screen looks identical at every rate.
Reference
Frame rates at a glance
What each rate costs per frame, and roughly how it reads to the eye.
| Rate | Frame time | How it looks |
|---|---|---|
| 15 FPS | 66.67 ms | Choppy |
| 24 FPS | 41.67 ms | Choppy |
| 30 FPS | 33.33 ms | Noticeable stutter |
| 45 FPS | 22.22 ms | Standard |
| 60 FPS | 16.67 ms | Standard |
| 75 FPS | 13.33 ms | Smooth |
| 90 FPS | 11.11 ms | Smooth |
| 120 FPS | 8.33 ms | Very smooth |
| 144 FPS | 6.94 ms | Very smooth |
| 165 FPS | 6.06 ms | Very smooth |
| 240 FPS | 4.17 ms | Ultra smooth |
FAQ
Common questions
Can I see the difference between 60 and 120 FPS?
Most people can, in motion. Scroll a page on a 120 Hz phone and then a 60 Hz one and it is obvious. In a still image there is nothing to see.
Why do the 120 and 240 lanes look the same?
Your display cannot refresh fast enough to show them differently. That is the honest limit, not a bug.
Is there a limit to what the eye can see?
Not a single hard number. The old "the eye sees 30 FPS" claim is nonsense — people reliably tell 60 from 120, and many tell 120 from 240 in fast motion. Returns diminish, they do not stop.
Is 60 FPS enough for gaming?
For most games, yes. Competitive shooters are where higher rates earn their money.
Why does 30 FPS look worse here than in a film?
Films have motion blur baked into every frame by the camera shutter, which fills the gaps between positions. A sharp block at 30 FPS has none, so you see every step.
Keep going
More tools
Everything here runs in your browser, free, with no sign-up.
See it on your own screen
Pick two rates, watch one block at a time, decide for yourself.
Open the comparison