Open one decisive round, jump to each utility throw and draw its complete trajectory. Compare the throw and its effect against player movement, contact and the round result. For flashes check the recorded victims, for damaging utility check recorded damage, and for smokes inspect the intended lane and any available sightline result. Then keep evidence and conclusion apart: "the flash detonated before the entry and two enemies were recorded blind" is evidence; "that was the right flash" is interpretation.
Start with evidence, not a verdict
A CS2 demo records game state and events, and the utility view turns that into something you can interrogate. Throws are grouped by type and round; selecting one jumps the replay to it and draws its complete trajectory in the 3D world — release point, bounces, destination. Smokes are not represented by a sprite: they render as real volumes driven by the voxel data recorded in the demo, which is the difference between judging where a smoke was and judging what it actually covered.
Depending on the recording and the processed cache, an individual throw can also carry:
- Flash victims — who the demo says was blinded and for how long, including whether a victim was recorded looking away.
- Utility damage — recorded damage attributed to the thrower's HE, molotov or incendiary.
- Repeated starts — how many other throws in the match began from close to the same origin, which is how you spot a lineup someone actually practised versus one they improvised.
- Smoke-blocked sightlines — pairs of positions the smoke geometrically blocked. When this cannot be computed, the interface says sightlines are unavailable and gives the reason, rather than quietly showing nothing.
That last behaviour is the one to internalise. None of these numbers reveal the team's intended execute, a player's attention, or a voice call. Where a metric could be mistaken for causation, the interface labels it — observed movement after a flash is shown as observed movement, with no causation claim attached. Write two lines for every important grenade:
- Observed: what the replay or event data directly shows.
- Interpretation: what you think the utility was for, and whether another choice may have worked better.
Read what a CS2 demo analyzer can and cannot tell you before making broader claims from any of it.
A round-by-round utility review workflow
- Choose the round and the purpose. Start with an entry, a site hold, a retake or a post-plant where utility plausibly shaped the result.
- Watch it once without pausing. Note the first contact, the space gained or lost, and the outcome.
- Open the utility tab. Count the recorded throws, then jump to each relevant smoke, flash, HE or fire grenade.
- Draw the trajectory. Inspect the release point, the path, the bounces and the destination in the world instead of judging an inventory icon. N toggles grenade trails if you would rather see paths without leaving the replay.
- Compare the timeline. Look at where teammates and opponents were when the grenade left the hand, and again when its effect began.
- Check recorded outcomes. Use flash-victim events and utility damage where present. For a smoke, use a sightline result only when the interface reports it as available.
- Write one actionable change tied to an observable cue: a teammate's position, contact, bomb state, or the start of a coordinated move.
What to inspect for each grenade type
Smokes
Follow the trajectory to its destination, then switch to free or top-down camera. Ask which lane it occupied, who could move while it was active, and whether teammates actually used the space. Because smokes render as real volumes, you can put the camera at head height on either side and see what was and was not covered — a smoke that looks correct on a radar line can still leave a gap that decided the round.
When the review reports smoke-blocked sightlines, treat that as geometric evidence about the reported pairs — not proof that any player was watching or reacting to the smoke. If sightline analysis is unavailable, review the reconstructed scene directly and say so in your notes.
Flashbangs
Compare the detonation against the supporting peek. Recorded blinded-player events and their durations show who the demo says was affected; they do not prove where a player's attention was, or that the blind caused the next kill. A flash that lands on three opponents but arrives after the entry fight is still badly coordinated. A flash with no recorded victim may still have forced a turn — but that is interpretation unless the replay supports it.
The "looking away" annotation on a victim is worth reading carefully. It tells you the demo recorded the victim facing away, which changes how much the blind mattered. It does not tell you they turned because of the flash.
Molotovs and incendiaries
Inspect where the fire lands relative to the intended choke, the plant position or the clearing route. Then check whether players moved, waited or fought around it, and whether recorded utility damage followed. Damage is one outcome, not the purpose: space denial and delayed movement have to be assessed from round context, without inventing intent.
HE grenades
Check the trajectory, the detonation location and the recorded utility damage. Compare the throw against opponent positions visible in the replay. Avoid concluding that a player "knew" someone was there unless the preceding POV and events support that information actually existing.
Review timing without inventing a magic number
There is no universal correct delay between a grenade and a peek, and any guide that gives you one in seconds is making it up. The useful comparison is the sequence recorded in that round. Pause before the throw, at the effect, and at first contact, then ask:
- Was the entry player ready to move when the flash or smoke took effect?
- Did defenders regain the lane before teammates arrived?
- Did the throw expose its user, or leave another lane unsupported?
- Was the grenade reacting to recorded information, or thrown before that information existed?
- Did two teammates duplicate the same function while a required lane stayed open?
- Was utility still in inventory when the round reached the situation it was meant to solve?
Describe timing relative to visible events — "before the first player crossed", "after contact", "while the retake players were separated" — rather than against an estimated constant. The frame-step keys , and . put you exactly on the release and the detonation; the rest of the navigation is in the controls reference.
Re-throw the lineup you just reviewed
The most useful thing you can do with a bad smoke is throw it again. Any supported throw in the utility view can be opened directly in practice: you are placed at the recorded release position, on the recorded side, with a ghost of the original trajectory to throw against. G toggles that ghost, R resets the attempt, and Esc returns you to exactly where the replay was paused.
This matters because the grenade behaviour underneath is the ported CS2 throw and physics, not an approximation — a lineup that works in practice is a lineup that works. Throws can also be exported as a lineup, which is how a team turns "that smoke was slightly short" into a repeatable setup rather than a note nobody reads. Grenade types that cannot yet be recreated say so instead of loading something subtly wrong.
CS2 utility demo review checklist
- What was the round situation, and what was this grenade plausibly for?
- Who threw it, and from where?
- Where did the complete trajectory actually end?
- What happened immediately before and after its effect?
- Which flash victims or utility damage are recorded?
- For a smoke: is sightline analysis available, unavailable, or unnecessary for this question?
- Did teammates act while the utility created an opportunity?
- Is your conclusion directly observed, or an interpretation?
- What single cue should change the next throw or the follow-up?
Keep the final note specific. "Wait until both entry players reach the choke before throwing the site flash" is testable. "Use flashes better" is not.
Frequently asked questions
How do you review utility in a CS2 demo?
Choose a decisive round, jump to each recorded throw, inspect its trajectory and outcome, then compare its timing with teammate and enemy movement. Record observations separately from tactical interpretation.
Can a demo prove that a smoke or flash was good?
No. It can show recorded state, events and outcomes, but the best tactical choice also depends on plans, communication and intent that may not exist in the demo.
What utility evidence does the demo viewer show?
Depending on available demo and asset data, the review can show throws by type and round, complete trajectories, detonation or landing details, flash-victim events with durations, utility damage, repeated nearby throws and smoke sightline results.
Can I practise a grenade lineup taken from a demo?
Yes. Any supported throw in the utility view can be opened directly in practice, which places you at the recorded release position with a ghost of the original trajectory to throw against. The lineup can also be exported.