Most "best browser games" lists are written by people testing on fast machines. If you are on an eight-year-old laptop, a school computer, or a Chromebook that cost less than a pair of shoes, half those recommendations will stutter or refuse to start.

This is a list for that machine, plus a way to tell in advance which games will be fine.

How to tell before you click

Three signals, in order of usefulness.

Does it look 3D? Anything rendering in three dimensions is using WebGL and your graphics hardware. On integrated graphics from before roughly 2016, expect problems. That covers racing games, most modern arcade titles, and anything with lighting effects.

Is the art flat and geometric? Games drawn with simple shapes and solid colours are almost always 2D canvas or plain HTML, which any machine from the last fifteen years handles without noticing.

Does it have a lot happening at once? Particle effects, dozens of moving enemies, and continuously scrolling backgrounds all cost frames. A game where one thing moves at a time will run anywhere.

The safest games here

These are drawn with plain HTML elements or simple 2D canvas. They will run on essentially anything with a browser.

2048 — the tiles are HTML divs. There is no rendering engine at all. It will run on a machine that struggles with the browser itself.

Sudoku and Minesweeper — a grid, some numbers, nothing animating. Both are essentially free to run, and both are untimed, so even if your machine does hiccup it costs you nothing.

Chess — turn-based with drag-and-drop pieces. Nothing moves unless you move it.

Asteroids — this one surprises people. It looks like it should be demanding, but it is thin white vector lines on a plain background, written in dependency-free JavaScript. It is one of the lightest genuinely-fun games on this site.

Invaders — pure HTML, CSS and JavaScript with no libraries. Loads instantly and stays at full speed.

Approach with caution on old hardware

Not bad games — just demanding ones.

HexGL is the heaviest thing here. It is a full 3D racer running in WebGL, and it is glorious on capable hardware and unplayable without it. It has quality settings; drop them before assuming it will not work.

Cuberun and other 3D runners are the same story — beautiful, and reliant on your graphics hardware.

Anything described as 3D in its category tag is worth treating the same way.

Things that help regardless of the game

Close the other tabs. This is not the cliché advice it sounds like. Every open tab holds memory, and on a machine with 4GB the browser starts swapping to disk, which affects everything. A game that stutters with twenty tabs open often runs perfectly with two.

Use fullscreen. Rendering to a smaller area is less work. Counter-intuitively, fullscreen on a low-resolution screen is often faster than a window on a high-resolution one, because the total pixel count is what matters.

Check for hardware acceleration. In Chrome, chrome://gpu will tell you whether the browser is using your graphics hardware or falling back to software rendering. If it says software, 3D games will crawl no matter what you do — and turning acceleration on in settings sometimes fixes it outright.

Avoid running on battery saver. Most laptops throttle the CPU substantially in power-saving mode. Plugging in can genuinely double your frame rate.

Why browser games are a good fit for old machines anyway

There is an upside to all this. A browser game cannot demand a 40GB install, cannot leave background updaters running, and cannot fill your drive. When you close the tab, it is gone.

For a machine that is short on storage and short on patience, that is a better deal than anything you would install — and the games on this list have not needed a fast computer at any point in the twenty years some of them have existed.