What is a PC bottleneck?

Published 2026-09-02 · Updated 2026-09-02 · By the PCPartGuide team

Short answer: A PC bottleneck is the single component that limits your frame rate while the other parts wait on it. In games that is almost always the CPU or the GPU. Being GPU-bound is the normal, healthy state; being CPU-bound means a faster graphics card gains you nothing until you raise the resolution or replace the processor.

The pipeline: three stages, one frame rate

Every frame you see passes through three stages. The CPU prepares the frame: game logic, physics, AI, and the job of telling the graphics card what to draw. The GPU then draws it, which means shading every pixel, lighting, shadows, and post-processing. Finally the display shows it, at most once per refresh.

Each stage has a ceiling, the highest frame rate it could manage on its own. The slowest stage sets the frame rate you actually get, and the other two spend part of every frame waiting. That slowest stage is the bottleneck.

Think of it as a relay: it does not matter how fast the second and third runners are if the first one hands over the baton late. Buying a faster GPU while the CPU is the slow runner changes nothing you can see.

This is how the bottleneck calculator on PCPartGuide models a build. Every part gets a frame-rate ceiling for a chosen game and resolution, the lowest ceiling is the frame rate you see, and the gap between the CPU and GPU ceilings is reported as a percentage. The page on how the estimates are made covers the indexes behind those ceilings.

CPU-bound vs GPU-bound: what the overlay shows

The quickest way to see which side limits you is a performance overlay, either the one built into your GPU driver or any tool that shows GPU usage and per-thread CPU usage in-game.

GPU-bound looks like this: GPU usage sits at 97 to 100 percent, CPU usage is moderate, and the frame rate moves the moment you change resolution or graphics quality. The card is working flat out, which is what you paid for.

CPU-bound looks different: GPU usage bounces well below 95 percent, often between 50 and 85, and the frame rate barely changes when you drop the resolution. Total CPU usage may look low, say 30 or 40 percent on a 12-thread chip, but one or two threads sit pinned near 100, because games hang on a main thread and a low overall number hides a saturated one.

A pinned CPU thread is not a problem in itself; if the frame rate is above your target, that is a busy processor doing its job. The guide on whether 100 percent CPU or GPU usage is bad goes through the readings in more detail.

A one-minute test settles it: drop the resolution scale to 50 percent. If the frame rate jumps, you were GPU-bound. If it barely moves, you were CPU-bound.

Why resolution, refresh target, and the engine decide which side limits

The same PC can be CPU-bound in one situation and GPU-bound in another. Three things decide which.

Resolution is the big one. The CPU does roughly the same work per frame whether you play at 1080p or 4K, because the simulation and the draw calls do not care how many pixels end up on screen. GPU work scales with pixel count, and 4K has four times the pixels of 1080p, so the higher the resolution, the more the load shifts onto the graphics card. This is why a fast card looks CPU-limited at 1080p and well matched at 1440p or 4K; the 1080p vs 1440p vs 4K bottleneck guide shows how the balance moves.

Your frame-rate target matters just as much. Chasing 240 fps on a 1080p esports monitor means the CPU must prepare 240 frames every second, a CPU problem; a story game at 60 fps in 4K is almost entirely a GPU problem. A monitor refresh rate or an in-game frame cap adds a third ceiling, and when the display is the lowest ceiling nothing else is limiting you, which is fine.

The game engine decides the rest. Big open worlds, strategy and simulation games, sandbox titles, and competitive shooters at low settings lean hard on the CPU with objects, AI, and draw calls. Cinematic single-player games at high settings with ray tracing lean on the GPU. Processors with a large cache, such as AMD's X3D chips, pull ahead specifically in the CPU-heavy category, which is why the calculator's CPU index is built on gaming results rather than general benchmarks.

The parts that rarely bottleneck frame rate

Plenty of parts get blamed for low frame rates they cannot cause.

The motherboard does not set your frame rate. As long as it supports the CPU and runs the RAM at its rated speed, a budget board and a flagship board deliver the same fps. What the board decides is features: PCIe generation, M.2 slots, USB, and whether the power delivery can hold a high-end chip at full boost under sustained load. The one exception: cards with an x8 PCIe link can lose a few percent on an older PCIe 3.0 board.

The power supply either delivers enough clean power or it does not, and it adds no frames. An undersized or failing unit shows up as crashes, restarts, or shutdowns under load, not as a lower average frame rate. Size it to the GPU maker's recommendation and forget about it.

Storage affects load times, texture streaming, and hitching in open worlds, not average fps. Moving from a hard drive to any SSD is a large quality-of-life upgrade; moving from SATA to NVMe is barely noticeable in most games, with titles built on DirectStorage as the exception.

Mixing brands is a non-issue. An AMD graphics card with an Intel processor, or an NVIDIA card with a Ryzen chip, talks over PCIe like any other pairing, with no brand penalty. Compatibility means checking the CPU socket, the RAM type (DDR4 or DDR5), PSU wattage and connectors, and physical clearance in the case.

RAM is the one supporting part that does move the needle, because it feeds the CPU. Too little capacity for the game, a single stick instead of a dual-channel pair, or a kit running at its slow default speed all lower the CPU's ceiling, and the calculator adjusts for each of them.

What about integrated graphics?

With integrated graphics, the GPU is the bottleneck in almost every game, and by a wide margin. The newest integrated graphics manage esports titles at 1080p on low settings, and that is about the ceiling. Even a budget dedicated card such as an RX 6600 or an RTX 3050 lifts that ceiling several times over, so a dedicated card is the first purchase for anyone who wants to play anything demanding. Intel chips with an F suffix and most older Ryzen chips have no integrated graphics at all.

Check your build: three worked examples

Three pairs from the site show how the rules play out at different budgets. Each headline verdict comes from a demanding modern game at high settings, and each pair page also breaks the result down by game.

A Ryzen 9 3900X with an RTX 3080 reads as a significant CPU bottleneck at 1080p in the headline game, because a 2019 processor cannot prepare frames as fast as that card draws them. In the per-game table the CPU-leaning shooters and sandbox games are the worst cases. At 1440p the two ceilings sit close together, and at 4K the card takes over.

A Ryzen 5 5600 with an RX 7800 XT shows a CPU bottleneck at 1080p in the headline game, and the CPU-leaning titles run into the processor's ceiling harder still. At 1440p most of that disappears, because the extra pixels give the card more to do. The fixes are the two you would expect: play at 1440p, or drop a Ryzen 7 5700X3D into the same board with that RX 7800 XT and watch the CPU-limited rows thin out.

A Ryzen 7 9800X3D with an RTX 5090 pairs the reference CPU of the calculator's index with the reference GPU, and even here the esports and sandbox titles in the per-game table go CPU-limited at 1080p. Nothing feeds a card that fast at 1080p. At 4K it is heavily GPU-bound, which is what the card is for. A CPU bottleneck on the fastest gaming processor money can buy is not a problem; it is a resolution mismatch.

Run the bottleneck calculator with your own game, resolution, RAM kit, and monitor; it works as a bottleneck detector for a build you have not bought yet. Results under 10 percent count as balanced, 10 to 25 as mild, 25 to 45 as significant, and over 45 as severe, and a GPU-side result is only worth acting on when the frame rate falls short of your target.

Every combination on the site is listed under the CPU and GPU pair pages, and the CPU pages and GPU pages rank each part against every partner. The numbers are estimates derived from published benchmark aggregates, not measurements of your PC.

FAQ

Is a GPU bottleneck bad?

No. It means the graphics card is the part working hardest, which is the normal state for a gaming PC and the one you want. It only becomes a problem when the frame rate falls below your target, and then the fix is lower settings, upscaling, or a faster card.

Can a bottleneck damage my hardware?

No: a bottleneck is a mismatch in speed, not a fault, and the faster part simply waits. Running a CPU or GPU at 100 percent for hours is what those parts are built for, and thermal protection pulls clocks back long before anything is at risk. The only cost is money spent on performance you cannot see.

Does more RAM fix a bottleneck?

Only if RAM is the actual limit. Too little capacity for the game, a single stick, or a kit stuck at its default speed all drag the CPU ceiling down, and fixing those is cheap. Beyond that point, adding capacity or speed does nothing for frame rate. The calculator flags each RAM problem separately.

Is a 10 percent bottleneck worth fixing?

Almost never. Under 10 percent counts as balanced, and even the mild band of 10 to 25 percent is common for a good build at 1080p. Focus on whether you hit your frame-rate target: if you do, the percentage is trivia, and if not, the side that limits tells you what to upgrade.

Will a better motherboard or power supply raise my fps?

No. Neither part sets a frame-rate ceiling. A motherboard matters for compatibility, RAM speed support, connectivity, and keeping a power-hungry CPU at full boost; a power supply matters for stability and headroom. Upgrade them for those reasons, or when a new CPU or GPU needs them, not in search of frames.

References

Check your own build

Pick your CPU, GPU, RAM and resolution to see which part is the limiter and what to upgrade first.

Open the bottleneck calculator