CS2 Wallhack Commands: See Players Through Walls Legally
The console commands that still work for a legal wallhack in CS2, how to turn them on with sv_cheats, X-ray in demos without cheats, binds, and the commands that no longer exist
When people hear "wallhack" or "wh" in Counter-Strike, they think of cheating. But Counter-Strike 2 has built-in ways to see players through walls for practice, testing, map study or just for fun, and none of them needs any third-party software.
In this guide I show the wallhack commands that work in CS2 right now, how to enable them, how to get an X-ray view in demos without sv_cheats, and which popular commands from old guides are gone. One of them, cl_player_proximity_debug, was removed from the game in April 2026, so a lot of guides on the internet are out of date.
What Is a Legal Wallhack in CS2
A legal wallhack in CS2 means using the game's own console commands to see players through walls, without installing cheats and without any VAC risk. These are developer and spectator tools that Valve left in the game for testing and for watching matches.
What you can use it for:
- see how bots or friends rotate behind walls and learn the usual paths;
- practice utility and timings and see where players really are when your smoke lands;
- check off-angles and how much of a player shows from a spot;
- review your own demos and see what the enemy was doing;
- record content or set up custom training with friends.
Orange boxes around players and objects, visible through walls. Needs sv_cheats 1.
X-ray outlines and names through walls in demos and as a spectator. No cheats needed.
Removed in April 2026. Doesn't exist in CS2 anymore.
How to Enable Wallhack in CS2 (sv_cheats 1)
You don't need any programs, file edits or disabled Steam services. Everything is already in the game:
- Turn on the developer console: Settings β Game β Enable Developer Console β Yes.
-
Start a local match:
Play
β
Practice
β
With Bots
, or type
map de_dust2in the console. Workshop maps and your own server work too. - Open the console with ~ and enable cheats.
- Enter the wallhack command.
sv_cheats 1 cl_ent_bbox *
sv_cheats 1 only works where you are the host. On official servers it's locked, so these commands simply don't run there. If you want a full practice setup with bots, my CS2 bots guide and bot difficulty guide cover the commands.
cl_ent_bbox: The CS2 Wallhack Command That Works
Since cl_player_proximity_debug is gone, cl_ent_bbox is the main wallhack command in CS2. It draws the movement bounding box of an entity in orange, and the box is visible through walls, smokes and thin cover. Players, weapons, grenades, even chickens.
cl_ent_bbox // box on the entity you aim at cl_ent_bbox 482 // box on one entity by its index cl_ent_bbox * // boxes on all entities, enter again to remove cl_ent_clear_debug_overlays // removes all boxes
| Command | What it does |
|---|---|
cl_ent_bbox |
Box on the entity under your crosshair: a bot, a dropped weapon, a chicken |
cl_ent_bbox # |
Box on one entity by its index number |
cl_ent_bbox * |
Boxes on everything on the map, enter it again to turn them off |
cl_ent_clear_debug_overlays |
Removes every debug overlay at once |
With cl_ent_bbox * the screen fills up fast, every weapon and prop gets a box too. It feels more like a debug view than a clean wallhack. If you only want the players, box them one by one.
How to Find a Player's Entity Index
Turn on developer mode: add -dev to your launch options or type developer 1 in the console. After that, cl_ent_bbox prints the class name and index of each entity it marks, for example class='C_CSPlayerPawn', index='482'.
Look for C_CSPlayerPawn, those are the players. Then run cl_ent_bbox with that number for each of them, and you get boxes only on players, no clutter.
X-Ray Wallhack in CS2 Demos Without sv_cheats
There's one more legal way to see players through walls, and it doesn't need cheats at all: the spectator X-ray. The game describes spec_show_xray like this: with 1, you see player outlines and name IDs through walls, and who you see depends on your team and the mode.
spec_show_xray 1 // X-ray on (default) spec_show_xray 0 // X-ray off
Where it works:
-
Demos.
Open your match in
Watch
or with
playdemo, and you see all players through walls. The best way to understand what the enemy did in a round you lost. - GOTV and spectating. As a spectator you see players through walls according to the server's rules.
It's on by default (spec_show_xray 1), so if you don't see outlines in a demo, check that nobody turned it off in your config.
Wallhack Bind for CS2 Practice
Typing commands every time gets old. Two keys are enough for practice: one turns the boxes on and off, the other clears everything.
bind "F6" "sv_cheats 1; cl_ent_bbox *" bind "F7" "cl_ent_clear_debug_overlays"
Put these lines in your practice config or autoexec. They do nothing on official servers, so they're safe to keep. How binds work in general: CS2 bind tutorial. More ready-made toggles are in legal wallhack scripts.
Wallhack Commands That No Longer Work in CS2
cl_player_proximity_debug (removed in April 2026)
For a long time this was the best legal wallhack in CS2: with cl_player_proximity_debug 1 enemies got small numbers near their legs, and the numbers stayed visible through walls. Clean, light, almost like a real wallhack.
Valve removed it in the CS2 update of April 2026 (build 2000791): the command is gone from the game files, so the console just won't find it. If an old guide or script tells you to use it, that guide is out of date. Use cl_ent_bbox or demo X-ray instead.
r_drawothermodels
The classic CS:GO wallhack command from the old Source engine. It doesn't exist in Source 2 and does nothing in CS2.
cl_physics_highlight_active
In the early CS2 beta in 2023 this command gave a wallhack effect even without cheats. Valve fixed it right away, now it's a developer-only command that players can't use.
Can You Get VAC Banned for Wallhack Commands?
No. These are official commands that are part of the game. cl_ent_bbox only works with sv_cheats 1, so it only runs in your offline matches, on workshop maps and on servers you control. On official servers cheats are locked, and the console only tells you that the command needs cheats.
X-ray in demos and as a spectator is a normal spectator feature, nothing to worry about there either.
The only real risk is third-party software. Anything that promises a wallhack in matchmaking is a cheat, and it gets you banned.
Conclusion
A legal wallhack in CS2 is a training tool, not a cheat. Right now you have two of them: cl_ent_bbox with sv_cheats 1 in your own matches, and X-ray in demos and as a spectator without any cheats. cl_player_proximity_debug is gone since April 2026, so don't waste time on it. Use these tools to learn rotations, timings and angles, and the knowledge stays with you in real matches.
CS2 Wallhack Commands FAQ
What is the wallhack command in CS2?
cl_ent_bbox * after sv_cheats 1. It draws orange boxes around players and objects that you see through walls. It only works in your own matches and on servers you control.
Does cl_player_proximity_debug still work?
No. It was removed from CS2 in the April 2026 update and isn't in the game anymore. Use cl_ent_bbox or X-ray in demos.
Can I use wallhack commands in matchmaking?
You can type them, nobody stops you. But they won't work: they need sv_cheats 1, and on official servers it's locked. The console just says the command needs cheats, and that's it.
Will I get VAC banned for cl_ent_bbox?
No. It's an official game command, not third-party software. VAC doesn't care about console commands.
How do I see players through walls without sv_cheats?
Watch a demo or spectate: spec_show_xray 1 (on by default) shows player outlines and names through walls.
Does r_drawothermodels 2 work in CS2?
No. It's an old Source engine command that doesn't exist in Source 2.
Can I use these commands on community servers?
Only if the admin has enabled sv_cheats 1, which almost never happens. Your own server or a local match is the way to go.
How do I remove the boxes?
Enter cl_ent_bbox * again or use cl_ent_clear_debug_overlays.

