I built the first version of this site on a Chromebook, so I have spent more hours than I would like working out what these machines can and cannot do. The short answer is that they are much better at browser games than their reputation suggests, and much worse at anything else. Here is how to get the most out of one.
Why a Chromebook cannot install games
Chrome OS is not Windows or macOS. It was designed around the browser, and it does not run Windows executables at all. There is no .exe to double-click, no Steam client in the way you would recognise it, and on most managed devices the Play Store and Linux support are switched off by whoever owns the machine.
That sounds limiting, and for installed games it is. But it says nothing about what the browser itself can do, and the browser on a modern Chromebook is the same Chrome you would find on any other machine. Anything that runs in a tab runs here.
What actually runs well
Every game on Classroom Connect is HTML5 or WebGL, which means it runs in the browser using standards Chrome OS supports natively. No plugin, no install, no admin rights. In practice the performance splits along fairly predictable lines.
- Excellent: 2D games, puzzle games, clickers and idle games, retro ports, anything Flash-era running through Ruffle
- Good: most .io games, side-scrolling platformers, arcade racers, physics games
- Variable: Unity WebGL games - some are fine, some will drop frames on an entry-level machine
- Struggles: large 3D survival and sandbox games, and anything with a big open world
If you have a mid-range or newer Chromebook, most of the library will run at full speed. If yours is an entry-level model a few years old, stick to the first two groups and you will barely notice a difference from a desktop.
Five things that measurably help
Chromebooks usually have modest memory, and browser games compete with everything else you have open. These are the changes worth making, roughly in order of how much they help.
- Close other tabs. This is the big one. A dozen open tabs can halve the frame rate of a WebGL game, and closing them costs nothing.
- Check hardware acceleration is on. Go to chrome://settings/system and make sure 'Use graphics acceleration when available' is enabled. Without it, WebGL games fall back to software rendering and become unplayable.
- Use fullscreen. Every game page here has a fullscreen control. Rendering to a smaller area is less work, but fullscreen also removes the page around it from the compositing job.
- Restart Chrome occasionally. Chrome OS is good at memory management but not perfect, and a browser that has been open for days will be slower than one that has not.
- Lower the in-game settings first. Most Unity games have a quality setting in their own menu. Dropping it one notch usually costs very little visually and gains a lot of frames.
If a 3D game runs badly, check hardware acceleration before you blame the machine. It is switched off more often than you would think, and turning it on is the single biggest difference you can make.
Where to start
If you want things that will run flawlessly on any Chromebook, the puzzle and idle categories are entirely safe, and so is almost everything from the Flash era. Bloxorz, 2048 and Cookie Clicker will run on anything with a screen.
For something more demanding that still behaves itself, Slope, Moto X3M and the Run series are all built lightly enough to hold a steady frame rate on modest hardware. Drift Hunters is the usual test case for whether a Chromebook can handle proper WebGL, and on most machines from the last few years it can.
The honest limitation
A Chromebook will not play a modern PC game, and no amount of settings tweaking changes that. What it will do is run several hundred browser games well, start them in seconds, and never ask you to install anything. For a machine that often costs less than a games controller, that is a reasonable trade.
