netart-extinction: A Timeline of How Digital Art Goes Extinct


Actual Net Art Extinction timeline
Net Art Extinction timeline, 5 November 2026. Marc Schütze. CC BY 4.0. Source

Digital art rarely dies on its own. It dies because something underneath it changes. A plugin reaches end-of-life, an API is switched off, a browser drops a feature, and the work that depended on it stops running.

I kept running into this while restoring works at ZKM. Eden.Garden renders through the Pulse 3D plugin, and Pulse 3D has been defunct for two decades. Many other works have the same problem, and I wanted to see all of it. So I built netart-extinction, a public timeline of the dependency changes that break digital art.

Events and artworks

The site models two things and the relationship between them. Events are dependency changes: “Flash Player blocked”, “Firefox removes the <blink> tag”, “Google AJAX/Search APIs discontinued”, “GeoCities shut down”. Artworks are the works those events hit. Each event lists the pieces it affected, with a severity per work and a status (dead, degraded, restored, unknown), and the fix or workaround where one exists.

It currently holds 128 events, from äda’web losing its funding in 1998 up to the present. They are mapped against a catalogue of more than eleven thousand artworks from the archives that track this: Rhizome’s ArtBase, Whitney Artport, Ars Electronica, LIMA, NTT ICC in Tokyo, the Archive of Digital Art, and Turbulence via the Wayback Machine. A D3 timeline lets you scroll through it and see where the breakages cluster: the plugin extinctions of the early 2000s, the long end of Flash, the API sunsets of the 2010s.

Why group by cause

If a work breaks because a browser removed a feature, preserving the work means accounting for that feature. The same dependency usually took out a dozen other pieces at the same time. Grouping them by cause instead of by artist shows that.

netart-extinction maps what goes wrong. The tools I build alongside it, the exhibition VM controller and the wayback cache proxy, keep specific works running against these changes. Eden.Garden is the counter-example: a 2001 work whose core dependency is on the timeline as extinct, brought back and kept exhibitable.

Open and citable

It is an Astro static site with a client-side D3 timeline, open source under MIT (code) and CC BY 4.0 (content), with a Zenodo DOI so it can be cited in the conservation literature. Contributions of events and affected works are welcome. Live at extinction.zkm.de.