Three routes, and the requirements nobody mentions
There are three ways to get Counter-Strike 1.6 running on a Chromebook, and two of them depend on hardware and permissions your device may not have. Steam for Chromebook needs a fairly capable machine, the Linux container needs a setting a managed device usually blocks, and the browser needs neither. Which route applies to you is worth establishing before you spend an evening on the wrong one.
Play now — free, no downloadBrowse serversGoogle publishes a minimum spec for Steam for Chromebook (Beta): at least an Intel i3 or Ryzen 3 processor, 8GB of RAM, and 128GB of storage. Their own check is simple — search your launcher for "Steam installer", and if it does not appear, your device does not meet the requirements for the beta.
A lot of Chromebooks sold for schools and for budget buyers sit below that line, particularly on memory and storage. That is not a fault in the device; those machines were built for web work, which is exactly what they are good at.
The other native route is the Linux development environment, which runs a container you can install a Linux build into. It works well on capable hardware and it is the route most written guides assume.
On a managed Chromebook, the one issued by a school or an employer, Linux is usually switched off by administrator policy, and there is no user-side setting to re-enable it. That is the intended behaviour of a managed device rather than a problem to be solved, and it is why so many step-by-step guides simply stop working at step one for the people most likely to be reading them.
The page currently ranking first for this question is a forty-four-word note that says to install Steam for ChromeOS or the Linux version, open the Steam library, and copy some files into a folder. It is accurate for a machine that meets the spec above. It says nothing about what to do if yours does not, which is the situation most people asking the question are in.
The rest of that results page is video tutorials, a thread about a different game, and download sites. There is very little written for the case where the native routes are unavailable.
Counter-Strike 1.6 also runs as a web page, compiled to WebAssembly, which asks nothing of ChromeOS beyond a current browser. There is no installer, no Linux container, no developer mode and no administrator permission involved, because from the device's point of view you are visiting a website.
That makes it the route that works on the hardware the other two exclude. A mouse makes an enormous difference and a trackpad is a real handicap in a shooter, so bring one if you can.
Memory is the real constraint on cheap hardware. A 4GB Chromebook running a browser game alongside a dozen tabs will struggle, and closing the tabs genuinely helps. This is the same limit the native routes hit, arriving from a different direction.
The other limit is the network rather than the device. A school or office connection decides for itself what it will let you reach, and that is between you and whoever runs it. If the site is blocked on your network, that is a decision made by its administrator, and working around it is not something this guide will help with.