Frame budget calculator: CPU and GPU time per frame
Enter how long your processor and graphics card each take to prepare a frame, in milliseconds. See your frame rate, which part limits you and how much time you must save to hit your target.
What a frame budget is
Every frame your PC shows must be prepared in a fixed amount of time if you want a steady frame rate. At 60 frames per second that is 16.7 milliseconds, at 144 it is 6.9 milliseconds and at 240 it is just 4.2 milliseconds. Inside that window the processor runs the game logic and prepares draw calls, then the graphics card turns them into pixels. If either part takes longer than the budget, the frame arrives late and your frame rate falls.
Thinking in milliseconds instead of FPS makes bottlenecks easy to see. The frame rate you get is set by whichever part takes longest, so 6.5 milliseconds on the CPU and 9.2 on the GPU gives about 108 frames per second, limited by the graphics card. Saving 1 millisecond on the CPU would change nothing, but saving 1 millisecond on the GPU would raise the frame rate.
Frame time budget for common frame rates
The budget is simply 1000 divided by the target frame rate. A frame must be finished inside this time to hold the target.
| Frame rate | Time per frame | Typical use |
|---|---|---|
| 30 FPS | 33.3 ms | Console style, cinematic |
| 60 FPS | 16.7 ms | Standard smooth gaming |
| 120 FPS | 8.3 ms | High refresh gaming |
| 144 FPS | 6.9 ms | Popular gaming monitors |
| 240 FPS | 4.2 ms | Esports displays |
Where to find your CPU and GPU frame times
Many performance overlays and capture tools report CPU and GPU frame time separately, or show a CPU and GPU busy graph. Engine tools and benchmarking utilities often list the same figures. If you only have a frame rate, you can estimate the limit by lowering the resolution: if the frame rate barely moves, the CPU is the limit, and if it rises sharply, the GPU was holding you back.
Enter the two numbers in the calculator and it shows your frame rate, the time budget for your target and exactly how much time the slower part needs to save. Use the table to see which targets each part can reach on its own. For a wider look at pairing parts, try the CPU and GPU bottleneck checker.
Using the result to improve performance
Once you know which part is limiting, the fix is clearer. A GPU limit responds to lower resolution, upscaling and reduced graphics settings. A CPU limit responds to lower CPU-heavy settings such as crowd density and draw distance, faster memory in some games, and sometimes frame generation, which adds frames without needing more CPU work per frame.
Remember that averages hide stutter. A game can average 100 FPS and still feel rough if a few frames take far longer than the budget. Pair this tool with the 1% low calculator to see how consistent your frame times are, and read our system bottlenecks guide for deeper advice.
How to use the frame budget calculator
- Open a performance overlay that reports CPU and GPU frame time and play a typical scene.
- Type the two milliseconds into the calculator.
- Pick the frame rate your monitor can show.
- Read which part limits you and how many milliseconds it must save.
- Change one setting at a time and measure again.
Common mistakes to avoid
- Adding the two times together. In a pipeline the slower part sets the frame time.
- Using an average from a menu scene. Measure during real gameplay.
- Chasing the faster part. Improving it changes nothing until the slower part improves.
Related tools and guides
Keep going with these: FPS to frame time converter, CPU and GPU bottleneck checker, DLSS and frame generation estimator, monitor and GPU matcher, system bottlenecks guide.
Frequently asked questions
What is frame time?
Frame time is how long one frame takes to produce, in milliseconds. It is 1000 divided by the frame rate, so 60 FPS is 16.7 ms. It shows smoothness better than average FPS because a single slow frame appears as a spike even when the average looks fine.
How do I know if my CPU or GPU limits my FPS?
Compare their frame times: the larger number is the limit. Without those figures, lower the resolution. If the frame rate stays about the same, the CPU is the limit. If it climbs a lot, the graphics card was the limit at the higher resolution.
Do CPU and GPU frame times add together?
Not in a normal pipeline. The processor prepares the next frame while the graphics card draws the current one, so the slower part sets the frame time. Some games or settings can serialise work, which adds the times, but the calculator assumes overlap.
Why is my frame rate lower than the lower frame time suggests?
The slower part limits the frame rate, not the faster one. Fixing the faster part does not help. Spikes, V-Sync, frame caps and memory stalls can also lower the average, so check consistency as well as the headline number. Measure again after each change.
What frame time should I aim for?
Aim for a time at or under the budget for your monitor, such as 6.9 ms for 144 Hz. More important is consistency: steady frame times feel smoother than a higher average with spikes. Watch your slowest frames, not just your average.
Independent site. Not affiliated with or endorsed by NVIDIA, AMD or Intel. Product names are trademarks of their owners.