Frame Time to FPS Calculator: Convert Frame Time to FPS

If you know how long a frame takes to render, you can calculate the equivalent FPS in seconds. The formula is simple:

FPS = 1000 ÷ Frame Time (ms)

For example, a frame time of 16.67 ms corresponds to approximately 60 FPS, while 8.33 ms corresponds to approximately 120 FPS.

This conversion is useful when analyzing gaming performance, reading frame-time graphs, comparing refresh-rate targets, or troubleshooting stuttering. It also explains why a small change in milliseconds can represent a surprisingly large change in FPS at lower frame rates.

Frame Time to FPS Calculator

Use this formula to convert any frame time measured in milliseconds into FPS:

FPS = 1000 ÷ frame time in milliseconds

Quick examples

These values come directly from the reciprocal relationship between frame rate and frame time. One second contains 1,000 milliseconds, so dividing 1,000 by the time required for one frame gives the number of frames that could theoretically be produced per second.

What Is Frame Time?

Frame time is the amount of time required to produce or render one frame. It is normally expressed in milliseconds, abbreviated as ms.

FPS, or frames per second, describes the rate from the opposite direction. If a game produces 60 frames every second, the theoretical time between evenly spaced frames is about 16.67 milliseconds.

That gives us two inverse formulas:

Frame Time (ms) = 1000 ÷ FPS

FPS = 1000 ÷ Frame Time (ms)

Unity also describes frame time as the number of milliseconds available for each frame, with 30 FPS corresponding to roughly 33.3 ms and 60 FPS corresponding to roughly 16.7 ms.

How to Convert Frame Time to FPS

Converting frame time to FPS only takes three steps.

Step 1: Find the frame time

Suppose a performance overlay or benchmark reports:

Frame time = 8 ms

Step 2: Divide 1,000 by the frame time

1,000 ÷ 8 = 125

Step 3: Add the FPS unit

8 ms = 125 FPS

So a consistent 8-millisecond frame time corresponds to approximately 125 FPS.

Another example: 12.5 ms

If each frame takes 12.5 milliseconds:

FPS = 1000 ÷ 12.5

FPS = 80

Therefore:

12.5 ms = 80 FPS

Why Is 1,000 Used in the Formula?

The number 1,000 comes from the relationship between seconds and milliseconds.

1 second = 1,000 milliseconds

FPS tells you how many frames occur in one second. If one frame takes a particular number of milliseconds, you can determine how many of those frame intervals fit into 1,000 milliseconds.

For example, with a 20 ms frame time:

1000 ÷ 20 = 50

So the theoretical rate is 50 FPS.

This is simply a unit conversion combined with the definition of frames per second.

FPS to Frame Time: The Reverse Calculation

You can reverse the calculation just as easily.

If you know the FPS and want to find the frame time:

Frame Time = 1000 ÷ FPS

For example, at 144 FPS:

1000 ÷ 144 = 6.944… ms

So:

144 FPS ≈ 6.94 ms per frame

At 240 FPS:

1000 ÷ 240 = 4.167 ms

Therefore:

240 FPS ≈ 4.17 ms per frame

This reciprocal relationship is why increasing FPS requires progressively smaller frame times.

Common FPS and Frame-Time Values

The following table is useful when interpreting gaming benchmarks, performance overlays, and monitor refresh rates.

The commonly referenced values of 60 FPS at approximately 16.67 ms, 120 FPS at approximately 8.33 ms, 144 FPS at approximately 6.94 ms, and 240 FPS at approximately 4.17 ms are consistent across current frame-time calculators and technical explanations.

Why Frame Time Matters for Gaming

FPS is usually the number gamers notice first, but frame time provides another way to understand performance.

Imagine two systems both reporting an average of 60 FPS.

One might produce frames at approximately:

16.6 ms, 16.7 ms, 16.6 ms, 16.7 ms, 16.6 ms

The second might produce something like:

5 ms, 8 ms, 12 ms, 50 ms, 8 ms, 17 ms

The average FPS could still look reasonable, but the second sequence contains a large frame-time spike. That spike can appear as a hitch or stutter.

This is why frame-time graphs can reveal problems that an average FPS counter does not. PCWorld and Digital Trends both highlight frame-time consistency as an important part of understanding how smoothly frames are actually delivered.

Lower frame time generally means higher FPS

The relationship is inverse:

Lower frame time → higher potential FPS

Higher frame time → lower potential FPS

For example:

• 4 ms → 250 FPS
• 8 ms → 125 FPS
• 16 ms → 62.5 FPS
• 20 ms → 50 FPS
• 40 ms → 25 FPS

However, this calculation describes the mathematical relationship. Real game performance can be affected by frame pacing, CPU and GPU workloads, synchronization, frame caps, and other factors.

Why 60 FPS Equals 16.67 ms

This is one of the most common frame-time questions.

At 60 FPS, there are 60 frames in one second.

Since one second contains 1,000 milliseconds:

1000 ÷ 60 = 16.6667 ms

Therefore:

60 FPS ≈ 16.67 ms per frame

This is often called the 60 FPS frame-time budget.

It does not mean every frame in a real game will take exactly 16.67 ms. It represents the average interval required for perfectly even 60 FPS delivery.

Why 120 FPS Equals 8.33 ms

The same calculation works at 120 FPS:

1000 ÷ 120 = 8.3333 ms

Therefore:

120 FPS ≈ 8.33 ms per frame

Compared with 60 FPS, the available time for each frame is cut roughly in half.

That is an important performance consideration. A system targeting 120 FPS has much less time to complete the work required for each frame than one targeting 60 FPS.

Why 144 FPS Equals 6.94 ms

For 144 FPS:

1000 ÷ 144 = 6.9444 ms

Therefore:

144 FPS ≈ 6.94 ms per frame

This is useful when interpreting a 144 Hz monitor. A sustained 144 FPS output corresponds to approximately 6.94 milliseconds between frames under even frame pacing.

Why 240 FPS Equals 4.17 ms

At 240 FPS:

1000 ÷ 240 = 4.1667 ms

Therefore:

240 FPS ≈ 4.17 ms per frame

The jump from 120 FPS to 240 FPS sounds large because the FPS number doubles. But the frame-time reduction is only about 4.17 ms per frame.

That is one reason FPS and frame time should be considered together. Equal numerical increases in FPS do not represent equal reductions in frame time.

FPS Gains Are Not Linear

A common misconception is that moving from 30 to 60 FPS and moving from 120 to 150 FPS should have a similar effect because both involve increasing the FPS number.

They do not.

Consider these frame-time values:

The relationship is reciprocal, not linear. Current frame-time references show the same pattern: doubling FPS produces a progressively smaller absolute reduction in milliseconds as the starting FPS becomes higher.

Frame Time vs Refresh Rate

Frame time and monitor refresh rate are related, but they are not the same measurement.

FPS describes how many frames the computer produces.

Frame time describes the time associated with producing or delivering each frame.

Refresh rate, measured in Hz, describes how often the display can refresh.

For example:

• 60 Hz display → one refresh every approximately 16.67 ms
• 120 Hz display → one refresh every approximately 8.33 ms
• 144 Hz display → one refresh every approximately 6.94 ms
• 240 Hz display → one refresh every approximately 4.17 ms

A computer can sometimes render more FPS than the monitor’s refresh rate. Whether those additional frames are visible or useful depends on technologies and settings such as VSync, variable refresh rate, frame caps, and the display pipeline.

Does a Lower Frame Time Always Mean a Better Gaming Experience?

Not necessarily.

Lower frame time means a higher potential frame rate, but smoothness also depends on consistency.

For example, a game consistently delivering frames around 8.3 ms may feel smoother than one averaging 120 FPS while occasionally producing very long frames.

This distinction is particularly important when diagnosing stutter.

A frame-time graph with relatively even values indicates consistent frame delivery. Large spikes indicate that individual frames took considerably longer than neighboring frames.

Digital Trends notes that a game can maintain a respectable average FPS while still suffering from large frame-time spikes that players perceive as stutter.

What Is a Frame-Time Spike?

A frame-time spike occurs when one or more frames take significantly longer to complete than the surrounding frames.

Suppose a game is targeting 60 FPS:

Target frame time = 16.67 ms

If most frames are around 16 to 17 ms but one frame takes 40 ms, that frame is much slower than the target.

The result can be a visible hitch.

Possible causes of frame-time spikes include:

• A sudden increase in scene complexity
• CPU workload spikes
• GPU workload spikes
• Asset or shader compilation
• Background processes
• Driver-related problems
• Memory or VRAM pressure
• Streaming new game assets
• Poor frame pacing
• Certain game-engine workloads

The exact cause depends on the game and system, so the frame-time graph should be treated as evidence of a timing problem rather than proof of one particular cause.

What Are 1% Lows?

1% low FPS is a performance metric designed to expose the slower portion of a benchmark run.

In simplified terms, benchmark software examines the slowest 1% of measured frames and summarizes their performance as a low-end FPS figure. The exact methodology can vary between tools, so benchmark results should be compared using the same measurement method.

The reason this metric is useful is that average FPS can hide short periods of poor frame delivery.

For example, two systems might both average 120 FPS, but one could have substantially worse slow-frame behavior.

RTINGS specifically uses frame-time differences between average FPS and 1% low performance to examine stutters and slowdowns, illustrating why looking at only the headline FPS number can be incomplete.

How to Use Frame Time to Diagnose Stuttering

If a game feels stuttery despite reporting a high FPS, check the frame-time data.

1. Record the average FPS

This tells you the general performance level.

2. Check the frame-time graph

Look for sudden spikes or large variations.

3. Compare the frame time with your target

For a 60 FPS target:

Target = 16.67 ms

For a 120 FPS target:

Target = 8.33 ms

For a 144 FPS target:

Target = 6.94 ms

4. Look at 1% low performance

A large difference between average performance and low-end performance can indicate inconsistent frame delivery.

5. Identify what changes during the spike

Check CPU and GPU utilization, memory usage, temperatures, background applications, and game settings while reproducing the problem.

The important distinction is whether the system has consistently high frame times or occasional frame-time spikes.

Consistently high frame times generally indicate that the system is taking too long to produce frames. Spikes point toward intermittent workload or frame-pacing problems.

Frame Time Budget Explained

A frame-time budget is the amount of time available for each frame if you want to sustain a particular frame rate.

Common targets are:

For example, if you want to sustain 120 FPS, your frame production needs to average about 8.33 ms per frame under even pacing.

This does not mean every part of the computer has exactly 8.33 ms available independently. CPU, GPU, game simulation, rendering, synchronization, and presentation interact within the overall frame pipeline.

Frame Time and CPU vs GPU Performance

Frame time can help identify whether your CPU or GPU is limiting performance, but the conversion itself cannot tell you which component is responsible.

If the GPU needs 12 ms to render a frame, that corresponds mathematically to:

1000 ÷ 12 = 83.33 FPS

If another workload causes the relevant frame interval to rise to 20 ms:

1000 ÷ 20 = 50 FPS

However, real systems have overlapping CPU and GPU work, queues, synchronization, and other pipeline behavior. Therefore, you should use a profiler or performance overlay to determine the actual bottleneck rather than assuming that the frame-time number alone identifies it.

Common Mistakes When Converting Frame Time to FPS

Mistake 1: Dividing frame time by 1,000

For frame time in milliseconds, the correct conversion is:

FPS = 1000 ÷ milliseconds

Not:

milliseconds ÷ 1000

The latter converts milliseconds to seconds, but it does not calculate FPS.

Mistake 2: Forgetting that FPS and frame time are inversely related

Higher FPS means lower frame time.

For example:

60 FPS = 16.67 ms

120 FPS = 8.33 ms

The FPS increases while the frame time decreases.

Mistake 3: Treating average frame time as every frame’s actual time

If a benchmark reports 60 FPS, that does not guarantee that every individual frame took exactly 16.67 ms.

The number can represent an average over a measurement period.

Actual frame times can fluctuate considerably.

Mistake 4: Assuming higher average FPS eliminates stutter

A high average can coexist with occasional long frames.

For diagnosing stutter, look at frame-time consistency as well as average FPS.

Mistake 5: Confusing FPS with monitor refresh rate

FPS is generated by the rendering system.

Hz describes the display’s refresh capability.

They interact, but they measure different things.

Quick Mental Math for Frame Time and FPS

For common gaming targets, memorizing a few values can make performance graphs much easier to read.

60 FPS ≈ 16.67 ms

120 FPS ≈ 8.33 ms

144 FPS ≈ 6.94 ms

165 FPS ≈ 6.06 ms

240 FPS ≈ 4.17 ms

360 FPS ≈ 2.78 ms

If you see a frame-time graph around 10 ms, you can immediately estimate:

1000 ÷ 10 = 100 FPS

If you see 5 ms:

1000 ÷ 5 = 200 FPS

If you see 25 ms:

1000 ÷ 25 = 40 FPS

Frame Time to FPS Formula Cheat Sheet

For frame time measured in milliseconds:

FPS = 1000 ÷ Frame Time

For FPS:

Frame Time = 1000 ÷ FPS

For frame time measured in seconds:

FPS = 1 ÷ Frame Time in seconds

For example:

0.008 seconds per frame

1 ÷ 0.008 = 125 FPS

The same result can be obtained by converting 0.008 seconds to 8 milliseconds and calculating:

1000 ÷ 8 = 125 FPS

Frequently Asked Questions

How do I convert frame time to FPS?

Divide 1,000 by the frame time in milliseconds.

FPS = 1000 ÷ frame time

For example, 10 ms gives:

1000 ÷ 10 = 100 FPS

What is 16.67 ms in FPS?

16.67 milliseconds is approximately 60 FPS.

1000 ÷ 16.67 ≈ 60

What is 8.33 ms in FPS?

8.33 milliseconds is approximately 120 FPS.

1000 ÷ 8.33 ≈ 120

What is 6.94 ms in FPS?

6.94 milliseconds is approximately 144 FPS.

1000 ÷ 6.94 ≈ 144

What is 4.17 ms in FPS?

4.17 milliseconds is approximately 240 FPS.

1000 ÷ 4.17 ≈ 240

What is 20 ms in FPS?

20 milliseconds corresponds to 50 FPS.

1000 ÷ 20 = 50

What is 33.33 ms in FPS?

33.33 milliseconds corresponds to approximately 30 FPS.

1000 ÷ 33.33 ≈ 30

Is 10 ms frame time good?

10 ms corresponds to approximately 100 FPS. Whether that is appropriate depends on your target frame rate, display, game, and desired experience.

For a 60 FPS target, 10 ms provides enough theoretical frame-time capacity for 60 FPS.

For a 144 FPS target, 10 ms is not enough to sustain 144 FPS because 144 FPS requires approximately 6.94 ms per frame.

Is lower frame time better?

Lower frame time means that frames are being produced more quickly, which corresponds to higher FPS. But a low average frame time does not automatically guarantee smooth gameplay. Consistent frame delivery is also important.

Why does my game have high FPS but still stutter?

Average FPS can hide individual frames that take much longer than the surrounding frames. A frame-time graph can reveal these spikes.

For example, a game averaging 100 FPS can still experience noticeable hitches if some frames take substantially longer to render.

Does 144 FPS require a 144 Hz monitor?

A 144 Hz monitor can refresh up to 144 times per second, while FPS describes the number of frames the computer produces. Matching approximately 144 FPS to a 144 Hz display allows the system to produce a frame for each refresh under ideal conditions, but synchronization settings and the display pipeline also matter.

What is the difference between FPS and frame time?

FPS measures how many frames occur per second.

Frame time measures how long each frame takes.

They describe the same underlying rate from opposite directions and are mathematical reciprocals when expressed as average or evenly paced values.

Final Takeaway

Converting frame time to FPS is straightforward:

FPS = 1000 ÷ frame time in milliseconds

So:

• 16.67 ms = 60 FPS
• 8.33 ms = 120 FPS
• 6.94 ms = 144 FPS
• 4.17 ms = 240 FPS
• 2.78 ms = 360 FPS

The bigger lesson is that FPS and frame time should be viewed together. FPS gives you an easy summary of performance, while frame time shows the timing behind that number. If you are troubleshooting stutter, frame-time consistency and spikes can reveal problems that average FPS alone can hide.

For a quick conversion, simply take your measured frame time in milliseconds and divide 1,000 by that number.