02 Runtimes
Unity Web Player
A plugin that brought a full 3D engine into the page, and was deprecated once the browsers closed the plugin interface.
A full 3D engine inside a page, on the condition that the visitor agreed to install something first.
oujouer.com collection
A full engine in a tab
Before WebGL was reliable enough to carry a real-time 3D scene, Unity Technologies shipped a browser plugin that did what no scripted page could manage on its own: it ran a compiled game engine inside a tab, handling physics, lighting, shaders and audio through a native binary that the browser loaded on demand. The Unity Web Player arrived around 2009 and for a few years it was the only credible way to put a three-dimensional interactive world on a public webpage without asking the user to download and install a standalone executable.
The mechanism was the same one that made Flash and Shockwave possible — a plugin interface baked into the browser that let a third-party binary register itself as the handler for a particular MIME type. When a page embedded a .unity3d file, the browser handed control of that rectangle to the plugin, which spun up a full Unity runtime: scripting, rendering, collision detection and all. From the player's point of view it was seamless, or nearly so. In practice there was a download of several megabytes before anything appeared, and on slower connections the experience could feel closer to installing software than loading a page.
The manuals outlasted the plugin. Documentation is often the last part of a runtime still legible.
oujouer.com collection
What the Web Player offered that Flash could not was genuine 3D. Flash eventually gained limited 3D capabilities through Stage3D, but Unity's renderer was built from the start around a scene graph with real geometry, real-time shadows and a physics engine derived from the same tools studios used for commercial releases. Developers who already knew Unity's desktop workflow could target the browser with relatively little friction, which made the plugin attractive to both indie developers and institutional clients building product configurators, architectural walkthroughs and educational simulations.
Director shipped on disc first and on the web second, which is why it never reached Flash’s install base.
oujouer.com collection
When the browsers closed the door
The plugin's lifespan was structurally determined by decisions made elsewhere. Google announced in 2013 that Chrome would stop supporting the Netscape Plugin Application Programming Interface — NPAPI, the interface that made all such plugins possible — and began enforcing that removal in 2015. Firefox and other browsers followed. Without NPAPI there was no mechanism to load a native binary into a page, and Unity Technologies deprecated the Web Player in 2015, pointing developers toward WebGL builds as the replacement.
What the Web Player offered that Flash could not was genuine 3D.
WebGL, standardised by the Khronos Group, gave browsers a low-level graphics interface that a JavaScript engine could call directly without a plugin. Unity already supported WebGL export, and the transition was real enough that most projects targeting browsers after 2016 used it. But WebGL builds are not runtime-identical to Web Player builds: they compile to JavaScript or WebAssembly, they run inside the browser's own sandbox, and they impose different memory and performance constraints. Games built specifically for the Web Player and never ported are simply gone from their original context.
The preservation situation is worse than it is for Flash, where the Ruffle project has produced an open-source reimplementation capable of running a large fraction of the existing catalogue in a modern browser without plugins. No equivalent exists for the Unity Web Player. Emulating the native binary requires either a period browser in a virtual machine — with all the configuration overhead that implies — or a preserved copy of the player itself running under controlled conditions. The Internet Archive has documented some Web Player content, but playback at scale remains unsolved. BlueMaxima's Flashpoint, which built its preservation model around bundling the runtime alongside the content, has limited Unity Web Player support, but the catalogue coverage is thin compared with its Flash holdings.
The preloader was the only moment the platform showed itself to the player.
oujouer.com collection
The practical result is a dead zone in browser game history roughly coinciding with the years 2010 to 2015, when 3D content was actively being made for the web and the plugin was the only way to experience it. A Unity .unity3d file is not corrupted or lost in the way that bit rot destroys physical media; the files exist on servers and in archives, but nothing in a current browser can run them. The runtime was closed, the plugin interface was removed, and the games are stranded inside containers the web no longer knows how to open.