When Pixels Decay and Code Stalls

Digital bit rot is the gradual loss of reliable access to digital information as files, storage media, software, operating systems, networks, and hardware become damaged, unsupported, or impossible to connect. In a museum, the problem is more complicated than a corrupted file. A software-based artwork may continue to exist on a hard drive while its operating system no longer runs, its graphics library has disappeared, or its display device produces a visibly different image. The work is present in storage, yet absent as an experience.

This creates a sharp contrast with conventional conservation. A marble sculpture can be stabilized, a canvas can be cleaned, and the materials themselves remain broadly intelligible across generations. Software-based art depends on a layered system that changes continuously. Its meaning may be carried by timing, interface behavior, screen characteristics, sound, network communication, or the relationship between code and a particular machine. As digital vulnerability guidance makes clear, preservation therefore requires more than locked storage. It requires active, pragmatic stewardship that monitors dependencies, tests access, and plans for controlled change.

The Fragile Stack of Modern Media Installations

A contemporary media installation is best understood as a stack of dependencies rather than a single object. At the bottom may be a power supply, motherboard, graphics card, monitor, projector, sensor, or custom microcontroller. Above that sits firmware, an operating system, drivers, runtime libraries, and perhaps a proprietary graphics framework. The artwork itself may rely on source code, databases, configuration files, external services, or a specific sequence of inputs. A failure at any layer can alter or prevent the work”s operation.

The physical interfaces are particularly easy to underestimate. A computer may still boot, but its original serial port, video connector, audio output, or controller may no longer be available on replacement equipment. Bespoke microcontrollers can be difficult to reproduce when their programming tools disappear or their chips are no longer manufactured. Even a seemingly minor substitution, such as changing a graphics driver, can affect color, frame rate, typography, input response, or the timing of an interactive piece.

Display equipment can carry significance beyond its functional role. A CRT monitor may produce scan lines, curvature, phosphor behavior, and motion characteristics that are part of the artwork”s visual identity. A modern flat panel may display the same pixels while changing the work”s texture and historical meaning. Tate”s conservation research emphasizes that display devices can have aesthetic, historical, conceptual, or authenticating value. The central question is not simply whether a replacement works, but whether it preserves the characteristics that matter.

• Operating system dependency: An application may require a discontinued operating system, obsolete permissions model, or unavailable system library.
• Software dependency: Proprietary codecs, graphics frameworks, plug-ins, and development environments may be difficult to reinstall or license.
• Hardware dependency: Ports, processors, controllers, sensors, and display technologies may no longer be manufactured.
• Environmental dependency: Temperature, network access, latency, room acoustics, and light levels can affect the intended experience.
• Knowledge dependency: The work may rely on undocumented installation procedures known only to the artist or original technician.

Software art can degrade faster than an oil painting because its preservation target is active behavior. A painting can remain legible even when its frame is replaced. A software work can become inaccessible after a routine security update, a cloud service closure, or the loss of a single library. The difficulty is compounded by institutional obsolescence: a format or device may still function somewhere, but not within the museum”s available technical environment. Conservation teams must consequently treat hardware and software as interdependent organisms rather than static objects.

Evaluating Practical Conservation Pathways

No single preservation strategy suits every work. Virtualization packages an original software environment so it can run on contemporary hardware, while emulation recreates the behavior of an older hardware or operating-system environment. Hardware scavenging preserves original machines or gathers replacement parts from a shrinking supply. Code refactoring changes the software so it can operate in a maintained environment. Each approach can protect certain aspects of a work while weakening others.

Approach	Primary strength	Main limitation	Best use
Virtualization	Captures a runnable software environment	May not reproduce unusual hardware behavior	Works dependent on standard computers and operating systems
Emulation	Can preserve original behavior and interfaces	Requires testing, expertise, and continued maintenance	Complex or historically significant software environments
Hardware scavenging	Maintains original physical characteristics	Parts fail and technical knowledge disappears	Works whose display or input hardware is artistically significant
Code refactoring	Reduces dependence on obsolete components	May change behavior, timing, or visual output	Projects with accessible source code and replaceable technology

The key difference is between preserving content and preserving behavior. A disk image may retain every original file, but it does not guarantee that the program will display correctly. Emulation can preserve access to original files and interactions, yet it introduces a new technical layer that must itself be documented and monitored. The Digital Preservation Coalition notes that emulation is especially useful for complex objects, but it requires expertise, maintenance, and attention to software licensing.

Before making a decision, conservators should identify the artwork”s significant properties. These may include resolution, frame rate, latency, color behavior, sound synchronization, physical visibility of equipment, user interaction, or the possibility of failure as part of the work. If a specific CRT, game console, sensor, or printer is visibly and conceptually important, physical maintenance should remain a priority. If the device is merely a hidden computational tool and the artist accepts substitution, virtualization or emulation may offer a more sustainable route. Artist interviews and installation histories are essential because technical equivalence cannot be decided by specifications alone.

Field Lessons from Contemporary Preservation Labs

Modern institutions increasingly combine documentation with technical intervention. Tate”s software-based art preservation work, developed through collaboration between collection care specialists and research partners, focuses on standardized workflows, condition checking, disk imaging, emulation templates, metadata, equipment, secure storage, and video documentation. This is important because a preservation action becomes repeatable only when another technician can understand what was done, why it was done, and what evidence supports the result.

The Smithsonian”s Time-based Media and Digital Art Working Group takes a similarly broad view. Its scope includes computer-based, web-based, audio, video, performance, and installation art, all of which require coordinated approaches to acquisition, documentation, installation, and display. The practical lesson is that software preservation cannot be isolated from exhibition planning. A work”s technical record should describe not only its files, but also setup geometry, input devices, display behavior, network conditions, sound, interaction, and acceptable substitutions.

Game preservation laboratories offer another useful model. The Strong National Museum of Play combines original-equipment access with disk imaging and gameplay video capture. This two-track approach is valuable because original hardware provides historical evidence and experiential fidelity, while images and recordings provide scalable access when the hardware eventually fails. Similar logic can guide museum collections of interactive installations: retain representative original equipment, create verified software images, and document the work operating under both original and substitute conditions.

• Create a write-protected master disk image, then use working copies for testing and migration.
• Build a virtual sandbox that records the operating system, drivers, libraries, permissions, and network assumptions.
• Capture installation video showing startup, normal operation, failure states, user interaction, and shutdown.
• Record timing, resolution, latency, sound levels, color response, and physical positioning where these affect the experience.
• Test CRTs and other original displays where they carry significance, while evaluating low-latency adapters as carefully documented alternatives.

Adapters deserve particular caution. A modern converter can introduce scaling artifacts, input delay, incorrect aspect ratios, or frame synchronization problems. The solution is not to reject all replacement technology, but to measure and document its effects. A contemporary display may be acceptable for research access while an original CRT remains necessary for public presentation. Separating access copies, study configurations, and exhibition configurations gives institutions flexibility without pretending that all outputs are identical.

A Structured Triage Checklist for Digital Art Acquisitions

Digital preservation should begin at acquisition, not when a work is already failing. The following sequence provides a practical baseline for museums and collectors. It can be expanded according to the work”s complexity, but each step should produce a durable record that can be reviewed by conservators, technicians, curators, and future custodians.

1. Extract complete source code, runtime dependencies, and configuration parameters. Collect source files, compiled builds, installers, licenses, databases, fonts, codecs, plug-ins, firmware, credentials procedures, and external service requirements. Record compiler versions, environment variables, network assumptions, input mappings, and startup instructions. Where source code cannot be transferred, document the legal and technical reason.
2. Generate reproducible system disk images and hardware baseline profiles. Create verified images of the original storage media and retain checksums, acquisition dates, tool versions, and chain-of-custody information. Profile the hardware, including processor, memory, graphics output, ports, controller behavior, display model, resolution, and latency. Preserve an untouched master and separate copies for emulation and testing.
3. Document the artist”s parameters regarding acceptable future component substitution. Ask which elements are essential, which are replaceable, and which visible signs of obsolescence should remain. Discuss display technology, sound, interaction, response time, failure behavior, networking, and physical placement. Convert the discussion into an agreed conservation rationale rather than leaving it as informal recollection.
4. Establish scheduled emulation integrity and playback checks. Reopen disk images at defined intervals, verify checksums, test the artwork in its virtual environment, and compare output against reference recordings and condition reports. Track changes in host systems, emulators, adapters, licenses, and security settings. A failed test should trigger investigation and documentation, not silent repair.

This checklist should be connected to broader institutional resilience. Maintain multiple backups in separate locations, restrict unnecessary network exposure, inventory credentials and dependencies, and ensure that more than one staff member understands the environment. The PERICLES emulation strategy is useful here because it separates the digital artifact, runtime environment, and hardware environment. That separation helps teams locate risk at the interfaces where failures most often occur.

Building an Active Future for Ephemeral Works

Digital art cannot be preserved by treating a computer as a sealed container. The object of care is a changing system composed of code, hardware, software environments, interfaces, documentation, and human knowledge. Static storage remains necessary, but it is only the foundation. Disk images must be verified, emulators tested, physical components assessed, and artist intentions revisited as technologies and institutional priorities change.

The practical path forward is active systems engineering shaped by conservation judgment. Start with a dependency inventory, secure original files and hardware, identify significant properties, and document acceptable substitutions before an emergency forces a decision. Preserve original equipment when its material behavior matters, use virtualization or emulation when they provide reliable access, and treat every migration as a documented interpretive act. For institutions and collectors building a framework today, the most valuable investment is not a single preservation tool. It is a repeatable process that keeps ephemeral works understandable, testable, and available for the future.

2026-09-15