Reporting a cheater in CS2 takes ten seconds in-game — and most of those reports vanish into a queue you never hear about again. Here's how the reporting pipeline actually works, why so little seems to happen, and how to file a report that a human will genuinely review.
The in-game report (do this, but know its limits)
During or right after a match, open the scoreboard, click the suspect's name, and choose Report. Pick the most accurate category — Cheating for aimbot/wallhack, separate from griefing or abuse. You can also report from Watch → Your Matches after the game by opening the match and reporting from there.
This feeds Valve's automated trust systems. It is worth doing every time. But understand what it is: a single data point thrown into an enormous pile. You will almost never get feedback, and a lone report rarely moves anything on its own. Volume and corroboration are what matter. (And note: CS2 never got Valve's Overwatch — the human review queue that existed in CS:GO — so there's no community verdict on the other end anymore.)
Why most reports feel like they go nowhere
Scale. Millions of matches are played daily, and Valve's detection deliberately runs on delay — bans arrive in coordinated waves weeks later so cheat developers can't reverse-engineer which signature tripped. (We break this down in how VAC detection actually works.) So even when your report contributes to a ban, you won't see a timestamped "thanks, we banned them." The system is real; it's just silent and slow, and it misses the entire tier of paid and DMA cheats that VAC can't see.
Grab the match share code — this is the key step
The single most useful thing you can do is capture the match share code. It's a short string like CSGO-xxxxx-xxxxx-xxxxx that lets anyone load the exact demo and watch the suspect from every angle. A report with a share code is evidence; a report without one is hearsay.
To get it:
- Open CS2 → Watch → Your Matches.
- Find the match and select it.
- Copy the share code (also retrievable later from your match history).
Hang onto it. Whether you escalate to a community review or just want to rewatch the rounds yourself, the share code is what makes the evidence portable.
Make it count: file a report that gets reviewed
This is where community oversight fills the gap Valve's silent queue leaves. On CSWatch you can look the player upand submit a report with the match share code attached. That demo then goes to community Overwatch reviewers who watch the same footage and vote guilty or insufficient. Convictions require a reviewer majority, and the verdict becomes part of the player's public record — visible to anyone who looks them up later.
The difference from the in-game button: it's transparent. You can see the case, the reviewer count, and the outcome, instead of trusting an invisible pipeline. And because the result is public, a confirmed cheater follows their own account around rather than getting a clean slate every match.
How to write a report reviewers can act on
- Attach the share code.Without the demo, there's nothing to review. With it, there's everything.
- Name the cheat type."Wallhang — pre-fires my exact spot every round" points reviewers at specific rounds far better than "obvious cheater."
- Note round numbers or timestampswhere the behaviour is clearest, so a reviewer doesn't have to watch all 24 rounds blind.
- Be honest about confidence.Smurfing and raw skill aren't cheating — if you're unsure which it is, check first (see how to check if someone is cheating in CS2) before filing.
What not to do
- Don't mass-report good players out of tilt. False reports waste reviewer time and erode the signal everyone relies on.
- Don't expect an instant Valve ban — even correct reports surface on Valve's timeline, not yours.
- Don't rely on a clean VAC badge as proof of innocence; it only means "not yet caught."
The fast version
- Report in-game every time — it feeds Valve's systems, but quietly.
- Grab the match share code from Watch → Your Matches.
- File it on CSWatch with the share code so community reviewers actually watch the demo and vote.
- Describe the cheat type and the rounds where it's clearest.
- Check before you report — don't confuse skill or smurfing with cheating.