A PC bottleneck is whichever part limits your frame rate in a specific game at specific settings, and you can find it in about ten minutes with an overlay. If GPU utilization sits near 95 to 100 percent while frame rate falls short of your target, the graphics card is the limit. If GPU utilization is well below that and one CPU thread is pinned near its ceiling, the processor (or the game engine’s main thread) is the limit. Upgrade what the measurement points at, and ignore online bottleneck calculators that skip this step.
Quick answer: Our top pick in 2026 is the GPU utilization 95 to 100 percent, fps below target — our #1 rated choice. See the full ranked comparison, alternatives and buying advice below.
Why every system has a bottleneck
Each frame requires the CPU to run game logic, physics and draw-call preparation, then the GPU to render the image. Whichever side finishes later sets the frame time. The limit can move: raise the resolution and the GPU takes longer, lower it and the CPU becomes the pacing part. So the question is never “do I have a bottleneck”, it’s “does the limit sit above or below my target frame rate, in the games I play”.
Start by writing down the target, such as 1440p at 144 fps or 4K at 60 fps. Without a target, a bottleneck reading is just a number.
Set up the measurement
- Install an overlay that shows per-thread CPU load, GPU utilization, GPU clock, VRAM use, and frame time. MSI Afterburner with RivaTuner, or the overlay built into your GPU driver software, works. Per-thread data matters because the total CPU percentage hides the real issue (see below).
- Remove frame caps for the test. V-Sync, an fps limiter or a driver cap can hold GPU utilization low on purpose, which looks like a CPU limit when it’s only the cap.
- Choose a repeatable heavy scene. A busy city, crowded battle or the same route each time gives a stable comparison. An empty menu tells you nothing.
- Run for two minutes at your normal settings and resolution, then note average fps, GPU utilization and the highest per-thread CPU load.
Read the numbers
| What you see | Meaning | Where to look next |
|---|---|---|
| GPU utilization 95 to 100 percent, fps below target | GPU-bound | Resolution, graphics settings, upscaling, or a faster graphics card |
| GPU utilization well under 90 percent, one or more CPU threads near 100 percent | CPU-bound | CPU-heavy settings, memory configuration, then processor |
| GPU and CPU both moderate, fps still low, clocks dropping | Throttling from heat or power limits | Cooling, fan curves, power settings |
| GPU high, VRAM at its limit, sudden stutters | VRAM-bound | Texture quality, resolution, a card with more memory |
| Both low, fps capped at a round number (60, 120) | Cap or V-Sync in effect | Disable caps for testing |
| Averages fine, 1% lows poor, frame time spikes | Often CPU, RAM or storage hitching | Check memory speed, background tasks, shader compilation, drive |
One detail catches many people: a 16-thread processor with a single thread at 100 percent shows only about 6 percent total CPU use in the standard task monitor. Many games have a main thread that can’t be split further, so that thread sets the ceiling while the rest of the cores idle. Always look at the per-thread view, not the overall figure.
Also note that GPU “utilization” measures how often the GPU has work queued rather than how fully its shaders are used. Even so, a sustained reading in the high 90s is a reliable sign that the graphics card is the limiting side.
Confirm with the resolution test
The fastest cross-check is to change one variable the CPU doesn’t care about: resolution or render scale. Lower resolution reduces GPU work but leaves CPU work almost the same.
- Drop the resolution (for example 1440p to 1080p) or lower render scale and repeat the same scene.
- If fps rises sharply, you were GPU-bound at the original setting.
- If fps barely moves, the CPU, memory or the game’s own limit is setting the frame rate.
- Raise resolution to check the other direction. If fps barely falls when the pixel count rises, the GPU still has spare capacity and the CPU is the limit.
The reason this works: GPU cost scales with the number of pixels, while CPU cost per frame is mostly independent of resolution.
Upscaling changes the picture
Upscalers such as DLSS, FSR and XeSS render at a lower internal resolution, which cuts GPU work. That can push a GPU-bound game into CPU-bound territory. If turning on upscaling gives a large jump at first but fps stops climbing as you lower the quality mode, you have reached the CPU limit. Past that point, a faster graphics card would not add frames in that game.
Other limits to rule out before buying anything
- Memory configuration: check that XMP or EXPO is enabled, since memory often runs at a slow default speed. Two sticks in dual channel generally outperform one stick of the same capacity in CPU-limited games.
- RAM capacity: 16 GB is workable for many games, but modern titles with background apps can page to disk. If usage is near the cap, hitching follows.
- Thermal and power throttling: a CPU near 95 to 100 degrees Celsius or a GPU with falling clock speeds lowers fps without any “bottleneck” in the usual sense. Dust, a poor cooler mount or a restrictive power limit are common causes.
- PCIe link: a card installed in a slot with fewer lanes than expected can lose performance, most visibly on cards with small VRAM that spill textures over the bus. Check the slot setting in the motherboard manual.
- Storage: traversal stutter and long shader compile pauses often come from drive speed or from shader caching being disabled.
- Engine or title limits: some simulators and older titles depend on one fast thread, and no amount of GPU power changes that.
What to upgrade first
| Finding | Free fixes first | Upgrade if those fail |
|---|---|---|
| GPU-bound at target resolution | Lower shadows, volumetrics and ray tracing; use an upscaler; reduce resolution scale | Graphics card |
| CPU-bound in your main games | Reduce crowd, view distance and physics settings; enable XMP or EXPO; close background apps | Processor and, if required, motherboard and memory. Cache-heavy gaming processors often help most in CPU-limited games |
| VRAM full | Lower texture quality and resolution | A graphics card with more VRAM |
| Throttling | Clean dust, improve airflow, adjust fan curves | Better cooler or case airflow |
| Hitching with fine averages | Check RAM speed and capacity, free storage space, drivers | More or faster RAM, faster drive |
| Different games give different answers | Weigh which game you play most and which one matters | Upgrade for the game that falls furthest below your target |
Why bottleneck calculators mislead
These tools compare a CPU and GPU pair and output a percentage. They have no knowledge of the game, resolution, settings, upscaler or frame rate target, which are the variables that decide where the limit sits. The same pair can be GPU-bound in one title and CPU-bound in another on the same day. A percentage that doesn’t say which game and settings it applies to isn’t actionable. Your own overlay readings are.
Frequently Asked Questions
How do I know if my CPU is bottlenecking my GPU?
Play a demanding scene with caps off. If GPU utilization is clearly below the mid-90s and at least one CPU thread is near 100 percent, the CPU or the game’s main thread is the limit. Confirm by dropping the resolution: if fps barely changes, the CPU is setting the pace.
Is it bad if my GPU utilization is 100 percent?
No. In a graphics-heavy game, full GPU use means your card is doing as much work as it can, which is the normal and desired state. It only matters if fps is below your target, in which case lowering settings or upgrading the card is the path.
Can RAM cause a bottleneck?
Yes, in two ways. Slow or single-channel memory limits CPU-bound games, and too little capacity causes hitching when the system pages data to disk. Enable XMP or EXPO and use dual channel before spending on other parts.
Which should I upgrade first, CPU or GPU?
Upgrade whichever your measurement shows is the limit in the games you play most. In most gaming at 1440p and above the GPU is the first constraint, while at 1080p with a high refresh rate target the CPU more often is.
Does a higher resolution reduce a CPU bottleneck?
It can mask it. Higher resolution lengthens GPU frame time, so the GPU becomes the pacing part and the CPU waits. The CPU limit is still there if you later lower resolution or add a faster graphics card.
Why are my frame rates fine but the game feels stuttery?
Average fps hides frame time spikes. Check 1% lows and the frame time graph, then look at RAM speed and capacity, background processes, storage and shader compilation. Those are the usual sources of hitching with a good average.
Ready to decide? Our #1 pick for 2026 is the GPU utilization 95 to 100 percent, fps below target.
Live price & availability on Amazon.
