Every bottleneck calculator, this one included, is working from averages. Your machine is not an average. If you want the real answer for the games you actually play, you can get it in about five minutes, and it will be more accurate than anything a website can tell you.
Step one: get a utilisation overlay
You need to see GPU utilisation while you play. Any of these will do it:
- The Xbox Game Bar (Windows key + G), which is already installed and needs no setup
- NVIDIA app or AMD Adrenalin, both of which have a built in overlay
- MSI Afterburner with RivaTuner, which gives the most detail and takes the most fiddling
Turn on GPU utilisation, CPU utilisation and frame rate at minimum.
Step two: read the GPU number while you play
Load a game, play normally for a couple of minutes, and watch GPU utilisation.
| GPU utilisation | What it means |
|---|---|
| 95 to 100% | Your graphics card is the limit. This is the healthy state. |
| 60 to 85% | Something else is holding the card back, usually the processor. |
| Bouncing around wildly | Usually a CPU limit in a game with variable load, or asset streaming stutter. |
Sitting at 95 to 100%. Your card is doing everything it can and you are getting your money’s worth. If you want more frames, lower settings, turn on upscaling, or buy a faster card.
Sitting at 60 to 85%. Most often the processor, sometimes memory, sometimes a frame rate cap you forgot about.
Bouncing around wildly. Watch frame times rather than the utilisation figure here — an unstable number usually means uneven processor work, which is the subject of 1% lows vs average FPS.
Step three: the confirmation test
Utilisation alone can mislead, so confirm it. This test takes thirty seconds and is nearly foolproof.
Stand still in a demanding spot in the game and note your frame rate. Now drop the resolution one step, from 1440p to 1080p for example, and note it again.
- Frame rate went up a lot. The graphics card was the limit. Lower resolution means less work for it, so you got more frames.
- Frame rate barely moved. The processor was the limit. You reduced the card’s workload and it changed nothing, because the card was never the thing you were waiting on.
That second result is the clearest possible evidence of a CPU limit, and no calculator can give it to you. The reason the test works at all is explained in why resolution changes the bottleneck answer.
Step four: check the boring explanations first
Before concluding you need new hardware, rule these out. In rough order of how often they turn out to be the culprit:
- A frame rate cap. V-sync, a limiter in the game’s menu, or a cap in the driver control panel. If you are pinned at exactly 60, 120 or 144, this is your answer.
- Memory running at default speed. XMP or EXPO not enabled in the BIOS. Extremely common, easily worth 5 to 15% — see does RAM speed cause bottlenecks.
- The wrong GPU doing the work. On laptops especially, check the game is running on the discrete card and not the integrated one.
- Power and thermal limits. A laptop on battery, a poorly ventilated case, or a Windows power plan set to balanced can all cost double digits.
- Background load. Recording software, browser tabs playing video, an antivirus scan mid-game.
- Resizable BAR switched off, which costs a few percent on cards that support it.
A surprising share of “my CPU is bottlenecking me” posts turn out to be one of the first three.
Step five: decide whether it matters
Here is the part people skip. Suppose you confirm a CPU limit and you are getting 110 frames a second on a 60 Hz monitor. It does not matter. You cannot see the frames you are missing.
A bottleneck only costs you something if it drops you below the frame rate you can actually use, which is set by your monitor’s refresh rate and by how sensitive you are to frame timing. Before spending money, ask what the extra frames would do for you — and if the answer is that they would help, should you upgrade your CPU or your GPU covers which one to replace.
Where a calculator still helps
Testing on your own machine only works for hardware you already own. The bottleneck calculator is useful for the question you cannot test: if I buy this card, will my current processor waste it? That is what this site is for, and it is a genuinely different question from is my current PC balanced. What it can and cannot answer is set out in are bottleneck calculators accurate.
Use the estimate to shortlist. Use the overlay to decide.
FAQs
How do I know if my CPU is bottlenecking my GPU?
Watch GPU usage in an overlay while gaming. At 95 to 100%, the graphics card is your limit. At 60 to 85% with lower frame rates than you expect, something else — most likely the processor — is holding it back. Confirm it by dropping the resolution one step: if frames barely change, the processor is the limit.
Why is my GPU not running at 100%?
The likeliest causes are a frame rate cap you forgot about, memory running at default speed instead of its XMP or EXPO profile, a laptop running the game on integrated graphics, power or thermal limits, and background software. A processor limit is only one possible cause, and rarely the first thing to check.
Is low GPU usage always a problem?
No. If you are hitting a frame cap or your monitor’s refresh rate, low GPU usage is normal — the card has finished its work and is idle. There is nothing to fix.
What GPU usage should I see while gaming?
In an uncapped, GPU limited game, 95 to 100%. Anything consistently below 90% while you are wanting more frames is worth investigating.
Do I need MSI Afterburner to check this?
No. The Xbox Game Bar is already on Windows and shows enough to pass this test. Afterburner gives more detail and frame time graphs if you want to go further.
Is a bottleneck calculator better than testing myself?
Not for hardware you own. Measuring your own machine in your own games always beats an average-based estimate. Calculators are for hardware you cannot test right now.
My GPU is at 100% but I still get stutter. What now?
Stutter at full utilisation is usually about frame consistency or video memory rather than raw speed. Drop textures one step and watch frame times rather than average FPS — see running out of VRAM is not the same as a bottleneck.