The browser as a games platform: its runtimes, and what happened when they were switched off.

02 Runtimes

Shockwave

The heavier sibling that arrived first and handled the work the lighter runtime could not.

RuntimesEntry 2 of 6Every entry is one runtime, and what it took with it.

A shelf of 1990s software boxes and manuals photographed square-on in daylight, spines facing out

Director shipped on disc first and on the web second, which is why it never reached Flash’s install base.

oujouer.com collection

The runtime that had to carry weight

Macromedia Shockwave arrived in 1995, roughly a year before Flash, and it carried something that Flash, at the time, could not: content built in Director, Macromedia's full authoring environment for multimedia CD-ROMs. Director had been the professional tool of choice since the late 1980s, and Shockwave was simply Director's output delivered through a browser plugin rather than pressed onto a disc.

1989First dated event
2019Last dated event
30Years spanned
5Dated entries below

That origin shaped everything. A Shockwave file was a compressed Director movie — a .dcr — and it could contain 3D scenes, scripted physics and Lingo, Director's own object-oriented scripting language. This made Shockwave capable of genuinely complex games years before the lighter plugin caught up: isometric strategy titles, physics puzzlers and early 3D shooters all ran in Shockwave during the late 1990s. The portals that carried them — including Shockwave.com, which Macromedia launched as a dedicated destination — treated the format as a premium tier.

A stack of 1990s software manuals and ring binders on a desk beside an older computer, daylight from a side window

The manuals outlasted the plugin. Documentation is often the last part of a runtime still legible.

oujouer.com collection

When Adobe acquired Macromedia in 2005, it inherited both runtimes. Flash had by then overtaken Shockwave in reach and developer mindshare, and Adobe's investment followed that momentum. Shockwave continued receiving updates but never converged with the Flash toolchain; the two remained architecturally separate products built on different authoring environments.

A desktop monitor in a dim room showing a simple animated interface mid-load, a mouse and mousemat in front of it

The preloader was the only moment the platform showed itself to the player.

oujouer.com collection

The end, when it came, was abrupt compared with Flash's three-year runway. Adobe announced in 2019 that Shockwave for Windows would be discontinued, effective immediately, and offered no extended support period. The macOS player had already been dropped years earlier. Because Shockwave never saw the kind of organised preservation effort that Flash attracted, the loss was quieter but arguably sharper: the Ruffle project targets Flash's ActionScript runtime, not Director's Lingo engine, and no equivalent open-source reimplementation exists for Shockwave. The Internet Archive holds some Shockwave titles, but playability depends on a functioning Windows installation of the now-unavailable plugin — a dependence that, without emulating the runtime rather than the game, only deepens with time.

The portals that carried them — including Shockwave.com, which Macromedia launched as a dedicated destination — treated the format as a premium tier.

An unopened software installation disc still in its paper sleeve on a desk

Distributed, installed, withdrawn — the disc outlived the software’s reach.

oujouer.com collection

Also in Runtimes

The layer between the game and the browser.