Which Component Limits Your FPS? CPU vs GPU Intensive Games Explained

Quick answer: CPU-intensive games like CS2, Valorant, Cities: Skylines 2, and Microsoft Flight Simulator are usually limited by your processor, which simulates AI, physics, and hundreds of moving entities. GPU-intensive games like Cyberpunk 2077 and Alan Wake 2 are usually limited by your graphics card, which renders dense visuals and ray tracing. The fastest way to check any game: drop your resolution one step. If FPS barely moves, your CPU is the wall. If it jumps, your GPU is.

If you have ever wondered why your PC crushes one game but chokes on another, the answer usually comes down to cpu intensive vs gpu intensive games. Some games ask your processor to do the heavy lifting. Others ask your graphics card to do it. Knowing which kind you play decides where your money should go when you upgrade, which settings actually help, and whether a bottleneck is even worth worrying about. This guide maps popular games to the component that usually limits them, shows you a five-minute test to check any game on your own rig, and explains how resolution, refresh rate, DLSS, and frame generation move the bottleneck around.

 Why Some Games Are CPU-Bound and Others GPU-Bound

Every frame you see on screen passes through two workers, one after the other. The CPU plans the frame. It runs the game logic, moves AI characters, calculates physics, tracks bullets, streams in world data, and then hands the GPU a long list of drawing instructions called draw calls. The GPU then draws the frame: it shades millions of pixels, applies textures, computes lighting and shadows, and handles effects like reflections and ray tracing.

Think of it like a restaurant. The CPU is the kitchen deciding what to cook and sending out orders. The GPU is the team of chefs plating every dish. If the kitchen is slow, the chefs stand around waiting. If the chefs are slow, orders pile up no matter how fast the kitchen plans. Whichever side cannot keep up becomes the bottleneck, and that is the part holding your FPS back.

A game becomes CPU-bound when its planning workload is heavier than its drawing workload. That happens with complex simulations, lots of AI entities, big multiplayer player counts, or very high frame rates that force the CPU to plan hundreds of frames per second. A game becomes GPU-bound when its drawing workload is heavier: high resolutions, dense geometry, heavy textures, and lighting effects like ray tracing.

Takeaway: your bottleneck is not a property of your PC alone. It is a property of your PC *plus* the game *plus* your settings and resolution. Change any of those and the bottleneck can move.

What Your CPU Does During a Frame

Your processor handles everything that is not drawing. In a typical frame, the CPU updates game logic, moves enemies and NPCs, resolves hit detection, runs physics for objects and particles, manages networking in multiplayer, streams assets from storage, and issues draw calls to the GPU. Some of this work scales with core count, but a surprising amount still depends on single-core speed, because game logic is a chain of dependent steps that cannot easily be split across cores.

One detail that trips people up: the CPU does a fixed-ish amount of planning work per frame no matter what resolution you play at. Planning 200 frames per second at 720p costs the CPU roughly the same effort as planning 200 frames per second at 4K. That is why CPU bottlenecks show up most at low resolutions and high refresh rates, where the GPU finishes frames so fast that the CPU cannot feed it any quicker.

What Your GPU Does During a Frame

Your graphics card takes the draw calls and turns them into pixels. Its workload scales directly with resolution and visual settings: more pixels, sharper textures, longer shadow distances, denser fog, and especially ray tracing all mean more shading work per frame. Unlike the CPU, the GPU is massively parallel, so it loves big, uniform workloads.

Ray tracing deserves special mention because it flips many games from balanced to heavily GPU-bound. Instead of faking lighting with precomputed tricks, ray tracing traces actual light paths through the scene. Path tracing, used in games like Cyberpunk 2077’s RT Overdrive mode and Alan Wake 2, takes this further and can cut frame rates dramatically on anything but strong GPUs. When you flip ray tracing on, you are almost always handing the bottleneck to your GPU.

Games That Are Usually CPU-Bound

A CPU-bound game is a “too much happening” problem, not a “too pretty” problem. Look for games that simulate living worlds, track hundreds of entities, or need to spit out enormous frame rates for competitive play. Here are the main categories, with real examples.

Competitive Esports Shooters CS2, Valorant, and Apex Legends

Competitive shooters are the classic CPU-bound case. CS2, Valorant, and Apex Legends are deliberately built to run fast on modest GPUs. Pro and serious players run them at low settings on 1080p with 240 Hz or 360 Hz monitors, chasing 300-plus FPS for the lowest input latency. At those settings the GPU finishes each frame in a blink, so the limit becomes how fast the CPU can plan the next frame.

CS2 leans on the CPU for its sub-tick networking model, physics, and dense player interactions, and our dedicated breakdown of whether CS2 is CPU or GPU bound walks through the exact settings that shift its load. Valorant is similar: Riot designed it to run on mid-range PCs, and single-core CPU speed matters far more than GPU muscle for high frame rates, as our Valorant CPU vs GPU guide explains in detail.

The practical lesson: if esports titles are your main games, money spent on a faster CPU (and fast RAM) beats money spent on a bigger GPU almost every time. A mid-range card paired with a strong gaming CPU is the classic competitive formula.

Simulators and City Builders: Flight Sim and Cities: Skylines 2

Simulation games are the heaviest CPU workloads in all of gaming. Microsoft Flight Simulator streams real-world terrain, weather systems, air traffic, and flight physics at the same time. Cities: Skylines 2 simulates traffic, economy, services, and tens of thousands of individual citizens living their lives. These are planning workloads, and no GPU setting can relieve them.

Our Microsoft Flight Simulator CPU bottleneck guide covers why even monster GPUs sit half-idle in that game when the CPU cannot keep up with the simulation. The same story plays out in city builders: our Cities: Skylines 2 CPU bottleneck guide shows how a big, mature city turns even a strong CPU into the limit, and which simulation settings actually ease the pressure.

Takeaway: for sims and builders, prioritize a CPU with strong single-core performance and plenty of cache. This is the genre where a CPU upgrade genuinely transforms the experience.

Strategy and 4X Games: Total War, Civilization, and Stellaris

Strategy games look simple next to a ray-traced shooter, but under the hood they are some of the most CPU-intensive games ever made. A late-game Total War battle has thousands of units pathfinding, colliding, and fighting at once. A late-game Civilization VI or Stellaris turn asks the CPU to resolve the decisions of dozens of AI factions across a huge map. Turn times and late-game stutter in these games are almost always CPU limits.

These games also expose a truth about core counts: many strategy engines still lean on a few fast cores for their main simulation thread, so clock speed and cache often beat raw core count. If your favorite games are grand strategy, a CPU with excellent single-thread performance will do more for you than extra cores you will never fully use.

Games That Are Usually GPU-Bound

A GPU-bound game is a “too pretty” problem. The visuals are dense, the resolution is high, and effects like ray tracing multiply the shading work. These are the games where a GPU upgrade gives you the biggest, most immediate FPS gain.

AAA Open Worlds With Ray Tracing: Cyberpunk 2077 and Alan Wake 2

Cyberpunk 2077 with path tracing enabled and Alan Wake 2 with its heavy ray-traced lighting are the textbook GPU-bound games of this generation. Night City at 1440p with full ray tracing asks the GPU to trace light through one of the densest game worlds ever built. Alan Wake 2 layers volumetric fog, complex materials, and ray-traced reflections on top of that. In both games, reviewers consistently find that even flagship CPUs barely matter once the GPU is maxed: drop the resolution or turn off ray tracing and FPS climbs immediately, which is the signature of a GPU limit.

The lesson is straightforward. If cinematic single-player games at high settings are your thing, put the biggest share of your budget into the GPU, and treat ray tracing as a luxury tax you pay in frames.

Dense Open Worlds That Stress Both Sides: Starfield

Some games refuse to pick a side. Starfield pairs a dense, object-heavy world with a CPU-hungry simulation layer: settlements, ship systems, NPC schedules, and physics objects everywhere. On many PCs it lands in an awkward middle where neither component is clearly the wall, and performance varies wildly by location. Our Starfield CPU bottleneck and best settings guide breaks down which settings relieve the CPU side (crowd density, shadows) and which relieve the GPU side, because in a game like this you have to tune both.

Takeaway: when a game stresses both sides, upgrade the weaker of your two components and tune settings per side instead of blindly lowering everything.

Battle Royale Shooters: Fortnite, Warzone, MW4, and Battlefield 6

Battle royales sit in the middle and swing either way depending on how you play them. Fortnite and Warzone at competitive settings (1080p, low details, high refresh) behave like esports titles: the CPU plans 100-plus players, vehicles, and constant action, and it becomes the limit. The same games at 1440p or 4K with maxed settings flip to GPU-bound, because the visual load grows faster than the simulation load.

This category is especially relevant right now. Call of Duty: MW4 opens campaign early access this week ahead of its full launch on October 23, and our MW4 PC requirements breakdown covers what the game actually demands. Battlefield 6 is the other big name in this space: large-scale multiplayer with destructible environments is exactly the kind of workload that punishes weak CPUs in busy scenes. Check our Battlefield 6 PC requirements guide before you decide which side of your rig needs help.

Takeaway: for battle royales, your settings decide your bottleneck. Competitive settings make it a CPU game; cinematic settings make it a GPU game.

Game by Game Bottleneck Map

Use this table as a starting point, then verify with the five-minute test below. Every PC is different, and settings can flip a game from one column to the other.

Game	Usually limited by	Why
CS2	CPU	High frame rates, sub-tick networking, physics; GPU finishes frames fast at competitive settings
Valorant	CPU	Lightweight visuals, single-core speed drives high FPS targets
Apex Legends	CPU	Fast-paced 60-player matches at high refresh rates
Microsoft Flight Simulator	CPU	Terrain streaming, weather, flight physics, air traffic simulation
Cities: Skylines 2	CPU	Traffic, economy, and citizen simulation scale with city size
Total War: Warhammer III	CPU	Thousands of units with AI, pathfinding, and collision in big battles
Civilization VI	CPU	Late-game AI turn resolution across a huge map
Stellaris	CPU	Grand-scale simulation of factions, economies, and fleets
Minecraft (heavily modded)	CPU	Chunk generation, mod logic, and simulation tick on few threads
Fortnite	Mixed, settings-dependent	CPU-bound at competitive settings, GPU-bound at high resolution and max details
Warzone	Mixed, settings-dependent	Large player counts stress the CPU; high settings stress the GPU
MW4	Mixed, settings-dependent	Same engine family as Warzone; bottleneck follows your settings and resolution
Battlefield 6	Mixed, scene-dependent	Busy multiplayer scenes lean CPU; cinematic visuals lean GPU
Starfield	Both	Dense objects plus heavy simulation; tune CPU and GPU settings separately
Cyberpunk 2077	GPU	Dense world plus ray/path tracing; resolution scaling moves FPS directly
Alan Wake 2	GPU	Heavy ray-traced lighting and volumetrics crush all but strong GPUs
Hogwarts Legacy	GPU	Detailed open world with heavy lighting and effects at high settings
Red Dead Redemption 2	GPU	Lush visuals and long draw distances at high settings

How to Test Whether Your Game Is CPU- or GPU-Bound

Tables and categories are useful, but your specific PC, settings, and resolution decide your real bottleneck. These two tests take about five minutes and work in any game. For a deeper walkthrough with monitoring tools, our guide on how to find a PC bottleneck covers the full process step by step.

Test 1: The Resolution Drop Test

This is the single most reliable home test, and it needs no extra software.

1. Load into a busy, repeatable scene in your game (a crowded city, a big battle, not a menu).
2. Note your average FPS at your normal resolution, for example 1440p.
3. Drop the resolution one big step, for example from 1440p to 1080p. Change nothing else.
4. Play the same scene and note your FPS again.
5. Read the result: if your FPS jumps a lot, your GPU was the limit, because giving it less pixel work sped everything up. If your FPS barely moves, your CPU was the limit, because the CPU does the same planning work per frame regardless of resolution.

One caution: make sure your FPS is not capped by V-Sync, an in-game frame limiter, or your monitor’s refresh rate before you draw conclusions. A capped 144 FPS at both resolutions tells you nothing.

Test 2: The Settings Test and Overlay Reading

The second test confirms what the first one suggests.

1. Turn on an overlay that shows GPU utilization and per-core CPU utilization while you play. MSI Afterburner with RivaTuner, the NVIDIA or AMD driver overlay, or even the Xbox Game Bar (Win+G) all work.
2. Play a demanding scene and watch the numbers.
3. If your GPU sits at 95 to 100 percent, it is the limit. That is healthy, by the way: a maxed-out GPU just means you are getting everything you paid for.
4. If your GPU hovers at 50 to 70 percent while your FPS refuses to climb, something upstream is starving it, and that something is almost always the CPU. Check per-core CPU usage too: one maxed-out core can bottleneck you even when total CPU usage looks low, because many games still do their heaviest logic on one or two threads.
5. As a cross-check, drop the heavy GPU settings (shadows, reflections, ray tracing, volumetrics). If FPS climbs, you are GPU-bound. If it barely moves, you are CPU-bound.

Watch frame times, not just average FPS. A game can report 120 FPS and still feel awful if frames arrive unevenly. Spiky, inconsistent frame times in busy scenes are a classic CPU signature.

How Resolution Refresh Rate and DLSS Affect Bottlenecks 

Your bottleneck is not fixed. These four factors move it, sometimes dramatically, and understanding them saves you from upgrading the wrong part.

Resolution and Refresh Rate

Resolution is a GPU dial. Every step up (1080p to 1440p to 4K) multiplies the pixels your GPU must shade, so higher resolutions push the bottleneck toward the GPU. Refresh rate is a CPU dial: asking for 240 FPS means the CPU must plan 240 frames every second, so high refresh targets push the bottleneck toward the CPU. That is why 1080p at 240 Hz is the most CPU-demanding common setup, while 4K at 60 Hz is the most GPU-demanding.

This is also why “is my PC bottlenecked?” has no single answer. The same PC can be CPU-bound in CS2 at 1080p 360 Hz and GPU-bound in Cyberpunk at 4K 60 Hz on the same afternoon.

DLSS, FSR, and Upscaling

Upscaling technologies like NVIDIA DLSS and AMD FSR render the game at a lower internal resolution and then reconstruct a sharp final image. Because the GPU does less shading work, upscaling relieves GPU-bound situations and can shift the bottleneck back toward the CPU. This is a well-documented effect: turn on DLSS Performance mode in a GPU-bound game and your FPS climbs until the CPU becomes the new ceiling.

There is a practical consequence. If you play mostly with DLSS or FSR enabled at aggressive settings, your CPU matters more than the raw GPU specs suggest. NVIDIA’s own DLSS technology page explains how the reconstruction pipeline reduces render load, which is exactly why pairing upscaling with a weak CPU often disappoints: the GPU gets faster, but the CPU cannot feed it any quicker.

Frame Generation

Frame generation (DLSS Frame Generation, FSR Frame Generation, and similar tech) inserts AI-generated frames between real rendered frames. It raises the FPS number on screen, but it does not reduce the CPU’s per-frame planning work, and it adds a small amount of latency. In a CPU-bound game, frame generation can make the counter look better while the game still feels unresponsive, because the underlying simulation still runs at the CPU-limited rate.

Rule of thumb: use upscaling to relieve a GPU bottleneck, and use frame generation as a smoothness extra on top of a healthy base frame rate, not as a fix for a CPU bottleneck. If your base FPS is CPU-limited at 60, generated frames will not make the game feel like 120.

Which Side Should You Upgrade? Advice by Category

Stop asking “should I upgrade my CPU or GPU?” in the abstract. Ask it per game category, because the answer changes.

If you mainly play competitive esports (CS2, Valorant, Apex): upgrade the CPU first. Look for strong single-core performance and large cache; this is the genre where modern X3D-style chips earn their reputation. Your GPU just needs to be good enough to not cap your target frame rate at low settings.

If you mainly play simulators, city builders, or strategy: upgrade the CPU first, same as above, but value core count a bit more for the heaviest sims. Fast storage (an NVMe SSD) also helps these games stream world data without hitches.

If you mainly play cinematic AAA games at 1440p or 4K: upgrade the GPU first. This is where every dollar shows up directly in frame rates. Do not overspend on a flagship CPU here; a solid mid-range or upper mid-range CPU is plenty once the GPU is the limit.

If you play battle royales or a mix of everything: run the resolution drop test in your two or three most-played games, then upgrade whichever side the test points to. Mixed players benefit most from a balanced build, and our good bottleneck percentage guide explains what “balanced” actually means in practice instead of chasing a magic number.

General buying advice: compare real specs before you buy. TechPowerUp’s GPU database is the most detailed public spec reference for graphics cards, and reviews at Tom’s Hardware regularly test how CPUs and GPUs scale across real games. Never buy based on a bottleneck calculator percentage alone; those tools estimate, they do not measure your games.

Common Mistakes to Avoid

• Upgrading the GPU for a CPU-bound game. This is the most expensive mistake on this list. If your CPU is the wall in CS2, a bigger GPU changes nothing.
• Judging by total CPU usage instead of per-core usage. A CPU at 40 percent total can still be bottlenecked if one core is pinned at 100 percent running the game’s main thread.
• Testing in menus or empty areas. Bottlenecks show up in busy scenes. Always test where the game is actually demanding.
• Forgetting about RAM and storage. Stutter that looks like a CPU problem is sometimes a RAM capacity problem (the system paging to disk) or a slow drive streaming an open world. Rule those out before you buy anything.
• Chasing zero bottleneck. Some bottleneck always exists; a system with no limiting component would have infinite performance. The goal is a small, cheap-to-fix bottleneck in the component you care about least, not zero.

Frequently Asked Questions

Why is my CPU at 100% while gaming and my GPU only at 50%?

That is the textbook signature of a CPU bottleneck: your processor is maxed out planning frames while your graphics card waits for work. If it happens across CPU-heavy games, your upgrade path is the CPU (and check that background apps are not eating cycles). If it happens in one GPU-heavy game, something else may be wrong, like a driver issue or a frame rate cap.

Is it necessary to upgrade your CPU when you upgrade your GPU?

Not automatically; it depends on what you play. If you play GPU-bound AAA games at 1440p or 4K, a big GPU upgrade on an older but decent CPU usually pays off immediately, because the GPU was the limit. If you play CPU-bound esports or sims at high refresh rates, a new GPU may barely move your FPS, because the CPU was already the wall. Run the resolution drop test before you buy: if dropping resolution boosts FPS a lot, the GPU upgrade is safe; if it does not, upgrade the CPU first or buy both.

Is it worth downgrading the CPU for a better GPU?

Sometimes. At 1440p or 4K in GPU-heavy games, shifting money from the CPU to the GPU is often the right call: a mid-range CPU plus a stronger GPU beats a flagship CPU plus a weaker GPU for cinematic gaming. At 1080p high-refresh competitive gaming, it is usually the wrong call, because the CPU is doing the heavy lifting there. Also factor in platform costs: a cheaper CPU on a different socket can force a motherboard and RAM change that wipes out the savings.

How much does a CPU affect gaming?

It depends entirely on the game. In a logic-heavy game like Minecraft with mods, the CPU does nearly all the heavy lifting and matters enormously. In a graphics-heavy game like Cyberpunk 2077 with ray tracing at 4K, the CPU matters much less once it is fast enough to feed the GPU. The CPU always matters for frame pacing and 1% lows: even in GPU-bound games, a weak CPU can cause stutter that a strong GPU cannot fix.

Is Valorant CPU or GPU intensive?

Valorant is primarily CPU-intensive, especially on mid-range and better PCs chasing high frame rates. Riot built it to run on modest hardware, so the visuals are light and single-core CPU speed drives FPS far more than GPU power. On very weak systems with integrated or old graphics, it can become GPU-bound, but for most gaming PCs the CPU is the lever that matters.

Which graphic settings depend mostly on the CPU?

Settings that increase the amount of things in the world tend to load the CPU: draw distance and view distance, object and crowd density, physics quality, and sometimes shadow quality (in games where the CPU culls shadow casters). Texture quality, anti-aliasing, resolution, and ray tracing are almost pure GPU. So if you are CPU-bound, lower draw distance and density settings first; if you are GPU-bound, lower textures, shadows, and resolution first.

Key Takeaways

• Every game has a bottleneck; it is a property of your PC plus the game plus your settings, not of your PC alone.
• Esports, sims, city builders, and strategy games are usually CPU-bound. Cinematic AAA games with ray tracing are usually GPU-bound. Battle royales swing with your settings.
• The resolution drop test is the fastest way to identify your limit in any game: FPS jumps mean GPU-bound, FPS stuck means CPU-bound.
• Higher resolution pushes the bottleneck to the GPU; higher refresh rates push it to the CPU. DLSS and FSR relieve the GPU and can expose a CPU limit.
• Upgrade the side your games actually stress, verify with the test first, and stop chasing a zero bottleneck.

Conclusion

The difference between cpu intensive vs gpu intensive games is really a question about what each game asks your PC to do: simulate a living world, or paint a beautiful one. Once you know which kind your favorite games are, everything else gets simpler. You buy the right component, you tune the settings that actually matter, and you stop guessing. Run the five-minute test on the games you play most this week. Whatever it tells you, that is your upgrade plan, and it will save you from the most common mistake in PC building: spending good money on the part that was never the problem.