How to Review a CS2 Demo

During a match you remember the clip and the feeling. The demo remembers the second before the clip: whether you were still moving, whether a teammate was in trade range, whether the smoke you needed was still in inventory. Those details are what repeat. Review is how you stop arguing with memory.

Prefer a recent match, a close loss, or a game that felt like “your normal.” Those files contain the habits you actually play with. A 16–2 stomp mostly teaches you that the lobby was weaker. Reviewing only your best games hides the leak that appears when the game is even.

One complete demo is better than five you abandon at round 8. If you play FACEIT and Premier, pick the ladder you care about this week and stay there.

For each of your deaths, pause and answer only these:

• Was my position necessary — space, info, or a real trade setup?
• Could I be traded, or was I alone?
• Was my crosshair ready, or was I still moving / looking at the wrong angle?
• Did I have utility that would have changed the peek?
• Was I taking an unnecessary duel — ego, leftover tilt, or a fight we did not need?

Write the answer in a few words. “Lost aim” is not an answer until the demo agrees you were stationary, on time, and in a duel you should have taken.

Watch the two seconds before you die and the two seconds after. If a teammate could have traded and was playing the other side of the map, that is a default problem, not a teammate-bashing exercise. If nobody was near you, you chose an island. Note off-angles that worked once and failed the next three times — FACEIT opponents adapt.

Inventory at the start of the round vs inventory at your death tells the story. Saved utility that would have blocked the swing is a note. Utility thrown at nothing, or thrown so late the execute already died, is a note. Do not grade lineups you never intended to use. Grade the nades that belonged to the plan you actually called.

After first contact, jump to the mid-round. Did you rotate on a sound you never confirmed? Did you stay in a lost site for a second kill? Did you force a 2v4 because the score felt urgent? Decisions are visible in the demo as paths and timings. You do not need the opponent’s voice chat to see that you walked through mid 12 seconds late.

Only judge what the demo lets you assess. If voice is recorded and you can hear it, note comms that arrived after the peek or that never included a number. If you cannot hear voice, skip this section. Do not invent a story about teammates from kill feed alone.

Circle anything that appears three times. That is the review. A list of 25 unique mistakes is a diary. “Died wide on A ramp without a trade, four times” is a project. FACEIT ELO usually stalls on the project, not the diary.

One or two rows is a week of practice. Ten rows is a document you will ignore.

A second opinion helps when you keep writing “lost aim” and the pattern is still there, or when you want a shorter list than you will write yourself. Submit the demo on CS2 demo review. If you want those notes practiced on a call, follow with coaching. Neither is required to use the method above.

After you have a pattern, the work is in the next queue, not in a longer document. Use how to improve FACEIT ELO to turn the row into a loop. The review does not add ELO. The next week of cleaner deaths might.