Moving from 360 Hz to 500 Hz shortens the time between refreshes by 0.78 milliseconds. Whether you see a newer view of an opponent on the next refresh depends on when your PC finishes the frame. Start with the monitor’s timing, then compare it with the busiest moments in your matches.

How much time does a faster refresh save?

Divide 1,000 milliseconds by the refresh rate in hertz. At 360 Hz, a refresh starts about every 2.78 ms. At 500 Hz, the interval falls to 2 ms. Doubling that rate to 1,000 Hz saves another millisecond. The 1,250 Hz QHD prototype shown by TCL CSOT at DTC 2026 takes the interval down to 0.80 ms.

Refresh rateTime between refresh startsTime to screen centre in an ideal scan
360 Hz2.78 ms1.39 ms
500 Hz2.00 ms1.00 ms
1,000 Hz1.00 ms0.50 ms
1,250 Hz0.80 ms0.40 ms

Imagine a display drawing from top to bottom at a constant speed over the whole refresh interval. Halfway through, it reaches a crosshair at screen centre. In this model, 500 Hz reaches the crosshair about 0.39 ms earlier than 360 Hz after scanout starts. Actual scan timing depends on the display mode, including the pause between scans.

From mouse click to visible movement

Before a moving target changes position on screen, the game has to process the update and the GPU has to render it. A completed frame may wait for presentation. The monitor then processes the signal, scans the image and changes its pixels. A panel’s pixel response time describes a colour transition. Measuring how long a click takes to appear requires observing both the input and the resulting change on screen.

At a steady 250 rendered FPS, a new game frame arrives every 4 ms. A fixed 500 Hz screen can refresh twice in that time. The quicker scan can still help show a ready frame sooner, but the game supplies only one new view per 4 ms. If frame generation is active, an output counter may include intermediate images. Use rendered FPS to judge how often the game produces fresh frames.

FSR Frame Generation Stutter: Why High FPS Can Still Feel Choppy

Check what VALORANT or CS2 sustains during a fight

A peak of 500 FPS in an empty corridor tells you little about a fight in smoke. Even a 500 FPS average can hide late frames. For example, alternating 1 ms and 3 ms frames average 2 ms each, yet half of them exceed the 500 Hz refresh interval. Look at how often that happens during the part of the game you want to improve.

  1. Confirm the active refresh rate at your playing resolution. Record the CPU, GPU, game build, frame cap, sync settings and graphics preset. For a test of maximum rendering speed, check whether a cap is limiting the run.
  2. Warm up the game. In VALORANT, repeat a strafe, turn and ability use in the Practice Range. In CS2, replay the same demo segment with a smoke effect and several players in view. Use the same duration for each run.
  3. Record rendered FPS, 1% low FPS and the frame-time trace. VALORANT has FPS and timing displays under Settings > Video > Stats. Use the same capture tool and settings for each comparison. Repeat each condition three times.
  4. Count the frames longer than 2 ms for 500 Hz, or 1 ms for 1,000 Hz, and divide by the total frame count. Inspect where those frames cluster. Repeat at your intended monitor resolution, then check a real match for heavier scenes.

If frames regularly take 3–4 ms in fights, investigate those slow frames before paying for a 1 ms refresh interval. Try lowering render resolution while holding other settings fixed. If the slow frames get shorter, rendering load deserves attention. If they persist, check the cap and investigate the recurring hitch. If frames already arrive evenly within 2 ms, testing a 500 Hz display with your usual settings is a more informative comparison.

VALORANT FPS Drops and Mouse Stuttering: Riot Client and Overlay Checks

FAQ

The 0.78 ms is the difference between refresh intervals. The actual click-to-screen change depends on when the frame is ready, where the changed pixel sits and how the panel responds.

To supply one newly rendered frame per refresh at a steady cadence, the PC needs to finish a frame every millisecond. Lower FPS still works. Check the frame-time trace in busy scenes to see how often the game meets that budget.

It summarises the slower part of a run. To find the proportion above budget, count individual rendered frame intervals over 2 ms. Clusters during fights can matter even if the rest of the session runs smoothly.

Related articles