Cache Is Back: The CS2 Season 5 Map Pool, and Why Your Veto Is About to Be Wrong

On July 6, Cache enters the Active Duty pool and Overpass leaves. That's the headline. Here's the part that costs people ELO: your entire veto muscle memory — permaban, comfort pick, "we always leave that one up" — was trained on a 7-map pool that no longer exists.

What actually changes on July 6

• Cache is in. The 2026 rebuild — familiar bones for CS:GO veterans, new timings and sightlines for everyone.
• Overpass is out. Every veto plan that referenced it — as a ban, a pick, or a "they can have it" — has a hole in it.
• Six maps carry over. Mirage, Dust2, Inferno, Nuke, Ancient, Anubis. All of your — and your enemies' — history on them is still fully valid.

A detail from our own scan data worth knowing: across hundreds of scanned FACEIT matches last season, Overpass was the least-played map in the pool — it showed up as the played map roughly six times less often than Mirage. Its exit changes fewer games than people think. What it changes is vetoes — because even unplayed, it soaked up bans and shaped what remained.

Why the first weeks are free ELO

For the first few weeks, nobody has meaningful Cache stats. No 100-game win rates, no reliable reads. That means two things, and most players will get both wrong:

1. Cache is a dice roll. If neither team has drilled it, playing it is a coin flip you chose voluntarily. The team that avoids the dice and steers toward its proven maps is stealing expected value in every veto.
2. The other six maps matter MORE, not less. All the information that still exists lives there. If the enemy stack wins Inferno at 65% over their last 30 games, that fact survived the pool change perfectly intact — and almost nobody will check it.

The veto rules for Season 5's opening month

• If Overpass was your permaban — congratulations, you have a free ban. Spend it on whatever the enemy is best at. Spending it on Cache "because it's new" only makes sense if your team is worse on it than they are — which you can't know yet. Ban information, not novelty.
• If Overpass was your pick, you have a pool hole. Fix it deliberately: pick your second-best map by the numbers, not by feel. And expect anyone who scans you to see the hole too.
• Ban what THEY win, not what you hate. This was true before Season 5 and it's doubly true now: with one map of pure uncertainty in the pool, wasting a ban on autopilot is a bigger relative error.
• Only pick Cache on purpose. If your five have actually drilled it, early Cache is a legitimate cheese pick — you're the only team at the table who isn't rolling dice. If you haven't, don't.

Reading the enemy's maps: the manual way and the fast way

Manual: open each enemy player's FACEIT profile, tab through their map stats, and mentally average five players' win rates per map while the veto timer runs. It works; it takes longer than the timer gives you.

Fast: take your match room URL and swap faceit.com for sfaceit.com. The room gets scanned — every player's real per-map history, smurf flags, and a win probability for each remaining map, yours vs theirs. We track how those probabilities perform publicly — across 800 resolved matches, confident calls hit 76.7%.

One honest caveat for Season 5: Cache itself will show thin data for a while — for everyone, on every tool. When the sample is small we say so instead of inventing a number. The edge in July isn't a magic Cache read; it's that the other six maps are fully readable and your opponents aren't looking.

FAQ

Is Cache in the CS2 map pool?

Yes — Cache enters the Active Duty map pool on July 6, 2026, when CS2 Premier Season 5 starts, replacing Overpass. It's Cache's first appearance in the competitive pool since the CS:GO era, in a rebuilt 2026 version.

What map did Cache replace in CS2?

Cache replaces Overpass. Mirage, Dust2, Inferno, Nuke, Ancient and Anubis all carry over from the Season 4 pool.

When does CS2 Premier Season 5 start?

July 6, 2026. FACEIT matchmaking follows the Active Duty pool, so the change hits your FACEIT vetoes immediately.

How should I veto after the pool change?

Ban the enemy's best proven map instead of autopiloting your old permaban, treat Cache as a coin flip until you've actually drilled it, and lean harder on per-map win rates for the six carried-over maps — that history is still fully valid and most opponents will ignore it.

Related: the full map veto strategy guide · AI anti-strat: countering a team's demos before round 1 · spotting smurfs after the reset.