Read-Only Memory is a class of non-volatile semiconductor memory historically designed so that stored information could be read by a system but not normally modified during ordinary operation. The original concept involved permanently encoded data that was physically established during manufacture, making the contents persistent even when power was removed. The term subsequently became a broader label for several technologies that retain data without power, including programmable and electrically erasable forms. In contemporary computing, the term often remains in use even when the underlying memory can technically be rewritten. This historical terminology can therefore be misleading if interpreted literally as meaning that all modern ROM devices are permanently unwritable.
Traditional mask-programmed ROM stores information through manufacturing processes that establish the logical state of memory cells. Such devices were useful when large quantities of identical firmware or fixed data were required because the contents remained stable without electrical power. Programmable read-only memory, commonly known as PROM, introduced the ability for a device to be programmed after manufacture, typically through a one-time physical programming process. Erasable programmable read-only memory, or EPROM, allowed contents to be erased and reprogrammed, historically using ultraviolet light through a transparent package window. Electrically erasable programmable read-only memory, or EEPROM, permitted electrical rewriting and became important for configuration storage and firmware.
ROM became particularly significant for firmware because computers need some form of persistent code available immediately after power-on. Early computers and embedded systems could store boot or control routines in ROM or related technologies. Modern PCs generally store firmware in electrically rewritable flash memory rather than literal mask ROM, but the firmware is still sometimes informally described as residing in "ROM". This usage reflects the functional role of the memory as persistent firmware storage rather than its exact physical implementation. Firmware stored in flash can be updated to add hardware compatibility, correct defects or address security issues, which would not be possible with genuinely immutable mask ROM without replacing the physical device.
Read-only memory is particularly valuable where data must survive power loss and should not ordinarily change. Embedded systems may store fixed program code, lookup tables, boot routines, calibration data or configuration information in non-volatile memory. Historically, game cartridges, calculators, appliances and industrial controllers used ROM and related technologies to retain software. Modern embedded systems may combine several forms of non-volatile memory, using immutable or protected boot components alongside rewritable firmware. The choice depends on requirements for updateability, manufacturing cost, endurance, security and expected product lifetime.
The different ROM technologies represent different trade-offs. Mask ROM is inexpensive at high production volumes but requires the contents to be fixed during manufacturing. PROM can be programmed once after manufacture, making it useful for lower-volume or configurable production. EPROM permits reuse after ultraviolet erasure but requires specialised handling and exposes the device to an inconvenient erase process. EEPROM supports electrical rewriting, generally with smaller write operations and different endurance characteristics from flash memory. Flash memory is a form of electrically erasable non-volatile memory optimised for higher-density storage, typically using block-oriented erase operations. These distinctions matter because "ROM" does not identify one uniform physical technology.
ROM and RAM have fundamentally different historical roles. RAM is normally used as a writable working area for data and programs currently being executed, whereas ROM and related non-volatile technologies provide persistent information that remains available after power is removed. A computer may load firmware from non-volatile memory into other memory resources during startup, after which most normal application execution occurs from RAM. Modern processors can execute code directly from certain non-volatile memories in some embedded architectures, although performance and memory-mapping characteristics vary. The relationship between ROM and RAM is therefore architectural rather than simply a binary distinction between "permanent" and "temporary" data.
Modern security architectures have renewed interest in genuinely immutable or strongly protected code storage. A hardware root of trust can begin with code that is difficult or impossible to modify, establishing an initial trusted stage for secure boot. Subsequent firmware can be authenticated before execution using cryptographic signatures and hardware-protected keys. Rewritable firmware storage introduces an update mechanism but also creates a potential attack surface if update processes are not properly protected. Consequently, the distinction between immutable ROM, protected flash and ordinary writable storage can have significant security implications.
A common misconception is that any memory described as ROM cannot ever be rewritten. Modern terminology often uses ROM as a functional or historical category even where the actual component is flash or EEPROM and is therefore electrically rewritable. Another misconception is that ROM necessarily means firmware; although firmware is a major application, ROM technologies can store any persistent digital information.
The most useful interpretation depends on context: historically, ROM describes non-volatile memory with restricted modification capability, while contemporary computing often uses the term loosely for persistent firmware memory. Precise technical discussions should identify the actual technology, such as mask ROM, PROM, EPROM, EEPROM or flash memory, rather than relying solely on the generic label.
