AimFinder

CS2 demo analysis

Upload CS2 demos of your matches. AimFinder measures how you flick onto every kill (overshoot, correction time, crosshair placement) and derives sensitivity propositions from how you actually play.

…

What the replay report measures

The analyzer replays your match server-side and reconstructs every kill: how many degrees the fight required, how far your first ballistic movement actually travelled (its overshoot or undershoot), how long you spent correcting, where your crosshair sat when the fight started, and whether you were properly stopped when you fired.

Kill by kill, those numbers aggregate into your systematic bias — the strongest sensitivity signal a replay contains. The report turns it into a concrete cm/360 and sensitivity proposal, with a separate headshot-only segment once at least 8 headshot kills are available, and always shows the sample size behind every figure.

Upload two or three recent matches for a trustworthy average; one match is a first look, not a diagnosis. The proposal is best validated with the 10-minute in-browser test afterwards.

How to get a replay file

CS2 → Watch tab → Your Matches → download; Faceit serves demos from each match room. The analyzer accepts .dem files and the compressed .dem.bz2 / .dem.gz / .zip forms those platforms serve, up to 400 MB — no unzipping needed.

Full walkthrough with file locations: how to download a CS2 demo.

What happens to the file

The replay is parsed and then immediately deleted from the server. Only the per-kill aim numbers for your player are kept, tied to your account so your reports stay available. Deleting the account removes everything — details in the privacy policy.

Replay analysis FAQ

Is uploading replays VAC-safe?

Completely. A replay is a file the game itself gives you; analyzing it happens on AimFinder’s server, entirely outside CS2. Nothing runs alongside the game and nothing touches its files.

Do Faceit demos work?

Yes — upload the .dem.gz exactly as Faceit serves it; the analyzer unpacks bz2, gz and zip itself. Matchmaking and Premier demos from the Watch tab work the same way.

How many replays should I upload?

Two or three recent matches give the per-kill statistics enough volume for a stable average; the report always shows how many kills each number is built on. More recent beats more numerous — your aim from last season is not your aim today.

Why does the report need my current sensitivity and DPI?

A replay only contains camera angles — your settings leave no trace in it. The analyzer needs the sensitivity the match was played at to convert angular bias into a concrete cm/360 and sensitivity proposal.