FPS to frame time converter

A thousand divided by the frame rate. Sixty frames a second means each one is on screen for 16.67 milliseconds, 144 means 6.94, and 30 means 33.33.

The division is the easy part. What it hides is that the frames you add later are worth much less than the ones you added first.

Because it is smaller, and by an exact amount. Doubling the frame rate always shortens the frame by half of what the previous doubling shortened it: from x to twice x saves 500 divided by x milliseconds, and the next doubling saves 250 divided by x.

So 30 to 60 takes 16.67 milliseconds off the frame, while 60 all the way to 240, four times as many frames, takes off 12.5. The first frames you add are the ones you feel.

For the image itself, no: on a fixed refresh rate the screen changes what it shows every so many milliseconds, and frames drawn in between never reach your eyes.

There are reasons people still do it, mostly to shorten the wait between the input and the frame that carries it, and variable refresh rate changes the picture entirely. That is why this page says how many frames the screen can show rather than how many are wasted.

It is the frame rate of the worst one in every hundred frames, and it is the number that matches a stutter. An average of 144 with a one percent low of 60 means the worst frames take 2.4 times as long as the usual one.

An average alone cannot show that, which is why two setups with the same average can feel completely different.