Updated
Does your crosshair rest too low, too high, or wander between the two? Start with the report's Head-level shots, use average lean to choose a review question, then inspect the demo before choosing a drill. The examples below are illustrations, not real player data.
This page is specifically about pre-aim and crosshair placement as a measurable signal. For broad fundamentals see the CS2 aim training guide; for the upstream movement problem see CS2 counter-strafe analysis.
Head-level shots is the share of your measured shots fired with the view pitch within ±2° of level. A higher share means more shots near geometric level. It does not mean those shots were on an enemy's head.
In the deep dive, Vertical pre-aim angle shows Average lean at shot: the signed mean pitch, where positive = below level and negative = above level. A mean beyond +3° is labelled Aiming low; below −3° it is Aiming high. Otherwise the label is No steady lean. These labels describe average direction, not placement quality.
Level is a geometric proxy: expected head height depends on stance, distance, and elevation. Holding near the expected head position can reduce vertical correction. An average view angle near level does not prove that your crosshair was on a head.
Use the demo to review where your crosshair rested before contact and how far it had to move before the shot.
In game: your crosshair rests around the floor or torso before contact, then you pull upward to reach the expected head position. Review a repeatable angle, such as Mirage A ramp toward ticket, and check whether this actually happens before your shots.
In the report: for example, Head-level shots of 20% alongside Average lean at shot of +4.5° and Aiming low suggests a downward bias worth reviewing. The low share is the height-quality signal; the positive mean supplies the direction.
Ten-minute drill: spend two minutes identifying a standing head-height reference at that angle in an offline practice session. Spend six minutes repeating the approach slowly, setting your crosshair on that reference before exposing yourself. Spend two minutes repeating at normal pace. Check crouched positions and elevation changes separately rather than holding one height everywhere.
Recheck with the next demo: compare Head-level shots and Average lean at shot, then replay similar approaches. Look for a higher head-level share and fewer upward corrections. A smaller positive mean alone is insufficient: new high shots could cancel the low ones.
In game: you hold above the expected head position, then pull downward as an opponent appears. Check whether you carried a crosshair height from a higher position into a level-ground duel.
In the report: for example, Head-level shots of 20% alongside Average lean at shot of −4.5° and Aiming high is the mirror case. The negative mean identifies an upward bias; it does not measure how far every shot missed a head.
Ten-minute drill: spend two minutes checking a head-height reference from one fixed position. For six minutes, repeat a short route into that angle, lowering your resting crosshair to the reference before peeking. Use the last two minutes at normal pace, checking that you have not replaced a high hold with a low one.
Recheck with the next demo: look for a higher Head-level shots share and fewer downward corrections on comparable angles. Read Average lean at shot for direction, but do not treat a move toward 0° as proof of improvement.
In game: some approaches start low and others high. You make vertical corrections in both directions, especially when switching between angles. Confirm this in the replay: a match-wide average cannot identify the cause or the particular corner.
In the report: for example, Head-level shots of 15% with Average lean at shot near 0° and No steady lean is a reason to investigate scatter. It is not a good-placement verdict. Where available, use Pitch distribution at shot to inspect the spread; older saved results may not have this chart.
Ten-minute drill: spend two minutes choosing two adjacent angles and checking their expected head positions. Alternate between them slowly for six minutes, pausing to reset the crosshair before each peek. Spend two minutes repeating without the pause while keeping the same references.
Recheck with the next demo: prioritize a higher Head-level shots share and replay the same transitions for fewer corrections in either direction. Average lean at shot may stay near 0° throughout; that is why it cannot tell you whether scatter improved. Match context changes, so one demo is a review cue rather than proof that a drill worked.
Use the numbers the report actually displays, keeping their different samples separate:
For a more complete view of what demo analysis can and cannot prove, see CS2 demo analysis limitations.
Practise one angle family per session. See demo to training plan for how to sequence this across a week.
Check your pre-aim from a demo