The short answer
A CPU bottleneck is worse for gaming. At the same average frame rate, a CPU-bound game has lower 1% lows and more stutter, and lowering graphics settings or turning on upscaling does almost nothing to help. You're stuck with it until you change hardware or the game.
A GPU bottleneck is the normal, healthy state. It means the graphics card, usually the most expensive part in the build, is being used fully. Frame delivery is even, and you have a dozen settings that trade image quality for frame rate.
There are exceptions. A GPU bottleneck is a real problem when your frame rate is too low for your monitor and settings are already turned down. A CPU bottleneck stops mattering when you're already above your refresh rate. Both are covered below.
What actually happens in each case
Each frame passes through two stages. The CPU runs the game simulation (input, physics, AI, animation, and the draw calls that tell the GPU what to render). Then the GPU turns those instructions into pixels. They work in parallel on different frames, so your frame rate is set by whichever stage takes longer.
When the GPU is slower, the CPU finishes its frame early and queues it up. There's always work waiting for the graphics card, so it runs at 95–99% usage and frames come out at a steady pace. The workload per frame is also fairly consistent: the same resolution, the same shaders, more or less the same pixel count every frame.
When the CPU is slower, the GPU finishes early and waits. Its usage drops, and the frame rate now depends on how much the simulation has to do on each frame. That varies a lot: an explosion, a crowd turning a corner or a new area streaming in can double the CPU's work for a handful of frames. Each spike becomes a long frame, which you feel as a hitch.
That difference in consistency is the whole story. A GPU-bound game slows down smoothly. A CPU-bound game slows down in jolts.
Why a CPU bottleneck feels worse: 1% lows
The 1% low is the frame rate of the slowest 1% of frames. It's the closest single number to how smooth a game feels, because your eyes notice the hitches, not the average. The table below compares builds with similar average frame rates in AAA games. Some are limited by the CPU, some by the GPU.
| Build | Avg FPS | 1% low | Low ÷ avg | Limited by |
|---|---|---|---|---|
| Ryzen 5 3600 + RTX 4070 Super 1080p, High | 80 | 56 | 70% | CPU 42% |
| Core i5-10400F + RTX 5070 1440p, High | 85 | 61 | 71% | CPU 13% |
| Ryzen 5 3600 + RTX 5070 Ti 1440p, High | 80 | 56 | 70% | CPU 35% |
| Core i5-12400F + RTX 4060 Ti 16GB 1080p, High | 93 | 72 | 78% | GPU 21% |
| Ryzen 5 5600 + RTX 5060 Ti 16GB 1440p, High | 76 | 60 | 78% | GPU 27% |
| Ryzen 7 7800X3D + RTX 5060 Ti 16GB 1440p, High | 77 | 63 | 82% | GPU 56% |
The CPU-bound builds keep only 70–71% of their average in the 1% lows, while the GPU-bound builds keep 78–82%. Look at the first and last rows: the Ryzen 5 3600 build averages more frames than the Ryzen 7 7800X3D build (80 vs 77 FPS), yet its worst moments drop to about 56 FPS while the GPU-bound build holds 63. Higher average, rougher experience. Large-cache X3D processors such as the Ryzen 7 7800X3D hold their lows best of all, which is a big part of why they're the default recommendation for gaming.
The numbers come from the same model as the bottleneck calculator, which estimates 1% lows from whichever part is the limit. Real games vary, but the pattern is consistent in independent benchmarks: CPU-limited scenes are where the stutter lives.
Why settings fix one and not the other
Almost every graphics setting changes how much work the GPU does. Resolution, shadows, anti-aliasing, texture filtering and upscaling all lighten the graphics card's load. Very few settings reduce the CPU's work per frame. Here's the same set of changes applied to a CPU-bound build and a GPU-bound one:
| Setting | Ryzen 5 3600 + RTX 5070 Ti 1080p · CPU-bound | Core i5-12400F + RTX 5060 Ti 16GB 1440p · GPU-bound |
|---|---|---|
| High (baseline) | 80 | 77 |
| Ultra | 77 −4% | 62 −20% |
| Medium | 82 +3% | 101 +32% |
| Low | 85 +6% | 120 +56% |
| DLSS/FSR Quality | 80 ±0% | 103 +34% |
Dropping from High to Low gives the GPU-bound Core i5-12400F build 56% more frames. The CPU-bound Ryzen 5 3600 build gets 6%, and turning on DLSS or FSR changes nothing at all, because the GPU was already waiting. The flip side is useful too: when you're CPU-bound, you can raise graphics quality or resolution almost for free. Going to Ultra costs that build only 4% of its frame rate.
A handful of settings do lean on the CPU: crowd and traffic density, view distance and level of detail, physics quality, and in some engines shadow quality (more objects to draw). Ray tracing also adds CPU work to build its acceleration structures. Those are the ones to turn down first when you're CPU-limited, as covered in our guide on how to fix a CPU bottleneck.
When a GPU bottleneck is the real problem
Being GPU-bound is healthy only if the frame rate is good enough. It becomes the problem when:
- FPS is below what you need even at Medium settings with upscaling on. A Ryzen 5 5600 + RTX 4060 build is GPU-bound in AAA games at 1440p at about 49 FPS. That's a perfectly healthy bottleneck that still needs settings turned down for a smooth experience.
- You're out of VRAM. When textures don't fit in the card's memory, the GPU stalls while data crosses PCIe, and the result looks like a CPU bottleneck: low GPU usage and stutter. Eight-gigabyte cards hit this at 1440p in many 2025–2026 releases. Lowering texture quality is the fix.
- You want ray tracing or 4K and the card doesn't have the muscle. No CPU upgrade will help there.
In those cases the GPU is the right thing to upgrade, and the calculator's upgrade cards will show which models your CPU can keep fed without creating a new CPU bottleneck.
When a CPU bottleneck doesn't matter
A CPU bottleneck is only a problem if it holds you below a frame rate you care about. If you play esports titles on a 144 Hz monitor, being CPU-bound at 300 FPS changes nothing you can see. A Ryzen 5 5600 with an RX 9070 XT is CPU-limited in CS2-style games at 1080p, yet still averages about 275 FPS, which is more than a 240 Hz panel can show.
It also doesn't matter much when you cap the frame rate. Many people run a cap a few frames below their refresh rate to keep G-Sync or FreeSync active and cut input lag. If the CPU can hold that cap in the busiest scenes, it doesn't matter that it couldn't go higher.
The latency twist
There's one way a GPU bottleneck is worse: input latency. When the GPU is pegged at 99%, finished CPU frames wait in a render queue, which adds a few milliseconds between your mouse movement and the screen. Competitive players fix that with NVIDIA Reflex or AMD Anti-Lag 2, or with a frame cap just below what the GPU can sustain. A CPU-bound game has no queue, so its latency is naturally lower, even though its frame pacing is worse.
Which part should you upgrade first?
Work out which part limits you in the games you actually play, at the resolution you actually use, then follow these rules of thumb:
- CPU-bound by 20% or more and below your target FPS: upgrade the CPU first. A faster graphics card would mostly sit idle. Check for a drop-in upgrade on your current socket before buying a new platform.
- GPU-bound and below your target FPS: upgrade the GPU, but make sure the new card won't flip you into a CPU bottleneck. A card that's 60% faster helps little if your CPU tops out 20% above your current frame rate.
- Slightly GPU-bound and happy with your FPS: don't upgrade anything. That's a well-balanced PC.
The calculator does this comparison for you and suggests the smallest upgrade that balances the build. If you're about to change resolution, read how resolution changes the bottleneck first, because a new monitor can move the bottleneck from one part to the other. To measure what your PC is doing right now, see how to check for a bottleneck.
Frequently asked questions
Is it better to be CPU or GPU bottlenecked?
GPU bottlenecked. A GPU-bound game has smoother frame times and better 1% lows, and you can raise FPS with settings or upscaling. A CPU-bound game stutters more in busy scenes, and lowering settings barely helps.
Does a CPU bottleneck cause stutter?
It often does. A CPU-bound game's frame rate depends on how much simulation work each frame needs, which spikes during explosions, crowds and streaming. Those spikes show up as low 1% lows and visible hitches, even when the average FPS looks fine.
Is a GPU bottleneck bad?
Not by itself. A GPU running at 95–99% means you're getting the performance you paid for. It's only a problem if your FPS is too low for your monitor even after lowering settings or enabling DLSS or FSR, or if the card is running out of VRAM.
Does DLSS help a CPU bottleneck?
DLSS and FSR upscaling don't. They render fewer pixels, which lightens the GPU's load, so a CPU-bound game gains nothing and becomes even more CPU-bound. Frame generation is different: it adds generated frames without CPU work, which raises perceived smoothness, with slightly higher input latency.
Can a CPU bottleneck damage my GPU?
No. A bottleneck is a performance mismatch, not a fault. An underused GPU just runs cooler and quieter. Neither part is stressed beyond its design.
How much bottleneck is acceptable?
Under 10% is excellent and 10–20% is fine. A CPU bottleneck between 20% and 35% starts to show in 1% lows, and above 35% a large part of the graphics card is wasted. A GPU bottleneck of any size is fine as long as your FPS meets your target.