Cities: Skylines 2 reworks the economy loop from the first game. Where the original leaned on a simple “zone it, tax it, expand” rhythm, the sequel ties industrial output, worker availability, and per-zone tax brackets into a tighter feedback system. Misread the demand indicator and you either stall growth or tank service coverage. This guide covers the mechanics that actually move the budget line: how industry demand is generated, how density changes cost and throughput, and how tax policy stabilizes (or destabilizes) revenue over a city’s first 50,000 residents.

What it covers: The CS2 economy loop — industry demand, density costs, and tax policy that stabilizes revenue. Why it matters: Misread the demand indicator and you stall growth or tank service coverage. Who should pick this: New mayors learning what actually moves the budget line.

The core economy loop

CS2’s budget runs on four interacting cycles:

  1. Zoning creates demand for workers and customers. Residential zones supply workers; industrial and office zones supply jobs and goods; commercial zones sell goods and serve customers.
  2. Industry produces goods consumed by commerce and exported. Goods flow via roads and cargo infrastructure. Bottlenecks here choke the whole chain.
  3. Tax revenue is collected per zone type at a rate you set. This is your primary income.
  4. Services cost upkeep per facility plus per-use costs. Police, fire, health, education, parks, and transit all draw from the same pool.

The RCI bar at the bottom of the screen tracks demand for Residential, Commercial, and Industrial zoning. It updates continuously based on jobs available vs. workers available, goods supply vs. commercial demand, and export capacity. Reading it correctly is the single most important budget skill in the game.

Industrial demand: what actually drives it

Industrial demand in CS2 is not “more factories = more money.” It is a derived demand, pulled by several upstream factors:

Demand sources

  • Commercial zones needing goods. Every commercial building consumes industrial output. If commerce outpaces industry, demand for industrial zoning rises.
  • Export capacity. If your city can ship surplus goods out (via highway connections, cargo harbors, train cargo), industrial buildings stay profitable and demand stays high.
  • Worker availability. Industry needs workers with appropriate education levels. Raw industry (the base industrial zone) prefers low-education workers; if your residential zones over-educate the population, you get a labor mismatch.
  • Land value and services. Industrial zones with good road access, cargo transit, and reasonable services (power, water, garbage) operate at higher efficiency.

What kills industrial demand

  • Traffic congestion on cargo routes. If goods can’t reach commerce or export hubs, factories reduce output and demand collapses.
  • Over-zoning industry. If you zone more industry than commerce and exports can absorb, buildings go underused or abandoned.
  • Worker shortages. Too few residents, or residents educated above what industry needs, starves factories of labor.

The density question

CS2 separates low-density and high-density zoning for residential and commercial. Industrial zoning has a base form and, with milestones/progression, specialized forms; the exact unlock ordering has shifted across patches. The density choice changes cost, throughput, and workforce draw:

Zoning typeUpfront costWorkers per tile (approx.)Tax revenue per tileTraffic load
Low-density residentialLowLowLowLow, car-dependent
High-density residentialHigherHighHighHigh, transit-friendly
Low-density commercialLowLowLowModerate
High-density commercialHigherHighHighHigh
Industrial (base)ModerateModerateModerateHeavy cargo
OfficeModerateHigh (educated)ModerateLight, passenger

Note: per-tile revenue figures scale with land value, service coverage, and tax rate. The table expresses relative relationships, not fixed numbers, and the exact ratios shift between patches.

Tax policy mechanics

This is where most players lose money. CS2 lets you set tax rates per zone type: residential, industrial, commercial, and office each get an independent slider. The default is 9% across the board.

How tax brackets work in CS2

CS2 does not use progressive income brackets in the household-finance sense. “Tax brackets” here refers to the per-zone rate tiers you set. Each zone type pays a percentage of its economic activity as tax to the city. The levers:

  • Residential tax — levied on households, scaled by building level and land value.
  • Industrial tax — levied on industrial output.
  • Commercial tax — levied on commercial sales.
  • Office tax — levied on office activity.

Lowering a rate stimulates growth in that zone (more buildings upgrade, demand rises). Raising a rate extracts more per transaction but suppresses growth and can trigger abandonment if pushed too high.

The 9% default and why people change it

The default 9% is a balanced starting point. Common adjustments:

  • Early game (population < 10k): Many players lower residential to 7-8% to accelerate population growth, since more residents means more workers and more demand. Industrial is often held at 9% or raised to 10% because early industry is profitable and less sensitive.
  • Mid game (10k-50k): As services expand and costs rise, rates are nudged back up. Residential to 9-10%, commercial to 10-11% if goods supply is healthy.
  • Late game (50k+): Stable cities often run 10-11% across the board, with office occasionally lower to stimulate high-education employment.

Worked example: a 20k-population city

Assume a mid-game city with the following weekly tax haul at default 9% (illustrative numbers — actual values vary by city layout, patch, and service level; verify in your save):

Zone typeTaxable buildings (approx.)RateWeekly tax
Residential (mixed density)~4,500 households9%~$18,000
Industrial~600 buildings10%~$9,500
Commercial~700 buildings10%~$7,500
Office~250 buildings9%~$3,000
Total weekly tax~$38,000

If weekly service costs (police, fire, health, education, parks, transit, garbage, power/water upkeep) total ~$30,000, you run an ~$8,000 weekly surplus. That surplus funds loans, new infrastructure, and milestones.

Now raise industrial tax from 10% to 13%. Short-term revenue jumps roughly 30% on that line — call it +$2,850/week. But within a few in-game weeks, industrial demand softens: fewer buildings upgrade, some go underused, and worker demand drops. If the net effect is a 20% reduction in active industrial buildings, you lose ~$1,900/week of base and the higher rate nets only ~$950/week extra — and you’ve weakened your goods supply to commerce, which will hurt commercial tax next. This is the core tax-tuning tension: rates are levers on volume, not just price.

Revenue stability: the real goal

A city that swings between +$15k and -$5k weekly is harder to run than one holding steady at +$3k. Stability comes from three practices:

1. Match service expansion to revenue growth, not milestone unlocks

Milestones unlock services. They do not require you to build them immediately. A common budget error is plopping a full hospital network the moment it unlocks, then watching upkeep outpace tax growth. Build services when demand indicators (complaints, coverage gaps, death waves) force it, not when the unlock notification fires.

2. Keep industrial throughput healthy

Industrial tax is one of your most stable revenue lines because it scales with goods moved, not with fickle residential land value. Protect it:

  • Maintain cargo road redundancy. A single congested highway connection to industry can collapse output.
  • Build cargo harbors or train cargo terminals before industrial demand peaks, not after.
  • Avoid placing industry at the end of long, signal-heavy road corridors.

3. Use per-zone tax as a dampener, not a megaphone

When a zone overheats (e.g., residential demand maxes and you’re growing faster than services can cover), nudge that zone’s tax up 1-2% to slow growth. When a zone stalls, nudge down 1-2%. Small moves, observed over a few in-game weeks, give you a smoother budget curve than large swings.

Death waves and tax feedback

A known CS2/CS1 pattern: if population grows in a burst (high residential demand met with massive zoning), citizens age in cohort, producing synchronized death spikes (“death waves”) that drain healthcare and create abandonment. Tax revenue dips sharply during these waves as buildings empty. Spreading residential zoning over time and avoiding sudden high-density bursts reduces this volatility. Per-zone tax rate is the primary tool for pacing that growth.

Common budget mistakes

  • Raising all taxes to 13% on day one. Suppresses growth, triggers abandonment, collapses the revenue base you’re trying to build.
  • Ignoring industrial traffic. Industry looks fine on the RCI bar but ships nothing because cargo is gridlocked. Revenue flatlines with no obvious cause.
  • Over-servicing early. Full education and healthcare tiers before the tax base supports them creates structural deficits.
  • Treating office like industry. Offices employ educated workers and produce little cargo traffic. They are a workforce sink, not a goods engine. Taxing them like industry misses their role.
  • One tax rate for everything. The per-zone sliders exist for a reason. Flat rates leave growth-pacing leverage on the table.

Quick-reference: tax rate cheat sheet

SituationResidentialIndustrialCommercialOffice
Early growth, need population7-8%9%9%9%
Stable mid-game9%10%10%9%
Revenue crunch, services heavy10-11%11-12%11-12%10%
Overheating residential demand10-11%9%9%9%
Industrial stall / goods shortage9%8%10%9%

These are starting points, not constants. Watch the RCI bar and your weekly budget line for two in-game weeks after each change before adjusting again.

Glossary

  • RCI indicator — the Residential/Commercial/Industrial demand bar. Shows zoning pressure, not guaranteed revenue.
  • Zoning density — low vs. high density for residential and commercial; affects cost, workers, revenue, and traffic per tile.
  • Per-zone tax — the independent tax rate you set for each zone type.
  • Cargo throughput — the rate at which industrial goods move to commerce and export; the hidden cap on industrial revenue.
  • Death wave — synchronized population death spike from cohort aging after burst residential growth.
  • Land value — a per-area score raised by services, parks, and transit; drives building upgrades and tax per tile.
  • Milestone — population-gated unlock of services and zoning options; unlocking does not obligate building.

Sources & further reading

Next read