A CS2 bug is any behaviour that clearly goes against how the game is meant to work. Think of a crash, a missing sound, a wall you can see through, or a grenade that passes through solid geometry. Valve fixes bugs through regular updates, and good player reports help them find problems faster. This guide explains how to check that a bug is real, how to write a report that developers can use, and what usually happens next.
Is it a CS2 bug or your setup?
Many problems that look like game bugs come from local settings. Rule these out first.
- Update everything. Make sure CS2, Steam and your graphics driver are current.
- Verify the game files. In your Steam Library, open the game's Properties, go to Installed Files and verify their integrity.
- Remove extras. Turn off overlays and remove unusual launch options. Our launch options guide lists the common ones.
- Reset configs. Temporarily move your autoexec and custom configs. See our guide on restoring your CS2 config after an update.
- Try to repeat it. If you can make the problem happen again on purpose, it is much easier to report.
What should a good bug report include?
Developers handle huge numbers of reports. The ones that get fixed fastest are easy to understand and easy to reproduce. Valve's public GitHub tracker asks for the same core details, so they are a good model.
| Part | What to write |
|---|---|
| Title | Short and specific, such as "Footsteps silent on one staircase on a named map" |
| Steps | Numbered steps that make the bug happen |
| Expected | What should happen |
| Actual | What happens instead |
| System info | From Steam, using Help, then System Information |
| Evidence | A short clip, screenshot, demo tick or crash details |
Keep one issue per report. Write in plain English, and stay polite. All-caps rants and repeated "still broken" comments do not speed anything up.
Crashes need extra detail
For a crash, note exactly what you were doing when it happened. Was it on loading a map, opening a menu or during a round? Include any crash ID or dump file the game creates, and say whether it happens every time. A list of hardware alone rarely helps. The steps that trigger the crash matter most.
Use demos and clips
A demo lets you show the exact moment a bug happened. Our CS2 demos guide explains how to find and replay matches. A ten-second clip of the bug is often enough on its own.
Where to report a CS2 bug
- Valve's GitHub tracker. Valve runs a public tracker,
csgo-osx-linux. Its name points to Linux and macOS, and its README still names CS:GO, so read it before posting to see whether your issue fits. It asks you to search existing issues first and add a thumbs-up instead of a duplicate. - Steam community discussions. The game's Steam discussion boards are a common place to share bugs and check whether others see the same thing.
- Community reports. Well-made videos and posts often reach developers too. Credit and clear steps help them spread.
Check each channel's own rules before you post, because they can change.
Bugs, cheats and exploits are different
If you think a player is cheating, report them in game instead. Our guide on how to report a cheater in CS2 covers that process, and the Overwatch guide explains how reports are reviewed. If you find an exploit that gives an unfair advantage, do not spread it in public. Report it privately with clear steps so it can be fixed before it is abused.
What happens after you report?
Do not expect a personal reply. Developers usually group similar reports, reproduce the problem and fix it in a future update. The fix then shows up in the patch notes, sometimes as a single line. Big issues can be fixed within days. Rare or complex ones can take much longer.
After each update, run through our CS2 patch checklist and retest your bug. If it is fixed, great. If not, add new details to your existing report rather than starting a fresh one.
Sources and checks
Reporting guidance was checked on 1 November 2026 against the README of Valve's csgo-osx-linux tracker on GitHub. Fixes are announced in the patch notes on counter-strike.net.
Frequently asked questions
How do I report a CS2 bug?
Rule out your own setup, then write a short report with steps to reproduce, what you expected, what happened, your Steam system information and a clip if possible.
Will Valve reply to my bug report?
Usually not directly. Fixes appear in later patch notes, so watch those and retest after each update.
Is a cheater a bug I should report?
No. Report suspected cheaters through the in-game report system. Bug reports are for problems with the game itself.
