Hz to FPS: Monitor Refresh Rate vs Game Frame Rate

Matching a Game's Frame Rate to the Panel in Front of You

A monitor advertises 144 Hz. A benchmark overlay reports 118 fps. Those are the same kind of measurement — events counted in one second — yet they describe two different pieces of hardware, which is exactly why people go looking for a conversion. The panel announces how often it can redraw; the graphics card reports how often it finished a frame.

Conversion factor: 1 Hz = 1 FPS, a factor of exactly 1, because a hertz is one event per second and a frame per second is one event per second. A 165 Hz panel is therefore matched by 165 fps, and each of those frames has 1 000 ÷ 165 = 6.061 ms of render budget before it is late.

Two devices, one figure

Refresh rate is a hardware ceiling

The panel redraws on its own schedule, so 300 fps into a 60 Hz screen still leaves 60 images per second reaching your eyes.

Frame rate is an average of work done

An fps figure counts a whole second, so it hides everything inside it. Two systems both reporting 120 fps can feel completely different to play.

Frame time is where stutter lives

Invert the rate for milliseconds per frame. One 33 ms frame inside an otherwise smooth second is felt as a hitch yet barely moves the average.

Reading a Panel Spec Into Frame-Time Numbers

Start from the rate the panel is actually running

Use the mode the desktop is set to, not the number on the box. A 165 Hz screen left on its default profile often runs at 60 Hz, and an overclocked mode may report something untidy like 143.98.

Put that figure beside your measured frame rate

The value crosses over unchanged, giving the frame rate the panel is asking your card for. Compare it with the average and the 1 % low from your capture tool to see how often that target is missed.

Work back from a frame rate you want to hold

Either field takes input and the swap arrows flip the labels, so you can start from a target such as 90 fps and read back the refresh mode that suits it before choosing a panel.

Copy the bare figure into your settings notes

The copy button gives digits with no unit and no spaces, which is what a frame-limiter box or a spreadsheet column of test results wants. Ctrl+C inside the field does the same.

Refresh Rates, Frame-Time Budgets and VRR Windows

The frame-time column is the render budget per frame; the variable-refresh column shows the range a typical panel of that speed advertises. Below the floor of that window the driver applies low framerate compensation, drawing each frame more than once to keep the panel inside its legal range.

Panel refresh	Matching frame rate	Frame-time budget	Typical VRR window	Double-buffered v-sync fallback
60 Hz	60 fps	16.667 ms	48–60 Hz	30 fps
75 Hz	75 fps	13.333 ms	48–75 Hz	37.5 fps
120 Hz	120 fps	8.333 ms	48–120 Hz	60 fps
144 Hz	144 fps	6.944 ms	48–144 Hz	72 fps
165 Hz	165 fps	6.061 ms	48–165 Hz	82.5 fps
240 Hz	240 fps	4.167 ms	48–240 Hz	120 fps

The jump people feel most is the first one: moving from a 16.667 ms budget to 6.944 ms removes 9.72 ms of waiting between images. Going from 144 Hz to 240 Hz saves only another 2.78 ms, which is why the returns flatten so sharply at the top of the range.

Panel spec and benchmark log in one line

Both boxes are live at once, so the advertised refresh mode and the frame rate your capture tool logged sit next to each other rather than in two browser tabs.

Untidy measured rates go in as they are

Reported modes rarely land on round numbers, so 143.98 or 164,83 are both accepted, either decimal mark, with the answer carried to eight decimal places.

Clean digits for a frame-limiter box

Copying returns the number alone, no unit and no thousands spacing, ready to paste into a driver cap, a config file or a column of test results.

Refresh Rate and Frame Rate Questions From PC Builders

If hertz and frames per second are the same number, what is there to convert?

Nothing arithmetically — the factor is 1, since both units count events in one second. What the crossover gives you is a display specification translated into a performance target: a 144 Hz panel is asking for 144 finished frames every second, and the 6.944 ms budget that implies is the number worth writing down.

What happens when the frame rate runs past the panel's refresh rate?

Extra frames are discarded or shown as a torn image, the top of the screen holding an older frame than the bottom. V-sync removes the tear by holding each frame until the next refresh, at the price of latency and, with plain double buffering, a drop to half the refresh rate whenever a frame misses its slot — 60 Hz becomes 30 fps, not 55.

What is my monitor's VRR range and what happens when I fall below it?

Adaptive-sync panels advertise a window, commonly starting near 48 Hz and ending at the maximum mode. Inside it the panel waits for the next frame, so there is no tearing and no fixed deadline. Below the floor the driver switches to low framerate compensation, repeating frames to stay legal: 40 fps drawn twice gives an 80 Hz refresh, 35 fps three times gives 105 Hz. That multiplier changing under load is what feels unsettled near the bottom of the range.

Why do reviewers care more about 1 % lows than the average?

An average counts a whole second and hides its own distribution. The 1 % low is the frame rate of the slowest one per cent of frames, so it exposes the long ones: a system averaging 120 fps with a 1 % low of 50 fps is delivering occasional 20 ms frames against an 8.333 ms budget, and those are the moments you notice.

Is a 240 Hz panel wasted if a game only reaches 80 fps?

Not entirely. A faster panel shortens the wait between a frame being ready and it appearing, so even at 80 fps the image reaches the glass sooner than on a 60 Hz screen, and 80 sits comfortably inside a 48–240 Hz adaptive window. The motion clarity such a panel is bought for still needs frames to fill it, so it is ahead of the graphics card rather than useless.