You just lost a match to someone who felt off: pre-aiming corners, flicking through smoke, never missing a spray. Before you call it in chat and move on, here's how to actually check whether a CS2 player is cheating instead of guessing. None of these steps require cheats of your own, special access, or paid tools.
Step 1: Pull up their public record first
Most of the useful signal lives outside the match you just played. Before you rewatch a single round, look at the account itself: VAC and game-ban history, account age, CS2 hours and profile visibility (and, by hand, how many of their Steam friends are banned). A fresh account with 40 hours, a private profile and three VAC-banned friends is telling you something the scoreboard can't.
This is exactly what a reputation lookup is for. Paste a Steam profile URL or SteamID into the CSWatch lookup and you'll get the ban record, an account-legitimacy read, community reports filed against them, and an aggregated reputation score, in one view instead of clicking through five sites. If the account is already flagged or convicted, you have your answer without watching anything.
Step 2: Get the match and watch the demo
The scoreboard is not evidence. The demo is. Every Premier and Competitive match records a server-side demo you can rewatch from any player's point of view, including the suspect's. To get it, open CS2 → Watch → Your Matches, find the game, and download it. If a teammate has the match share code, you can paste that in to pull the same demo, or run it through the match checker to see every player's bans and reputation.
Watch the suspect in first person, not the kill-cam. The kill-cam is smoothed and misleading; the raw POV is where cheating shows. If you want a structured approach, we wrote a full demo-review checklist, but the short version is below.
Step 3: Know what aimbot actually looks like
Real aimbot rarely looks like a cartoon snapping 180° onto heads. The common tells are subtler:
- Pre-aim before information. The crosshair sits on head level, locked onto an enemy through a wall, before there is any sound or visual cue the enemy is there.
- Identical micro-corrections. Human aim varies. An aim-assist routine produces the same tiny snap-to-target motion on kill after kill: a flick that always decelerates the exact same way.
- Tracking through smoke and flashes. The crosshair follows an invisible enemy's head through a smoke or while fully blinded.
- Recoil that's too clean. Long sprays that stay pinned to the head with no spray-pattern drift suggest a no-recoil script.
Step 4: Know what wallhack looks like
Wallhacks (ESP) are about information, not aim, so you watch for decisions a player shouldn't be able to make:
- Pre-firing exact positions round after round, including unusual off-angles nobody holds by default.
- Tracking enemies through walls: the crosshair drifts with a hidden player's movement.
- Repeatedly "guessing" rotations and never over-peeking into empty angles, as if they always know exactly who is where.
- Wallbangs into specific spots with no audio or utility reason to commit.
One instance proves nothing; anyone can read a tendency or get a lucky pre-fire. The signal is consistency across many rounds. Cheating is a pattern, not a moment.
What is NOT evidence
Being good is not cheating, and accusing skilled players poisons the whole reporting system. None of these, on their own, mean anything:
- A high K/D, a long ace, or a clean clutch.
- A smurf stomping a low lobby: annoying, against the rules, but a separate problem from cheating.
- A single suspicious flick or one lucky pre-fire.
- A high headshot percentage in isolation: some maps, weapons, and playstyles produce naturally high HS%.
Step 5: If you're confident, make it count
The in-game report helps Valve's automated systems but mostly disappears into a queue you never hear back from. To get a suspect actually looked at by humans, file a report with the match share code as evidence so community reviewers can watch the same demo and vote. We cover the full process in how to report a cheater in CS2.
And remember the limits of a clean record: as we explain in how VAC detection actually works, no VAC ban only means they haven't been caught running a publicly-known cheat, not that they're clean. That's exactly why account history plus demo review beats trusting the ban badge alone.
The fast version
- Check the account first: look them up on CSWatch for bans, history, and existing reports.
- Download the demo and watch the suspect in first-person POV.
- Look for pre-aim before info, identical flicks, smoke-tracking, and too-clean recoil, repeated across rounds.
- Don't confuse skill or smurfing with cheating.
- If you're sure, report with the share code so it gets reviewed.
Have the share code from the game? Run it through the match checker to see every player's bans and reputation