PCPairs

What a CPU bottleneck means at 1080p, 1440p and 4K

Every frame is produced in two stages. The CPU prepares the frame: game logic, physics, draw calls, the work that does not change with resolution. The GPU then renders it: shading pixels, work that grows with resolution. Whichever stage takes longer sets your frame rate. When it is the CPU, people say the CPU is "bottlenecking" the GPU. The card is waiting; you paid for performance you are not using.

Two things follow from this that the calculator is built around.

Resolution moves the bottleneck

At 1080p a modern card finishes its pixels quickly, so the CPU's fixed cost dominates. At 4K the same card is busy four times longer per frame while the CPU's job is unchanged, so the GPU becomes the limit and the CPU stops mattering as much. This is why the same pairing can read "moderate CPU bottleneck" at 1080p and "balanced" at 4K. Neither reading is wrong; they describe different workloads. If you play competitive titles at 1080p and high refresh, take the 1080p number seriously. If you play at 4K, the CPU column is mostly reassurance.

What the percentage is

The score is the share of the card's potential that is left unused because the CPU cannot feed it. For each resolution we estimate the gaming index a CPU needs to keep a given card busy (needed = a + b × GPU index, constants on the methodology page). A CPU at 80% of that figure shows as a 20% bottleneck. Under 10% we call the pair balanced: the two stages take about the same time and no upgrade on either side would be dramatic. 10–25% is mild — noticeable in CPU-heavy games, invisible in most. Over 40% is severe: a cheaper card would perform the same.

A bottleneck in the other direction (a CPU faster than the card needs) is normal and healthy. We only flag it as "CPU overkill" when the gap is large, because the money might have been better spent on the card.

Which CPU each card class needs

The table below is computed from the model: for representative cards from the top of our database to the bottom, the gaming index the CPU needs at each resolution, and the cheapest CPU in our database that reaches it. Anything faster is fine; anything much slower shows a CPU-side score.

Graphics card1080p — CPU needed1440p — CPU needed4K — CPU needed
RTX 5090Ryzen 7 9800X3D (index 107)Ryzen 7 9800X3D (index 100)Core i5-14600K (index 80)
RX 7900 XTRyzen 9 7900X (index 80)Core i7-12700K (index 74)Core i3-13100F (index 58)
RTX 3090Ryzen 7 5700X3D (index 74)Ryzen 9 5950X (index 68)Core i5-11400F (index 53)
RX 6800Ryzen 9 5950X (index 68)Ryzen 5 8600G (index 62)Core i5-10400F (index 48)
RTX 2080 TiRyzen 5 8600G (index 64)Core i3-12100F (index 58)Ryzen 5 3600 (index 45)
RX 6650 XTCore i3-13100F (index 60)Core i5-11400F (index 54)Ryzen 5 3600 (index 42)
GTX 1650Ryzen 7 3700X (index 51)Ryzen 5 3600 (index 45)Ryzen 5 3600 (index 34)

Read it column by column. Going from 1080p to 4K, the CPU requirement drops by roughly a third for the fastest cards. That is the whole argument for pairing a top card with a mid-range CPU when you play at 4K, and against doing so at 1080p.

Balanced pairs at 1440p

1440p is the most common target for a new build, so here is the band of CPUs that score "balanced" with each card class at that resolution. The low end of the band is the value pick; the high end is where spending more on the CPU stops changing the result.

Graphics cardBalanced fromup to
RTX 5090Ryzen 9 7950X3DRyzen 7 9800X3D
RX 7900 XTRyzen 9 5900XRyzen 7 7800X3D
RTX 3090Ryzen 5 5600XCore i9-13900K
RX 6800Core i5-11400FRyzen 7 7700
RTX 2080 TiRyzen 7 3700XCore i5-14400F
RX 6650 XTCore i5-10400FRyzen 7 8700G
GTX 1650Ryzen 5 3600Core i5-11400F

What the score does not know

The model uses average gaming performance. Simulation and strategy games (Factorio, Stellaris, Microsoft Flight Simulator) lean far harder on the CPU than the average; esports shooters at 240 Hz do too. Memory speed, background software and the specific game engine all move the real number. Treat the score as the starting point for a decision, then check a benchmark of the game you actually play. Run your own pair through the calculator.