What to check when a CS2 demo will not open
Find the failing stage before retrying a download, upload or analysis request.
Quick answer
Identify the failing stage first: account history, demo download, local upload, analysis or playback. Check the connected identity, source availability, complete file and supported format. Keep the match link and exact error if a complete supported demo still fails; repeated unchanged uploads may only use your allowance.
Jump to a section
Before you start
- Keep the match link and the exact visible error.
- Check whether the replay file exists before troubleshooting playback.
- An old match record does not guarantee a downloadable demo.
Find the stage that failed
Start with what you can actually see. Is the match missing from your account? Is its demo download unavailable? Was a local upload rejected? Or did processing fail after the file arrived? Each case needs a different fix. Treating every issue as a playback problem leads to repeated uploads without changing the cause.
Write down the match date, map and source alongside the error. If another match opens, compare its source and format with the failing one. That is a useful way to narrow the issue without changing your account setup unnecessarily.
No match row
Check the connected account, platform and match details. For Steam, check the match-sharing setup.
No demo file
Try the original match room or your saved local copy. Missing source data must be resolved before analysis.
Upload rejected
Check the extension, complete download, file size and current upload allowance.
Analysis failed
Keep the accepted file and exact processing error for Support. Repeating an unchanged submission may fail in the same way.
Check the file rather than its name
A .dem name can hide an incomplete transfer, a web error page or data from the wrong game. Download again from the original source if the transfer was interrupted. If the file arrived inside .gz, .bz2 or .zip, extract it before uploading; .dem.zst is supported directly.
Renaming an MP4 or an old CS:GO replay to .dem does not convert it into CS2 match data. Keep the original file and make any diagnostic copy separately so you do not lose the only replay you have.
Check source availability and processing
For FACEIT, open the correct match room and check whether its demo is available there. If the source no longer provides it, a reconnect or a new Flashback account cannot restore the file. If you saved the demo earlier, the local upload route can still be useful.
An accepted download may still need analysis before a replay opens. Follow the state shown in Flashback and avoid repeatedly submitting the same request. There is no universal processing time: file size, queue state and the match data can affect the job.
Send a report that can be investigated
Include the match URL or identifier, map, approximate date, source platform, file extension and exact error. Say whether the failure happened before upload, during processing or while opening an analysed replay. If a different match works, include that observation too.
Use the Support route rather than placing account authentication codes in a public discussion. A concise report with a reproducible failing step gives the team something concrete to investigate. Keep the demo until the investigation is complete if it is your only copy.
Common questions
Can match statistics recreate a lost demo?
No. Statistics do not contain the full replay data needed to reconstruct every player's movement and events.
Should I upload the same failing file again?
First identify what changed. If the file and visible error are unchanged, another upload may repeat the same failure and use your allowance.
Put the guide to work
The failing stage identified with a useful next step. Open the tool when you are ready, or follow a related guide below.