8.33 ms frame time is approximately equal to 120 FPS. In simple terms, when a game is running at 120 frames per second, there is about 8.33 milliseconds available for each frame.
The basic formula is:
Frame Time (ms) = 1000 ÷ FPS
So:
1000 ÷ 120 = 8.33 ms
This is why you may see 8.33 ms in an FPS counter, performance overlay, benchmark, or frame-time graph when a game is running around 120 FPS. FPS and frame time describe the same performance from two different perspectives: FPS tells you how many frames are produced per second, while frame time tells you how long each frame takes.
Quick answer: 8.33 ms equals how many FPS?
8.33 ms = approximately 120 FPS.
To convert frame time back into FPS:
FPS = 1000 ÷ Frame Time
Therefore:
1000 ÷ 8.33 ≈ 120 FPS
The relationship is inverse. A lower frame time means frames are being produced more quickly, resulting in a higher FPS.
| Frame time | Approximate FPS |
|---|---|
| 33.33 ms | 30 FPS |
| 16.67 ms | 60 FPS |
| 11.11 ms | 90 FPS |
| 8.33 ms | 120 FPS |
| 6.94 ms | 144 FPS |
| 6.06 ms | 165 FPS |
| 4.17 ms | 240 FPS |
| 2.78 ms | 360 FPS |
| 2.08 ms | 480 FPS |
The formula and these common conversions follow the reciprocal relationship between frame rate and frame time.
What does 8.33 ms frame time actually mean?
Imagine a game producing frames one after another.
At 120 FPS, the system produces 120 frames during one second. Since one second contains 1,000 milliseconds, you can divide that time among the 120 frames:
1,000 ms ÷ 120 frames = 8.33 ms per frame
So an 8.33 ms frame time means the average interval between frames is about 8.33 milliseconds.
It does not mean that every part of the computer finishes all of its work in exactly 8.33 ms. A game frame can involve the CPU, GPU, game engine, drivers, operating system, and other components.
For performance analysis, however, the number gives you a useful frame-time budget.
If you want to maintain approximately 120 FPS, your frame production needs to average around 8.33 ms per frame.
NVIDIA’s performance documentation similarly defines frame time in terms of elapsed time between frames and notes that lower frame time corresponds to higher frame rates.
How do you calculate 8.33 ms from FPS?
The calculation is straightforward.
Step 1: Start with the FPS
Suppose your game is running at:
120 FPS
Step 2: Divide 1,000 by the FPS
There are 1,000 milliseconds in one second:
1,000 ÷ 120
Step 3: Calculate
= 8.333… ms
Rounded to two decimal places:
= 8.33 ms
Therefore:
120 FPS ≈ 8.33 ms frame time
You can use the same calculation for practically any frame rate.
For example:
60 FPS
1,000 ÷ 60 = 16.67 ms
144 FPS
1,000 ÷ 144 = 6.94 ms
240 FPS
1,000 ÷ 240 = 4.17 ms
How do you convert 8.33 ms back to FPS?
If you already know the frame time and want to determine the equivalent FPS, reverse the formula:
FPS = 1000 ÷ Frame Time
For 8.33 ms:
FPS = 1000 ÷ 8.33
FPS ≈ 120
Because 8.33 is a rounded value, the result is approximately 120 FPS rather than an exact mathematical representation of 1/120 second.
The exact frame interval for 120 FPS is:
1 ÷ 120 second = 0.008333… second
or:
8.333… milliseconds
Why do gamers care about frame time?
FPS is useful, but it can hide important information about how consistently frames are being delivered.
Consider two games:
Game A
- 120 FPS average
- Frames arrive at roughly 8.33 ms intervals
Game B
- 120 FPS average
- Most frames arrive around 5 to 8 ms, but occasional frames take 20 or 30 ms
Both might report approximately 120 FPS over a measurement period, but Game B can feel less consistent because of those longer frame times.
This is one reason frame-time graphs are useful when diagnosing stuttering.
A high average FPS does not automatically mean perfectly smooth frame delivery. Frame-time consistency matters too.
8.33 ms frame time vs 120 FPS
These terms are closely connected, but they describe different things.
120 FPS answers:
How many frames are produced every second?
8.33 ms frame time answers:
Approximately how much time passes between frames at 120 FPS?
You can think of them as two sides of the same measurement.
| Measurement | What it tells you |
|---|---|
| FPS | Frames produced per second |
| Frame time | Time associated with each frame |
| 120 FPS | About 120 frames every second |
| 8.33 ms | About 8.33 ms per frame at 120 FPS |
FPS is often easier for gamers to understand at a glance, while frame time is particularly useful for developers, benchmarkers, and anyone investigating performance problems.
Is 8.33 ms the same as 120 Hz?
Not exactly, although the numbers are closely related.
A 120 Hz display refreshes its screen 120 times per second. One refresh cycle therefore takes:
1000 ÷ 120 = 8.33 ms
So:
120 Hz refresh interval = 8.33 ms
Likewise:
120 FPS frame interval = 8.33 ms
This is why 120 FPS and 120 Hz are frequently discussed together.
However, FPS and refresh rate are not the same thing.
FPS describes how quickly the computer or console produces frames.
Refresh rate describes how frequently the display can refresh.
For example, a PC could theoretically render a game at 200 FPS while a display is operating at 120 Hz. Conversely, a 240 Hz monitor does not guarantee that a game will actually run at 240 FPS.
What happens if your frame time is higher than 8.33 ms?
If your target is 120 FPS, an average frame time higher than 8.33 ms means you are below the 120 FPS target.
For example:
10 ms
1000 ÷ 10 = 100 FPS
12 ms
1000 ÷ 12 = 83.33 FPS
16.67 ms
1000 ÷ 16.67 ≈ 60 FPS
So even relatively small increases in frame time can reduce your achievable frame rate.
A useful reference is:
| Frame time | Approximate FPS |
|---|---|
| 5 ms | 200 FPS |
| 6 ms | 166.67 FPS |
| 7 ms | 142.86 FPS |
| 8.33 ms | 120 FPS |
| 9 ms | 111.11 FPS |
| 10 ms | 100 FPS |
| 12 ms | 83.33 FPS |
| 14 ms | 71.43 FPS |
| 16.67 ms | 60 FPS |
| 20 ms | 50 FPS |
This also demonstrates why FPS does not increase linearly as frame time decreases.
Why does lowering frame time produce higher FPS?
The relationship is reciprocal.
Suppose a frame takes 20 ms:
1000 ÷ 20 = 50 FPS
Now suppose optimization reduces the frame time to 10 ms:
1000 ÷ 10 = 100 FPS
Cutting frame time in half doubles the FPS.
But going from 8.33 ms to 4.17 ms also cuts frame time in half:
1000 ÷ 8.33 ≈ 120 FPS
1000 ÷ 4.17 ≈ 240 FPS
This illustrates an important point: moving from 120 FPS to 240 FPS requires reducing the frame-time budget from about 8.33 ms to about 4.17 ms.
8.33 ms frame time does not automatically mean smooth gameplay
A common misconception is that seeing 8.33 ms on a frame-time graph guarantees perfectly smooth 120 FPS gameplay.
It does not.
The important question is whether frame times remain consistent.
For example, imagine these simplified frame times:
8.3, 8.4, 8.2, 8.3, 8.4, 8.3 ms
That represents very consistent frame delivery around 120 FPS.
Now consider:
5, 8, 12, 6, 9, 25 ms
The average could still produce a respectable FPS figure, but the 25 ms frame takes substantially longer than the surrounding frames. That difference can contribute to visible or perceptible stutter.
This is why people sometimes report that a game “feels worse” than its average FPS number suggests.
What is a frame-time spike?
A frame-time spike occurs when one or more frames take significantly longer to complete than surrounding frames.
For example:
8 ms → 8 ms → 8 ms → 25 ms → 8 ms
The 25 ms frame is a large departure from the target.
Possible causes include:
- CPU bottlenecks
- GPU bottlenecks
- Shader compilation
- Asset or texture streaming
- Background applications
- Memory pressure
- Driver behavior
- Game-engine workloads
- Sudden increases in scene complexity
- CPU scheduling or other system activity
The exact cause depends on the game and system.
A frame-time graph can therefore be more informative than looking at average FPS alone when troubleshooting stuttering.
What is the 120 FPS frame-time target?
If you are targeting 120 FPS, the theoretical frame-time budget is:
8.33 ms per frame
That means the system needs to sustain approximately one completed frame every 8.33 ms to maintain 120 FPS.
For a perfectly steady 120 FPS stream:
8.33 ms + 8.33 ms + 8.33 ms + …
However, real-world frame delivery is rarely mathematically perfect. Small variations are normal.
The practical goal is generally not to make every measured frame exactly 8.333333 ms. It is to achieve the desired frame rate with consistent frame delivery.
How much faster is 120 FPS than 60 FPS?
The jump from 60 FPS to 120 FPS doubles the frame rate, but the frame-time difference is especially useful for understanding what actually changed.
At 60 FPS:
1000 ÷ 60 = 16.67 ms
At 120 FPS:
1000 ÷ 120 = 8.33 ms
Difference:
16.67 – 8.33 = 8.34 ms
So each frame at 120 FPS has roughly half the frame interval of 60 FPS.
This is one reason higher frame rates can improve perceived motion smoothness and responsiveness.
Blur Busters gives the same basic 60 FPS and 120 FPS frame-interval relationship, noting approximately 16.7 ms at 60 FPS and 8.3 ms at 120 FPS.
8.33 ms vs 6.94 ms: 120 FPS vs 144 FPS
A common comparison is 120 FPS versus 144 FPS.
At 120 FPS:
1000 ÷ 120 = 8.33 ms
At 144 FPS:
1000 ÷ 144 = 6.94 ms
The difference is:
8.33 – 6.94 = 1.39 ms
So the jump from 120 FPS to 144 FPS reduces the frame interval by only about 1.39 ms.
That does not mean the difference is necessarily irrelevant. It simply puts the difference into perspective.
The improvement from 60 to 120 FPS reduces the frame interval by about 8.33 ms, while the improvement from 120 to 144 FPS reduces it by about 1.39 ms.
| FPS | Frame time |
|---|---|
| 60 | 16.67 ms |
| 120 | 8.33 ms |
| 144 | 6.94 ms |
| 240 | 4.17 ms |
Does a 120 FPS game need a 120 Hz monitor?
Not necessarily, but a 120 Hz display is well matched to a 120 FPS target.
A display operating at 60 Hz cannot show 120 distinct refreshes every second. A 120 Hz display, by contrast, has a refresh interval of approximately 8.33 ms.
Higher FPS can still have benefits on displays with lower refresh rates in some circumstances, particularly regarding frame delivery and latency, but the display’s refresh behavior determines what can actually be shown.
Variable refresh rate technologies can further complicate the relationship because supported displays can adjust their refresh timing to the arriving frames within their operating range.
Is lower frame time always better?
From a pure frame-production perspective, a lower frame time means a higher potential frame rate.
For example:
8.33 ms → about 120 FPS
6.94 ms → about 144 FPS
4.17 ms → about 240 FPS
But chasing a lower number is not automatically the right optimization strategy for every game or system.
You also need to consider:
- Frame-time consistency
- CPU utilization
- GPU utilization
- Display refresh rate
- VRR support
- Game settings
- Resolution
- Input latency
- Power consumption
- Thermals
- Whether the game is actually CPU- or GPU-limited
For example, reducing graphics quality to gain additional FPS may make sense for someone prioritizing high-refresh competitive gameplay, while another player may prefer higher visual quality at a lower but stable frame rate.
What is a good frame time for gaming?
There is no single frame-time number that is universally “good.” It depends on the target frame rate and the type of game.
Common targets include:
- 60 FPS: 16.67 ms
- 90 FPS: 11.11 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
For many gaming scenarios, a stable frame rate with consistent frame times can be more useful than a higher but highly variable average.
How can you reduce an 8.33 ms frame-time problem?
First determine whether the CPU or GPU is responsible for the workload.
If the GPU is the bottleneck
Possible approaches include:
- Lower resolution.
- Reduce demanding graphics settings.
- Reduce ray-tracing settings if enabled.
- Adjust upscaling settings where appropriate.
- Reduce effects that heavily load the GPU.
- Check whether the GPU is thermal throttling.
The objective is to reduce GPU rendering time enough to meet the desired frame-time target.
If the CPU is the bottleneck
Consider:
- Lowering CPU-heavy game settings where available.
- Closing unnecessary background applications.
- Checking CPU temperatures and clock speeds.
- Investigating CPU utilization across individual cores.
- Checking for background processes that periodically consume CPU resources.
- Looking for game-specific optimization issues.
Not every CPU bottleneck can be fixed by lowering graphical settings because some game workloads depend heavily on simulation, AI, physics, or other CPU-side operations.
If the problem is inconsistent frame time
Look for spikes rather than focusing only on the average.
A frame-time graph can help identify whether the problem is:
- Continuous high frame time
- Occasional spikes
- Regular periodic spikes
- A CPU-related limitation
- A GPU-related limitation
- Asset or shader-related stuttering
The shape of the graph can provide useful clues about what is happening.
What does 8.33 ms mean for input latency?
An 8.33 ms frame interval is associated with a 120 FPS frame rate, but it should not be interpreted as total input latency.
Input latency involves multiple stages.
A simplified chain can include:
Input device → game processing → CPU/GPU rendering → frame queue → display scanout → pixel response
The 8.33 ms figure represents the frame interval associated with 120 FPS. It does not mean that pressing a mouse button will always appear on the display exactly 8.33 ms later.
Other factors can add latency.
For example, mouse polling is separate from game frame rate. Blur Busters notes that a 125 Hz mouse polls at 8 ms intervals, while a 1000 Hz mouse polls at 1 ms intervals, illustrating why input polling and frame timing should not be confused.
Is 8.33 ms the same as 8.33 ms MPRT?
No. This distinction is important.
Frame time describes the timing of frame production or frame intervals.
MPRT, or Moving Picture Response Time, describes a display motion-persistence characteristic.
In ideal sample-and-hold display conditions, a 120 Hz refresh cycle corresponds to approximately 8.33 ms, and Blur Busters discusses this relationship in terms of motion persistence.
However, you should not automatically treat every “8.33 ms” measurement as the same physical quantity.
For example:
- 8.33 ms game frame time
- 8.33 ms display refresh interval
- 8.33 ms MPRT
can involve different measurements and concepts even though the numerical value is the same.
This is one of the most common sources of confusion when reading gaming performance articles and monitor specifications.
Does 8.33 ms mean my game is running at exactly 120 FPS?
Not necessarily.
If you see 8.33 ms consistently, the corresponding frame rate is approximately 120 FPS.
But if a performance overlay reports an average of 120 FPS, individual frames can still have different frame times.
For example, the game might produce:
7 ms → 9 ms → 8 ms → 10 ms → 7 ms
The average performance can be around the 120 FPS region even though no individual frame necessarily takes exactly 8.33 ms.
This is why average FPS and frame-time graphs should be interpreted together when analyzing performance.
Common misconceptions about 8.33 ms frame time
“8.33 ms means my GPU renders every frame in exactly 8.33 ms.”
Not necessarily.
It represents the frame interval corresponding to 120 FPS. The actual time spent on individual CPU and GPU tasks can be different.
“120 FPS and 120 Hz are identical.”
No.
FPS describes frame production. Hz describes display refresh rate.
They happen to have the same numerical interval when both are 120, but they measure different parts of the system.
“A higher FPS number always means smoother gameplay.”
Not automatically.
Frame-time consistency matters. Large frame-time spikes can cause stutter even when the average FPS looks high.
“8.33 ms is the total input lag.”
No.
Input latency includes multiple stages and cannot be determined from frame time alone.
“Going from 120 FPS to 240 FPS takes the same amount of improvement as going from 60 FPS to 120 FPS.”
Both are a doubling in FPS, but the frame-time savings are different.
60 → 120 FPS:
16.67 ms → 8.33 ms
Savings: approximately 8.34 ms
120 → 240 FPS:
8.33 ms → 4.17 ms
Savings: approximately 4.16 ms
This demonstrates the diminishing time interval between increasingly high frame rates.
Frequently Asked Questions
What FPS is 8.33 ms?
8.33 ms is approximately 120 FPS.
Use:
FPS = 1000 ÷ 8.33 ≈ 120
Is 8.33 ms good for gaming?
8.33 ms corresponds to approximately 120 FPS, which is a high frame rate. Whether it is appropriate depends on your game, monitor, hardware, and priorities. Consistent frame times are also important.
What is the frame time for 60 FPS?
60 FPS corresponds to approximately 16.67 ms per frame.
What is the frame time for 144 FPS?
144 FPS corresponds to approximately 6.94 ms per frame.
What is the frame time for 240 FPS?
240 FPS corresponds to approximately 4.17 ms per frame.
Is 8.33 ms better than 16.67 ms?
In terms of frame rate, 8.33 ms corresponds to approximately 120 FPS, while 16.67 ms corresponds to approximately 60 FPS. A lower frame time means a higher frame rate, although the best target depends on the particular use case.
Why does my FPS say 120 but frame time is not exactly 8.33 ms?
FPS counters may use averages or different measurement windows. Individual frame times also vary. A reported 120 FPS does not require every frame to take exactly 8.333 ms.
Can I get 8.33 ms frame time at 60 FPS?
Not as a sustained one-to-one frame interval. An 8.33 ms frame interval corresponds to approximately 120 FPS. At 60 FPS, the average frame interval is about 16.67 ms.
What is 8.33 ms at 120 Hz?
At 120 Hz, one refresh cycle takes approximately 8.33 ms.
Does lower frame time reduce input lag?
A higher frame rate can reduce the time between frames, which can contribute to lower latency in a properly configured system. However, total input latency depends on the complete input-to-display pipeline, not frame time alone.
Final takeaway
8.33 ms frame time means approximately 120 FPS.
The calculation is:
Frame Time = 1000 ÷ FPS
and the reverse is:
FPS = 1000 ÷ Frame Time
Therefore:
1000 ÷ 120 = 8.33 ms
Understanding this relationship makes FPS graphs much easier to interpret. If your game is targeting 120 FPS, an average frame-time budget of about 8.33 ms is the mathematical target. But when diagnosing real-world gaming performance, do not look only at the average. Frame-time consistency, CPU/GPU workload, display refresh rate, and latency all matter too.
Once you understand that 8.33 ms = 120 FPS, the rest of the common frame-time values become easy to calculate: 16.67 ms is 60 FPS, 6.94 ms is 144 FPS, and 4.17 ms is 240 FPS.