html5explorationbrowser technology

How HTML5 Opened Up Exploration Games

Kaito NakamuraBy Kaito Nakamura

Of all the genres that moved into the browser, exploration had the furthest to travel. A platformer needs precise input and a flat plane. An exploration game needs a world — geometry, distance, a camera you control, and enough performance to make moving through it feel like moving rather than like waiting.

For most of the web's history that was not on offer. It is now, and the reasons are worth knowing if you want to understand why the browser catalogue looks the way it does.

What the plugin era could and could not do

Flash was extremely good at two-dimensional animation and vector art, and a generation of browser classics came out of it. What it was not built for was 3D space. Later versions bolted on hardware-accelerated 3D, but by then the plugin model itself was failing — a separate runtime, a separate security surface, a separate update cycle, and no presence at all on the phones that were rapidly becoming most people's computers.

So browser exploration games in that era were mostly top-down or side-on, and the "world" was a set of screens rather than a continuous space. That is a real constraint on a genre whose whole appeal is continuity — the sense that over there connects to here.

The three pieces that changed it

WebGL gave JavaScript direct access to the graphics hardware. That is the big one. A browser game could suddenly draw real 3D geometry at a real framerate without a plugin, using the same GPU everything else on the machine was using.

JavaScript engines got dramatically faster, and then WebAssembly arrived and made it possible to run code compiled from other languages at close to native speed. That matters for exploration specifically, because open spaces are expensive in ways a puzzle grid is not: collision detection, streaming terrain, keeping track of what is where.

Engines started exporting to the web as a first-class target. This is the least glamorous piece and possibly the most important. Once a developer could build in a familiar engine and publish to a browser without rewriting anything, the number of people capable of making a browser exploration game went up by orders of magnitude.

What that produced

You can see the result directly in what the catalogue contains. Space Rover pilots a six-wheeled rover across different terrain in 3D — a game that is fundamentally about how ground feels under a vehicle, which is not a thing you could ship in a browser in 2010. Wild Island Quest runs the gather-and-build loop on a remote island where resources are scarce, which needs persistent world state rather than a series of screens.

Neither of these is a hundred-hour epic, and that is the honest part of the story.

The constraint that has not gone away

Download size. A browser game has to start almost immediately or the visitor leaves, and that puts a hard ceiling on how much world you can ship. No amount of GPU access changes the fact that someone on a phone connection will not wait ninety seconds for terrain.

This is why browser exploration games are compact rather than vast, and why the good ones lean on density instead of scale: a small world with a lot in it, rather than a large one with a little. It is a genuine design discipline, and arguably it produces better exploration than open worlds where most of the map is travel time.

It is also why procedural generation is so common here — a world described by an algorithm costs almost nothing to ship compared with one described by files.

Where it goes next

WebGPU is the successor to WebGL and gives browser games access to the kind of graphics techniques desktop engines have used for years. It is arriving gradually across browsers rather than all at once, which is the normal shape of these things. The realistic near-term effect is not vastly bigger worlds — the download ceiling still applies — but better-looking ones at the same size.

If you want to see where the genre has got to, the platform adventures collection is the short answer, since that is where our exploration games ended up. For worlds you have to survive rather than just wander, survival adventures apply the same technology to a harsher brief.

Kaito Nakamura

Written by

Kaito Nakamura

Web Developer · Tokyo, Japan