*This post may contain affiliate links. As an Amazon Associate we earn from qualifying purchases.
An arcade game ROM is the game’s program and data stored on an arcade board, usually on a chip such as a mask ROM or EPROM. In MAME and other emulators, the same word is also used for the dumped file that was copied from that chip.
That double meaning is where most confusion starts. If a game will not run in MAME, the problem is often not just “missing ROMs” in the generic sense. It may be the wrong version of the set, a missing CHD, a bad file placement, or, on a real cabinet, a socket or connection issue rather than the chip itself.
This article breaks down what an arcade ROM actually is, how it differs from RAM and CHDs, and what to check first when a classic arcade board or MAME setup gives you trouble.
What an arcade game ROM actually is
In plain English, a ROM is the part of the game that tells the hardware how to run the software side of the arcade machine. On original boards, that usually means one or more chips on the PCB that hold code, graphics, sound data, or program data. The game board reads that data when the machine powers on.
When people talk about MAME ROMs, they usually mean a dumped copy of those chips stored as files on a computer. The emulator does not use the physical chip itself; it uses the dump of the chip’s contents.
That is why the same word can mean two different things:
- Physical ROM chip = the actual component on the arcade board.
- ROM file = the dumped data from that chip, usually in a ZIP file for MAME.
If you keep those two meanings separate, a lot of the confusion around arcade boards, emulation, and repairs makes much more sense.
Physical ROM chips vs. emulator ROM files
| Term | What it means | Why it matters |
|---|---|---|
| Mask ROM | A factory-programmed chip that cannot normally be re-written | If it fails, you usually replace it rather than reprogram it |
| EPROM | A chip that can be erased and burned again with the right equipment | Useful for repairs, reproduction boards, and testing |
| ROM dump | A file copied from the chip’s data | This is what MAME usually loads |
| CHD | Compressed Hunks of Data, used for storage devices like hard drives or laserdiscs | Many later arcade games need both the ROM ZIP and the matching CHD |
So when someone says “I need the ROM for this game,” they may mean the actual chip, the emulator file, or both. In repair work, that distinction is important. In MAME, it is even more important because file names, set versions, and companion files have to line up correctly.
When a game uses CHDs instead of only ROMs
Not every arcade game is just a simple ROM set. Many later titles need a CHD alongside the ROM ZIP. The ROM file handles the board’s code and smaller assets, while the CHD stores larger data such as disc images or hard drive contents.
For MAME, the usual rule is simple: the CHD has to be in the right folder structure and must match the game set it belongs to. If the ROM ZIP is present but the CHD is missing or placed wrong, the game may still fail to boot.
There is also a bigger exception that catches a lot of new readers off guard: some very early arcade machines used discrete logic instead of a traditional CPU-and-ROM setup. Those boards may not have a normal ROM dump at all.
Why MAME can still reject a ROM set
People often assume one ROM file should work with every version of MAME. In practice, that is not always true. MAME is picky because its job is to preserve specific board behavior, and dumps get corrected over time. A newer build may reject an older set, or a set may only work if it matches the exact expected version.
One more thing that trips people up: set labels such as “set 1” and “set 2” are not always a clean timeline of which version is newer. For older games, the naming can be confusing, and clone/original labels do not always tell you the whole story. If you are comparing board revisions, that kind of confusion is common in arcade collecting, just like it is in Galaga vs Galaxian differences.
That is why “download any ROM and it should work” is usually the wrong expectation. The file has to match the emulator version, the game revision, and sometimes an extra data file as well.
Common arcade ROM problems and the fastest safe checks
If a real arcade board is throwing a ROM error, the chip itself is not always the first thing to blame. Hobbyist repair reports repeatedly point to dirty sockets, oxidized legs, and board-level contact problems before a truly dead chip.
Use this order when you troubleshoot:
- Check the obvious file or set mismatch first. In MAME, confirm the ROM set matches the emulator version and that any required CHD is present.
- Check the folder structure. A misplaced ZIP or CHD is a very common reason for a game not to start.
- On original hardware, clean and reseat the chip or socket. Dirty legs and oxidized contacts can cause bad reads.
- Compare reads or swap in a known-good chip. If one read is inconsistent and another is clean, the chip may actually be failing.
- Only then assume the ROM chip is dead. A bad chip is real, but it is not the first thing to blame.
If the board uses a socketed ROM, a careful reseat and cleaning can solve more problems than people expect. If it is a soldered-down chip or a mask ROM, the fix may be replacement rather than reprogramming.
ROM, RAM, and why people mix them up
ROM stands for Read Only Memory. In arcade hardware, that means the part of the system that stores data the board needs to start and run the game. RAM is different: it is temporary working memory the machine uses while the game is running.
People sometimes say ROM “caches” data, but that is not really the right way to think about it. ROM is mostly about storing code and game data permanently. RAM is the part that changes constantly while the game is running.
So if the power goes out on an arcade board, the game does not “remember” your progress unless the board has separate save hardware. That is part of why arcade games were designed the way they were: quick, repeatable, and easy to reset for the next player.
What this means if you are buying, repairing, or emulating a cabinet
If you are buying a classic arcade board, ask whether the game uses simple ROM chips, EPROMs, or a ROM-plus-CHD setup. That tells you how hard it may be to repair and whether missing data is a likely problem.
If you are restoring original hardware, the safest mindset is to treat ROM problems as one possible cause, not the default cause. Clean contacts, verify the board revision, and confirm the correct chip type before assuming the game is beyond repair.
If you are trying to run a game in MAME, start with the exact set the emulator expects, then check for CHDs, then check file placement. That sequence solves a lot of the common “it used to work” complaints.
For a simple comparison of how arcade versions and naming can get confusing, the differences in Galaga vs Galaxian are a good example of why board revisions and set labels matter.
Frequently asked questions
Do all arcade games have ROMs?
No. Most classic arcade boards do, but some very early machines use discrete logic instead of a traditional ROM-based design. Those games may not have a normal ROM dump at all.
Why does MAME say a ROM is missing when I already have one?
Usually because the file does not match the exact set MAME expects, the ZIP is in the wrong place, or the game also needs a CHD. A missing parent/clone file can also trigger the error.
Is a ROM chip the same as a game cartridge?
Not exactly. A cartridge contains chips inside a removable shell. An arcade ROM chip is usually mounted directly on the board, although some systems do use cartridge-style boards or modules.
What is the difference between EPROM and mask ROM?
A mask ROM is programmed at the factory and normally cannot be erased. An EPROM can be erased and re-burned with the right equipment, which is why EPROMs are often easier to work with in repairs.
What should I check first if an arcade board says bad ROM?
Check the socket, leg condition, and board contacts before replacing the chip. If the error follows the chip across tests, then the ROM itself is more likely at fault.
For a real-world example of how arcade revisions can be confusing, the same kind of set and version questions show up in Galaga vs Galaxian differences and other classic board comparisons.
Once you understand that “ROM” can mean both a physical chip and a dumped file, arcade troubleshooting gets much simpler. The rest is mostly about matching the right file to the right board and checking the easy failure points before blaming the chip.