A bottleneck is when one part of your PC, the CPU or the GPU, cannot keep up with the other, so the faster part sits partly idle and your frame rate is capped below its potential. This calculator estimates which part limits you at the resolution you actually play, using aggregated gaming benchmarks. Pick your processor, your graphics card, and a resolution.
The honest part first: this is a directional estimate, not a benchmark. A real bottleneck depends on the specific game and engine, your settings, your memory speed, your refresh rate, and whether you use upscaling. What the tool is good for is a sanity check before you buy, spotting an obvious mismatch and understanding why the same pair behaves so differently at 1080p versus 4K. Being GPU-bound at 1440p or 4K is not a fault; it is the efficient, intended state.
The processor scores come from the Tom’s Hardware CPU benchmarks hierarchy (1080p gaming) and the graphics-card scores from the Tom’s Hardware GPU benchmarks hierarchy (rasterized gaming), both current through June 2026. The resolution-shifts-the-limiter principle is well established by reviewers and by Intel’s own developer guidance.
Worked examples
These are this calculator’s own outputs, computed with the same formula the tool runs in your browser — so you can see a real answer without touching a single input.
The tool’s own default state and a very common balanced 1440p gaming build: Ryzen 7 7800X3D + GeForce RTX 5070 Ti, playing at 1440p
- Inputs: CPU index (1080p gaming) = 85.6 (Ryzen 7 7800X3D). GPU raster index at 1440p = 69.8 (GeForce RTX 5070 Ti; its row is 76.2 / 69.8 / 61.9 / 16GB). Resolution = 1440p, so RES scale = 0.72. VRAM = 16 GB.
- Result: Headline: ‘GPU-bound (expected at 1440p)’ (neutral/accent colour). Stats row: Limiter = GPU, Imbalance = 41%, GPU VRAM = 16 GB. Bars: CPU - Ryzen 7 7800X3D 86 / 100 (100% wide, dimmed), GPU - GeForce RTX 5070 Ti @ 1440p 50 / 100 (59% wide, highlighted as the limiter). Recommendation text: the GPU sets the frame rate and that is normal at 1440p — the CPU is keeping up with headroom to spare; to gain fps, upgrade the GPU, lower a few settings, or turn on DLSS/FSR.
A classic real upgrade question: an older Alder Lake i5 kept from a 2022 build, paired with a brand-new high-end card, still on a 1080p high-refresh monitor. Core i5-12600K + GeForce RTX 5080 at 1080p
- Inputs: CPU index = 60.8 (Core i5-12600K — the lowest CPU index in the dataset). GPU raster index at 1080p = 81.9 (GeForce RTX 5080; row 81.9 / 76.7 / 69.8 / 16GB). Resolution = 1080p, so RES scale = 1.00. VRAM = 16 GB.
- Result: Headline: ‘Moderate CPU bottleneck’ (amber/warn). Stats row: Limiter = CPU, Imbalance = 26%, GPU VRAM = 16 GB. Bars: CPU - Core i5-12600K 61 / 100 (74% wide, highlighted as the limiter), GPU - GeForce RTX 5080 @ 1080p 82 / 100 (100% wide, dimmed). Recommendation text states roughly 26% of the GPU’s potential goes unused at 1080p, and suggests a faster gaming CPU (X3D chips lead), faster RAM, or moving to a higher resolution/settings. Switching the same pair to 4K flips the verdict to ‘GPU-bound (expected at 4K)’ with Limiter = GPU and Imbalance = 43%.
A mainstream all-new mid-range build checked at 1080p: Ryzen 7 7700X + Radeon RX 9070 — the case where the tool says stop worrying and just upgrade for performance
- Inputs: CPU index = 70.6 (Ryzen 7 7700X). GPU raster index at 1080p = 69.1 (Radeon RX 9070; row 69.1 / 62.1 / 52.1 / 16GB). Resolution = 1080p, so RES scale = 1.00. VRAM = 16 GB.
- Result: Headline: ‘Well balanced’ (green). Stats row: Limiter = GPU, Imbalance = 2%, GPU VRAM = 16 GB. Bars: CPU - Ryzen 7 7700X 71 / 100 (100% wide), GPU - Radeon RX 9070 @ 1080p 69 / 100 (98% wide, marked as the limiter). Recommendation text: well matched at 1080p, neither part holds the other back much, so spend on whichever you upgrade for performance rather than to fix an imbalance. Note the Limiter stat still reads GPU even though the headline is ‘Well balanced’ — the under-8% rule short-circuits the severity wording but not the limiter readout.
How to read the result
The tool gives you a limiter, CPU or GPU, and an imbalance percentage. Read it as a direction and a rough size, not a precise measurement. The processor and graphics-card scores come from two different game suites, so the exact number is an approximation; a result within a few points either way is effectively balanced hardware. What it reliably tells you is which part is likely holding you back at the resolution you chose, and how that flips as the resolution changes. Use it to catch an obvious mismatch before you spend money, then confirm with benchmarks for the specific games you play.
Why resolution decides the limiter
The processor does the same work every frame no matter the resolution: game logic, physics, AI, and setting up draw calls do not care how many pixels the screen has. The graphics card does far more work as resolution climbs, because there are far more pixels to shade. 1440p has roughly 1.78 times the pixels of 1080p, and 4K has four times as many. Raising the resolution loads up the graphics card while the processor’s job stays flat.
That is the whole reason the same CPU-and-GPU pair can be CPU-limited at 1080p and clearly GPU-limited at 4K. It is also why reviewers test processors at 1080p, to expose the gaps between chips, and treat 4K as mostly a graphics-card test. If you play at 4K, a mid-range processor paired with a strong card is usually fine; the same processor can hold that card back at 1080p.
Fixing a CPU bottleneck
If the tool flags your processor as the limiter, there are a few real levers. The most direct is a faster gaming chip, and the ones with extra cache (AMD’s X3D parts) lead in most games because gaming leans hard on cache. Faster memory with its profile enabled (EXPO on AMD, XMP on Intel) helps too, since game performance is sensitive to memory latency. The free option is to raise the resolution or settings, which shifts work onto the graphics card and often hides a mild CPU limit entirely. Before blaming the hardware, rule out the cheap causes: background apps, a stale chipset driver, or a power plan that parks cores can all make a CPU limit look worse than it is.
The mismatches that waste money
Two pairings burn money. The first is a top-tier graphics card behind a weak processor at 1080p: the card spends its life waiting on the CPU and you paid for frames you never see. The second is over-buying the processor for a 4K build, where the graphics card is the limiter anyway and the extra CPU headroom does almost nothing. The goal is not zero bottleneck, which is impossible since one part always leads, but a pair that is balanced for your resolution.
If you are planning a build rather than diagnosing one, the PC Builder picks balanced parts to a budget, and the 7800X3D vs 9800X3D upgrade guide shows how much a cache-heavy gaming chip actually moves the needle. For a worked 1440p example, the $1,500 RTX 5060 Ti build is balanced by design.
Assumptions and sources
- CPU indexes come from the Tom’s Hardware CPU benchmarks hierarchy (1080p gaming) and GPU indexes from the Tom’s Hardware GPU benchmarks hierarchy (rasterized, native resolution), both current through June 2026; parts without consistent figures across the two suites were omitted rather than estimated.
- The resolution scaling applied to the GPU score (1.00 at 1080p, 0.72 at 1440p, 0.50 at 4K) is a TechFuelHQ approximation of how far a top card’s frame rate falls as pixel count rises, stated openly here rather than hidden in the model.
- The under-8% “well balanced” band and the severity wording are TechFuelHQ editorial thresholds - the reason the page tells you to read the percentage as direction and rough magnitude, not measurement.