CPU vs GPU bottleneck, explained.

What a bottleneck actually is

Every frame in a PC game is a relay race between your CPU and your GPU. The CPU runs first: it figures out what’s where in the scene, what physics applied, what AI decided, and submits a list of drawing instructions (draw calls) to the GPU. Then the GPU takes over: it transforms vertices, shades pixels, applies post-processing, and presents the final image to your monitor. Repeat 60 to 360 times a second.

The slower component sets the frame rate. If the CPU takes 12 ms to prepare a frame and the GPU takes 8 ms to draw it, your frame time is 12 ms (~83 FPS) — the GPU sits idle waiting on the CPU. That’s a CPU bottleneck. Reverse the numbers and you have a GPU bottleneck. When both parts finish in roughly the same time, the build is balanced.

Every build is bottlenecked by something— that’s how rate-limiting steps work. The interesting question is which one, and whether the imbalance is severe enough to spend money on. For the diagnostic walkthrough see how to check your PC bottleneck.

CPU bottleneck — the specifics

When the CPU is the limit, frame rate plateaus and adding GPU power gets you nothing. Three concrete signatures:

• SYMPTOM #1GPU usage in Task Manager / MSI Afterburner stays below 95%, often floating around 60–85%, while CPU usage spikes high or one core is pinned at 100%.
• SYMPTOM #2Lowering graphics settings (textures, shadows, foliage) gives you little to no FPS boost. The GPU was already idle waiting on the CPU.
• SYMPTOM #3Frame time is irregular — frames take, say, 8 ms, 8 ms, 22 ms, 8 ms — even when average FPS looks fine. Stutters track to CPU spikes (background tasks, garbage collection, simulation ticks).

Games and scenarios that lean CPU-bound

• Competitive shooters at 240+ FPS — Valorant, CS2, Apex Legends, Fortnite at low settings. The GPU draws each frame in under 4 ms; the CPU has to keep up at the same cadence.
• Simulation games — Cities: Skylines II, Factorio, Anno 1800, Stellaris. Tens of thousands of independent agents simulated each tick; this work is mostly serial and falls on one or two CPU cores.
• MMOs and battle royale endgames — World of Warcraft raids, Final Fantasy XIV hunt trains, the last circle in PUBG/Warzone. Many networked entities, AI, and physics on screen.
• Strategy games at max zoom-out — Total War battles, Age of Empires IV with population caps raised. Same agent-density problem as simulation games.
• Streaming + gaming on the same machine — OBS x264 encoding hammers cores that the game also wants.

GPU bottleneck — the specifics

When the GPU is the limit, frame rate is gated by pixel work and adding a faster CPU gets you essentially nothing. This is the desiredstate for a balanced gaming build — it means you’re actually using the expensive GPU you paid for.

• SYMPTOM #1GPU usage stays at 95–100% throughout play. CPU floats at 30–70%. This is the textbook signature.
• SYMPTOM #2Lowering graphics settings gives a real FPS boost — the GPU suddenly has less work to do per frame.
• SYMPTOM #3FPS scales smoothly with resolution drops — going from 4K to 1440p roughly doubles your frame rate. (Under a CPU bottleneck, that same change barely moves the needle.)

Games and scenarios that lean GPU-bound

• 4K gaming, period. Pixel count quadruples vs 1080p. Even an RTX 4090 spends most of its budget on shading.
• Ray tracing enabled. Path tracing in Cyberpunk Overdrive mode or Alan Wake 2 makes nearly every build GPU-bound.
• High-poly open worlds at max settings — Red Dead Redemption 2, Hogwarts Legacy, Starfield with the texture mod, Red Dead 2.
• Anti-aliasing dialed up — DLAA / 4× MSAA / native AA at high resolution.

How resolution flips the answer

The same CPU + GPU combination can be CPU-bound at 1080p, balanced at 1440p, and GPU-bound at 4K — without anything else changing. This is the most counter-intuitive thing about bottlenecks, and the reason single-percentage bottleneck calculators are wrong about most builds.

The CPU’s work per frame is mostly independent of resolution — it’s the same physics, AI, and draw calls regardless of pixel count. The GPU’s work scales with pixel count. So as resolution rises, the GPU’s budget per frame grows while the CPU’s stays constant. Eventually the GPU becomes the slower one.

This is why we report the verdict at all three resolutions on every bottleneck pair page — a single number would be lying.

Which is worse — CPU or GPU bottleneck?

A common Reddit question. The honest answer: neither is inherently worse, they just have different fixes.

• GPU bottleneckmeans you’re using your expensive GPU. The fix is either lowering settings (free) or buying a faster GPU (expensive but linear payoff).
• CPU bottleneck means your expensive GPU is sitting idle. The fix is upgrading the CPU — but that often means a new motherboard and RAM too (DDR4 → DDR5, AM4 → AM5, LGA1700 → LGA1851). The pre-requisite cost is higher.

For most builders, “GPU-bound at 1440p” is the goal state. “CPU-bound at 1440p” means the CPU is the next upgrade.

How to fix each one — without a full rebuild

Fixing a CPU bottleneck (cheapest first)

1. Cap your FPS at your monitor’s refresh rate (NVIDIA Control Panel → Max Frame Rate, or RivaTuner). If you’re hitting 200 FPS on a 144 Hz monitor, you’re burning CPU on frames you never see.
2. Raise your resolution or graphics settings. Sounds backwards, but it shifts the budget toward the GPU. Often you can go from CPU-bound at 1080p Low to balanced at 1440p High without losing FPS.
3. Tune RAM speed. Especially relevant for Ryzen — going from DDR4-2400 to DDR4-3600 (or DDR5-4800 to DDR5-6000) can recover 10–20% in CPU-bound games for the cost of a BIOS toggle (XMP/EXPO).
4. Close background apps. Chrome with 50 tabs, Discord, OBS, antivirus, Microsoft Teams — they all steal CPU cycles.
5. Lower CPU-heavy settings. Draw distance, NPC density, simulation tick rate, shadow quality.
6. If nothing else works, upgrade the CPU. Run our calculator first to see whether the gain is worth the cost.

Fixing a GPU bottleneck

1. Lower the most expensive settings. Shadows, ray tracing, screen-space reflections, volumetric fog, and anti- aliasing are the heaviest. Texture quality is usually free if you have enough VRAM.
2. Enable DLSS / FSR / XeSS. Render at lower resolution, AI-upscale to native. Frame-generation features (DLSS 3, FSR 3 FMF) double FPS at the cost of latency.
3. Lower the resolution. Going from 4K to 1440p roughly doubles GPU-bound FPS.
4. Check VRAM usage.If you’re hitting your card’s VRAM limit (e.g. 8 GB on a 3060 Ti), texture quality is the highest-impact setting to drop.

FAQ