Cities Skylines 2 CPU Bottleneck | Fix Guide Settings and Proven Tweaks

Quick answer: Cities Skylines 2 CPU bottleneck problems come from its agent-based simulation, where every citizen, car, and service is a live calculation. Lowering graphics settings will not fix it. To fix it, confirm the bottleneck through simulation speed, change the settings that reduce CPU load, and pick hardware around single-core speed and cache instead of buying a bigger GPU.

If you built a city past 100,000 people and watched everything slow down, you are not imagining it, and your graphics card is probably not the problem. A player on an RTX 5070 and a Ryzen 7 7800X3D asked on the Steam forums why his city ground to a halt the moment it got congested, even with strong hardware. Another player with an RTX 5090 watched his GPU sit under 50 percent utilization while the game chugged. That is what a Cities Skylines 2 CPU bottleneck looks like. It does not show up as a slideshow of frames. It shows up as time itself slowing down.

This guide is different from the generic “low FPS fix” articles that tell you to lower your resolution and update drivers. This is the definitive Cities: Skylines 2 CPU bottleneck fix guide. You will learn why the game is so CPU hungry, how to confirm the bottleneck on your own PC, which settings reduce CPU load and which only reduce GPU load, which CPUs actually run large cities, and the step by step checklist that fixes most CPU-bound problems.

 Why Cities Skylines 2 Is a CPU Killer

Most games ask your CPU to do a little bit of work: handle game logic, feed the GPU draw calls, and keep the frame pacing smooth. Cities: Skylines 2 asks your CPU to simulate a living city. That is a completely different job.

The game uses an agent-based simulation built by Colossal Order on the Unity engine. Every citizen is an agent with a job, a home, a route, and decisions to make. Every car, bus, train, and garbage truck needs pathfinding through your road network. Water, electricity, services, the economy, weather, and pollution are all separate simulations running at once. When your city has 50,000 people, that is manageable. When it has 300,000, the number of live calculations explodes, and most of them land on the CPU.

Colossal Order’s own technology chief said it plainly before launch: a growing city will inevitably become CPU bound, and the game targets 30 fps for that reason. That is a remarkable admission, and it tells you everything about where to spend your upgrade budget. This game will always become CPU limited. The question is only how big your city can get before it happens.

There are two more technical realities worth understanding. First, simulation work in a game like this does not split evenly across all your CPU cores. Pathfinding and agent updates have parts that must happen in sequence, which means single-core speed and cache matter more than a huge core count. That is why a Ryzen 7 7800X3D often outperforms CPUs with far more cores in this game. Second, the workload grows roughly with population and service complexity, not with graphics settings. A dense, detailed city of 200,000 can run slower on identical settings than a simple city of 500,000, because the number of agents and services is what feeds the CPU.

Takeaway: your CPU is the engine room of this game. The GPU only paints the picture.

Official System Requirements vs Real World Reality

Paradox Interactive raised the official system requirements before launch after admitting the game had missed its performance targets. That context matters, because it means even the recommended specs were set as a floor, not as a guarantee of smooth play. Here are the final official specs:

Component	Minimum	Recommended
CPU	Intel Core i7-6700K or AMD Ryzen 5 2600X	Intel Core i5-12600K or AMD Ryzen 7 5800X
GPU	Nvidia GeForce GTX 970 (4 GB) or AMD equivalent	Nvidia GeForce RTX 3080 (10 GB) or AMD equivalent
RAM	8 GB	16 GB
Storage	60 GB available space	60 GB available space
OS	Windows 10 Home 64 Bit	Windows 10/11 64 Bit

Now here is the real world truth that every experienced player will tell you. The minimum spec gets the game to launch. It does not get a real city to run. The recommended spec handles a small to medium city fine. But once you push past roughly 100,000 to 150,000 population, even recommended hardware starts to show the signature symptom: not low frame rates, but slow simulation speed. Players on hardware well above recommended have reported cities of 220,000 people nearly freezing, with every graphics option turned all the way down. Graphics settings were never the bottleneck in those cases. The CPU was.

A useful mental model: treat the recommended spec as the requirement for a pleasant small city, and read the CPU section of this guide as the requirement for the city you actually want to build.

Takeaway: the printed requirements describe launching the game, not playing it at scale.

How to Confirm a Cities Skylines 2 CPU Bottleneck

Before you change anything, confirm that your problem is actually a CPU bottleneck. This game has two separate performance problems that feel similar but have different fixes, and most players mix them up.

The frame rate problem is about how smooth the picture looks. This is mostly the GPU’s job. If your picture stutters when you rotate the camera over a dense downtown, but city time flows normally, that is a rendering problem.

The simulation speed problem is about how fast the city itself runs. Cars crawl, citizens move in slow motion, and the game speed buttons feel like they do nothing. This is the CPU bottleneck, and it is the signature Cities: Skylines 2 problem. One forum user with a 500,000 person city found his simulation running at one eighth of normal speed while his frame rate stayed perfectly fine. That is the clearest possible proof: the picture was smooth, the city was in slow motion.

Here is how to confirm it on your PC:

1. Load your biggest city and set the game speed to 2x or 4x. If the visible speed of cars and people barely changes, your CPU cannot keep up with the simulation. A healthy system shows an obvious difference between 1x and 4x.
2. Open the game’s developer mode and check the simulation tab. The game has a built in simulation readout that shows how the sim is keeping up. Community members point to the “smooth speed” figure: it should match the speed setting you selected. If it sits far below, the CPU is the limiter.
3. Watch per core CPU usage, not total CPU usage. Open Task Manager or HWiNFO while the game runs. Total CPU usage can look low even during a CPU bottleneck, because the simulation threads are waiting on each other. One or two cores pinned near 100 percent while the GPU idles is the classic picture.
4. Check GPU utilization at the same time. If your GPU sits at 40 to 50 percent while the city crawls, the GPU is waiting on the CPU. The player with the RTX 5090 who saw his GPU never break 50 percent was watching this exact scenario.
5. Lower every graphics setting to minimum as a test. If the slow motion city barely changes, graphics were never the problem. This is the fastest five minute diagnostic you can run.

One honest note: if only the frame rate is bad and the simulation runs at full speed, you have a GPU side problem, not a CPU bottleneck. The fix table in the next section is built around that distinction.

Takeaway: slow motion city plus idle GPU equals CPU bottleneck. Diagnose before you upgrade.

CPU Load Settings vs GPU Load Settings 

This is the section other guides get wrong. Most “fix low FPS” articles give you one list of settings to lower. But in Cities: Skylines 2, lowering the wrong settings wastes your time, because half of them only reduce GPU load while your actual problem sits on the CPU. The table below splits them honestly.

Setting	What It Mostly Stresses	Lower It If Your Problem Is…
Level of Detail (LoD)	CPU and GPU	CPU bottleneck (biggest CPU saver)
Simulation speed priority	CPU	CPU bottleneck
Maximum pre-processed frames	CPU/GPU sync	CPU bottleneck (raise to 2 or 3)
Population density detail	CPU	CPU bottleneck in dense areas
Global Illumination	GPU	Low frame rate only
Volumetrics	GPU	Low frame rate only
Shadows quality	GPU	Low frame rate only
Ambient Occlusion	GPU	Low frame rate only
Depth of Field	GPU	Low frame rate only
Texture quality	GPU and VRAM	Low frame rate on weak GPUs
Anti-aliasing	GPU	Low frame rate only
Resolution	GPU	Low frame rate only

Level of Detail deserves special attention. VideoGamer’s testing found that dropping Level of Detail to Very Low made a major difference to performance without visibly hurting the picture much. In a simulation heavy game, that setting controls how much per object processing the CPU has to do, which is why it helps a CPU bottleneck while shadows and volumetrics do not.

Two settings in the options menu are especially relevant to CPU bound players. First, there is a toggle that lets you prioritize simulation speed over frame rate. If your problem is slow motion cities, try favoring simulation. Second, there is a slider for maximum pre-processed frames, which runs from one to three. Players on the Steam forums report that pushing this to two or three gives the CPU more breathing room to feed the GPU, at the cost of slightly more input lag. If you are CPU bottlenecked, that tradeoff is worth testing.

What about upscaling and frame generation? DLSS, FSR, and frame generation reduce GPU load and can make a CPU bound game feel smoother, because the GPU side stops being a problem and frame pacing improves. They do not fix the simulation itself. Think of them as a comfort upgrade for the rendering side while you fix the real problem on the CPU side. If you want the full breakdown of what upscaling can and cannot do for CPU limited games, our guide on whether DLSS reduces CPU bottlenecks covers it in detail.

Takeaway: change Level of Detail and simulation settings for CPU problems. Change shadows and volumetrics only for frame rate problems.

Which CPUs Handle Cities Skylines 2 Best

For most games, the best CPU advice is simple: buy the fastest gaming CPU you can afford. For Cities: Skylines 2, the advice is more specific. You want strong single-core performance, a large cache, and enough cores to spread the simulation workload. Cache turns out to be unusually important here, which is why AMD’s X3D chips are so popular with this game’s community.

The table below gives practical CPU tiers by the city size you are targeting. These are informed by community experience and hardware discussions, including a long Tom’s Hardware thread where experienced players compared chips specifically for this game. Think of them as starting points, not guarantees, because mods, assets, and city density change everything.

Target City Size	Recommended CPUs	Notes
Up to ~50,000	Ryzen 5 7600X, Core i5-13400F, Ryzen 5 5600X	Budget builds handle small cities fine
~50,000 to 150,000	Ryzen 7 7800X3D, Ryzen 7 7700X, Core i5-14600K	The sweet spot for most players
~150,000 to 300,000	Ryzen 7 9800X3D, Ryzen 9 7950X3D, Core i7-14700K, Core Ultra 7 265K	X3D cache or strong hybrid cores help here
300,000+	Ryzen 9 9950X, Core Ultra 9 285K, Ryzen 9 7950X	Enthusiast territory, and even these will eventually hit a wall

A few explanations so the table actually makes sense. In that Tom’s Hardware discussion, one experienced player estimated roughly 150,000 population per 8 cores before the simulation starts to stagnate, which is why core count becomes the soft ceiling for the very biggest cities. But cores alone are not the answer: the same discussion warned that single-threaded performance and cache are what keep mid size cities smooth, and a chip like the 7800X3D often punches above its core count for exactly that reason. Note the 7800X3D shows up in the mid tier, not because it is weak, but because players with large congested cities have reported even it slowing down around 300,000 plus population. No consumer CPU makes you immune. You are buying a higher ceiling, not removing it.

Two honest caveats. First, platform matters: a modern mid range chip like the Core i5-14600K has been reported by players to outperform older i9 chips in this game, so do not assume an old flagship beats a new mainstream chip. Second, these are player reported outcomes, not lab benchmarks, because almost nobody publishes rigorous CPU benchmarks for Cities: Skylines 2 specifically. Treat the tiers as informed guidance.

Takeaway: buy for single-core speed and cache first, core count second, and match the chip to the city size you actually plan to build.

Your GPU What Is Enough vs What Is Wasted

Here is the uncomfortable truth for anyone who bought a flagship card for this game. Cities: Skylines 2 does not need a flagship GPU. The official recommended spec asks for an RTX 3080 or RX 6800 XT, and even a mid range modern card handles the rendering side comfortably at 1440p. The player with the RTX 5090 at under 50 percent utilization is the perfect illustration: his $2,000 class card was sitting idle because the CPU could not feed it work fast enough.

So what is actually enough? For 1080p high settings, an RTX 4060 class card or better is plenty once your CPU is sorted. For 1440p, an RTX 4070 Super or RX 7800 XT class card covers you. At 4K, you need more GPU muscle, something like an RTX 4070 Ti Super or better, but even then the CPU remains the limiter for the simulation.

The October 2026 Steam Hardware Survey is instructive here: the RTX 5070 is now the most popular GPU on Steam at 6.2 percent of surveyed systems, with AMD’s CPU share at 48.4 percent and octa-core chips past 30 percent. That survey tells you the typical gaming PC has plenty of GPU for this game. It is the CPU side where cities fall apart.

This matters even more right now because of pricing. A 3DCenter report from October 2026, tracking German retail, found RTX 50 series prices up an average of 66 percent over the previous 12 months, with the RTX 5090 up a staggering 132 percent. Spending flagship money on a GPU for a CPU bound city builder in this market is the worst possible value decision. If your upgrade budget is fixed, the CPU upgrade wins for this game almost every time. If you are choosing a GPU for a new build targeting this game, a mid range card plus a better CPU beats a flagship card plus a weaker CPU, and it is not close.

One exception: if you also play demanding shooters or ray traced games, the flagship GPU earns its keep there. This section is about Cities: Skylines 2 specifically. Match the hardware to the game you actually play most.

Takeaway: in a CPU bound game, a mid range GPU with a great CPU beats a flagship GPU with an average CPU.

RAM and Storage Factors That Matter More Than You Think

RAM does not fix a CPU bottleneck, but the wrong RAM setup can make one worse. The official spec says 16 GB, and for a vanilla game that is a fair minimum. But two things push you higher. First, the September 2026 Steam survey found 32 GB has now overtaken 16 GB as the most common memory size among PC gamers, and simulation heavy games are exactly why that trend exists. Second, mods and custom assets eat RAM for breakfast. Players running large cities with heavy mod loads report that 32 GB of fast DDR5 removes the hitching that happens during peak simulation cycles. If you use lots of Workshop assets, treat 32 GB as the real recommendation.

Speed matters too, though not as much as capacity. Faster DDR5 with decent timings helps the CPU feed the simulation a little faster. It will not rescue a weak CPU, but on an otherwise balanced system it is a meaningful few percent.

Storage is simpler. The game needs 60 GB, and it must be on an SSD. That is non-negotiable in 2026. An SSD does not raise your simulation speed, but it slashes load times and asset streaming stutter, and large cities with lots of custom content load far more data. If you are still on a spinning hard drive, this is the cheapest upgrade with the most obvious payoff. For the full picture on how storage limits performance, see our guide on storage bottlenecks. And if you are planning a full build around this game, our RAM guide explains how much memory different game types actually need.

Takeaway: 32 GB of RAM on an SSD is the realistic baseline for serious city builders, especially with mods.

Common Mistakes Players Make With This Game

Buying a flagship GPU to fix a slow city. This is the number one mistake, and it is an expensive one. If your simulation is the problem, a faster GPU changes almost nothing. The money belongs in the CPU.

Judging the bottleneck by total CPU usage. Windows might show 35 percent total CPU usage while two simulation threads are maxed out. If you only glance at the overall number, you will conclude the CPU is fine and chase the wrong fix. Always check per core usage.

Lowering resolution to fix a CPU bottleneck. Resolution is almost purely a GPU load. Dropping from 1440p to 1080p will raise your frame rate if the GPU was the problem, but it does nothing for simulation speed. If the city still runs in slow motion at minimum settings, you have your answer.

Assuming the recommended spec means smooth large cities. The recommended i5-12600K or Ryzen 7 5800X is a good chip, but it was specced for the game at launch scale. A 300,000 person city is a different workload than the spec sheet imagined.

Ignoring background apps. Browsers with dozens of tabs, Discord, streaming software, and updaters all compete for the same CPU threads the simulation needs. On a CPU bound game, closing background apps is not generic advice. It directly frees simulation headroom. Our general guide on how to fix CPU bottlenecks walks through the Windows side of this in detail.

Expecting mods to be free. Every traffic AI mod, realism mod, and asset pack adds simulation or memory work. A heavily modded city can halve the population your CPU can handle. Add mods gradually and watch your simulation speed as you go.

Takeaway: every one of these mistakes wastes either money or time. The diagnostic steps earlier in this guide exist to keep you from making them.

Step by Step CPU Bottleneck Fix Checklist

Work through this list in order. Stop when the problem is fixed.

1. Confirm the bottleneck. Run the five minute test from the diagnosis section: biggest city, 4x speed, check whether the visible speed changes, and glance at per core CPU usage and GPU utilization.
2. Close background apps. Shut down browsers, launchers you do not need, streaming tools, and updaters. Restart the PC if it has been running for days.
3. Set the Windows power plan to High Performance or Best Performance. This stops the CPU from downclocking between simulation bursts.
4. Update GPU drivers and the game itself. Colossal Order has shipped performance patches since launch. Make sure you are actually running them.
5. Set Level of Detail to Low or Very Low. This is the single most effective in game change for CPU bound players.
6. Switch the performance preference to favor simulation speed over frame rate. Test both and keep whichever helps your actual problem.
7. Raise maximum pre-processed frames to 2 or 3. Accept the slight input lag in exchange for smoother CPU to GPU handoff.
8. Lower or disable the GPU only settings. Shadows, volumetrics, global illumination, ambient occlusion, and depth of field. These will not fix the CPU side, but they remove any GPU side drag so you can see the real picture.
9. Try DLSS or FSR upscaling. It reduces GPU load and can smooth out frame pacing, which makes a CPU bound game feel better even though the simulation speed is unchanged. If this is your first time with upscaling, our CPU vs GPU bottleneck explainer shows how to tell which side is holding you back.
10. Reduce city complexity if needed. Fewer active service buildings, simpler transit networks, and fewer mods directly reduce simulation work. This is a gameplay tradeoff, not a settings fix, but it is honest.
11. Consider the hardware upgrade. If you have done all of the above and your city still crawls, the CPU is simply too slow for the city size you want. Use the CPU table earlier in this guide. For most players, a modern 8 core chip with strong single-core performance and a big cache is the upgrade that actually moves the needle. Our signs your CPU is bottlenecking your GPU guide helps you confirm the diagnosis before you spend money.

Takeaway: software fixes first, settings second, hardware last. Most players never need step 11.

Frequently Asked Questions

Which CPU is best for Cities Skylines 2: 9800X3D, 7950X3D, 9900X, 9950X, or 285K? What matters more, cache, clock speed, or core count?

This exact question comes up constantly, including in a long Tom’s Hardware forum thread. The short answer is that you want a bit of everything, but not equally. Cache and single-core speed matter most for smooth play up to a few hundred thousand population, which is why the X3D chips are so popular with this community. Core count becomes the deciding factor only when you push toward truly huge cities, because more cores raise the population ceiling before the simulation stagnates. For most players, a Ryzen 7 9800X3D is the sweet spot. For 300,000 plus population ambitions, the 16 core Ryzen 9 9950X or the Core Ultra 9 285K make more sense.

Is a Radeon RX 7900 XT enough as a GPU for Cities Skylines 2 at 4K?

Yes, comfortably. This question also came from that Tom’s Hardware thread, and the answer from experienced players was clear: the 7900 XT is fine at 4K if you tune the graphics settings, with depth of field off and upscaling enabled. Remember that in this game the GPU is rarely the limiting factor. If your city runs slowly with a 7900 XT, the CPU is the problem, not the card.

Why is my GPU utilization so low on a high end PC? I have an RTX 5090 and it never goes above 50 percent.

Because the game is CPU bound, not GPU bound. Your graphics card can only render frames as fast as the CPU feeds it simulation and draw work. When the CPU is the limiter, the GPU sits idle waiting. This is completely normal for Cities: Skylines 2 on strong GPUs and it is not a driver problem or a broken card. The fix is on the CPU side: settings that reduce simulation load, or a faster CPU.

My city gets congested and everything slows down, and I cannot speed up the simulation anymore. I have an RTX 5070 and a Ryzen 7 7800X3D. What is wrong?

This is a real report from the Steam forums, and it describes the classic CPU bottleneck perfectly. Congestion means more agents, more pathfinding, and more decisions per second. The 7800X3D is a great chip for this game, but even it has a ceiling, and a dense congested city hits that ceiling. Work through the checklist: Level of Detail down, favor simulation speed, close background apps, and consider trimming transit complexity or mods.

How can I speed up the simulation in a 176k city?

Simulation speed is almost entirely a CPU question. Start with the settings that reduce CPU load: Level of Detail, the simulation priority toggle, and fewer active services and mods. Check the developer mode simulation readout to see how far behind the sim is running. And be honest about the ceiling: a 176,000 person city with heavy services is near the limit for mid range CPUs, so this may be the point where a CPU upgrade is the real answer.

Even with all graphics options turned all the way down, my 220k city nearly freezes on a high end PC. Is this normal?

Unfortunately, yes, and it is the single most reported experience in this game’s community. Turning down graphics settings does not help because graphics were never the bottleneck. The simulation load of 220,000 agents plus services is simply enormous. The settings that matter are the CPU side ones in the table above, and beyond that, the answer is a faster CPU or a smaller city.

Is Cities Skylines 2 worth buying with a Ryzen 9 5950X and RTX 5080?

That combination will run the game well. The 5950X has 16 cores and strong throughput, and the RTX 5080 is far more GPU than this game needs. Expect a smooth experience for small and medium cities. Just go in with the right expectation: no hardware runs a million person city at full simulation speed, so buy it for the building, not for infinite scale.

My game speed slows down as my city grows, and I have an older processor like an i9-9900K. Is there any trick to fix it?

There is no magic trick, and anyone selling you one is guessing. What you can do: run the full checklist above, especially Level of Detail, background apps, and the simulation priority setting. The i9-9900K is still a capable chip, but its single-core speed is several generations behind, and this game punishes exactly that. If the checklist does not get you there, a platform upgrade to a modern chip with strong single-core performance is the honest fix.

Key Takeaways

• Cities: Skylines 2 is one of the most CPU bound games on PC. Its agent-based simulation means the CPU does the heavy lifting and the GPU mostly waits.
• A CPU bottleneck in this game looks like slow motion, not low frame rates. Diagnose with simulation speed, per core CPU usage, and GPU utilization before changing anything.
• Level of Detail and simulation settings fix CPU problems. Shadows, volumetrics, and resolution fix GPU problems. Do not mix them up.
• Buy CPUs for single-core speed and cache first, core count second. X3D chips are the community favorite for a reason.
• A flagship GPU is wasted on this game alone, especially with current GPU prices. Spend the budget on the CPU.
• 32 GB of RAM and an SSD are the realistic baseline for serious cities, particularly with mods.
• No consumer CPU removes the ceiling entirely. Bigger cities will always eventually become CPU bound. Plan your build around the city size you actually want.

Conclusion

Cities Skylines 2 will probably never be a game where hardware disappears and only the city remains. But once you understand that the CPU is the whole game, every decision gets easier: which settings to touch, which upgrade to buy, and when to accept that your metropolis has simply outgrown your processor. If you are still unsure whether your CPU is holding back your GPU in this or any other game, run your exact pairing through our bottleneck calculator and check the signs in our CPU bottleneck guide before you spend a dollar.