MAME case study: how an emulator became hardware documentation

MAME is often remembered as the program that brings old arcade machines to a computer, but the project states a different priority: documenting how electronic machines worked before that knowledge disappears. Playing is possible because the documentation is executable. If original software behaves as it did on the physical equipment, the code provides a practical way to test the model’s accuracy.

That choice turned a collection of emulators into preservation infrastructure. Created in 1997 by Nicola Salmoria from several programs dedicated to arcade hardware, MAME grew through contributions from an international community. Its current documentation says it covers more than 32,000 systems spanning roughly five decades. Official version 0.289, released on July 31, 2026, demonstrates that this historical catalog still receives corrections and new capabilities.

Preserving behavior, not only files

Saving a ROM is only one part of the problem. Making those data work again also requires an understanding of processors, audio and video chips, timing, controls, memory, auxiliary boards and the relationships among those components. MAME describes those elements through reusable drivers and devices. The result is not a static picture of the hardware but a model that can respond to input and execute programs.

Execution becomes a test. Incorrect colors, mistimed sound, input failures or crashes may indicate that the documentation is incomplete. For that reason, a system appearing in the compatibility list does not mean it is reproduced perfectly. MAME displays warnings for machines with known issues, and later versions may require additional data extracted from original equipment. The project favors documentary accuracy even when that makes setup less convenient than emulators designed primarily for consumption.

Shared architecture enabled broader coverage

MAME moved beyond arcades by absorbing sister projects. The most important was MESS, which focused on computers and consoles and was incorporated into MAME in 2015. Calculators, chess computers, home systems, gambling machines and other devices then shared the same foundation. A component documented for one platform can help multiple machines that used the same chip.

This model reduces duplication and creates connected technical memory. Instead of preserving each game as an isolated application, the project records hardware families and relationships among systems. The open repository allows people to inspect those descriptions, submit corrections and preserve the history of changes. The project as a whole is distributed under GPL 2.0 or later, while most files, including the core, use the three-clause BSD license.

Open code does not mean freely available ROMs

The separation between emulator and content is central to the case. MAME includes no portions of the original ROMs, CDs or hard drives in its executable. Users must provide those images, and the technical availability of a machine does not grant a license to copy its software. The official site hosts a small selection of games released by their rights holders for free, noncommercial distribution, while warning that this permission does not automatically extend to other websites or bundles.

This distinction connects directly with Rota42’s explanation of why abandonware is not public domain. An emulator can document an architecture without turning its entire software catalog into freely distributable material. Technical preservation, ownership of an original board, data extraction, public access and institutional use involve different responsibilities.

What the MAME case teaches

The principal outcome is not the number of playable games but documentation that can be inspected, corrected and executed. Services such as the Internet Arcade show that this foundation can also support browser experiences, while museums and archives can combine emulation with manuals, photographs, source code and production records. MAME primarily addresses the machine-behavior layer; cultural context and permission for access still depend on other institutions and rights holders.

The case also shows that digital preservation does not end when a file is copied. Models must be updated, errors documented and scattered knowledge converted into something verifiable. By treating execution as evidence for its documentation, MAME preserves not only the visible output of a work but part of the technical system that allowed it to exist.