ISO 9660: Making CD-ROM Data Discs Interchangeable

The compact disc became a mass-market audio format before it became a dependable way to distribute computer files. A pressed disc can carry bits, but computers still need agreement about where a volume begins, how files are named, how directories are laid out, and which fields describe a file. ISO 9660 supplied that agreement for CD-ROM interchange. It was not the optical recording technology itself, nor an operating system, but a standardized volume and file structure that helped discs move between machines.

The standard’s importance is easy to overlook because later extensions and operating systems often hide its constraints. Early ISO 9660 compatibility favored a conservative shared subset. That made broad reading more achievable but constrained names and file organization. Extensions later addressed some of those limits, while the original standard remained a compatibility layer and a historical baseline.

An audio medium needed a data-volume model

The Red Book compact disc format standardized digital audio playback, but a computer data disc needed additional conventions. A drive could return sectors while leaving software to infer the meaning of those bytes. Without a shared file system, a disc authored on one platform could be unreadable or ambiguous on another, even when the physical media and drive were compatible.

During the mid-1980s, computer and optical-storage companies worked toward a common CD-ROM structure. The High Sierra Group’s proposal helped frame the problem, and Ecma International published ECMA-119, Volume and file structure of CD-ROM for information interchange, in December 1986. The International Organization for Standardization subsequently published ISO 9660 in 1988. Ecma’s current standards archive preserves the earlier editions, making it possible to see that the specification evolved rather than appearing fully formed in a single modern release.

The standard addressed how systems exchange recorded information, not every way an operating system might present it. It specified volume descriptors, file placement, directory records, and interchange levels. It left implementation details to systems within defined rules. A compatible authoring tool and a compatible reader still had to implement those rules correctly.

Volume descriptors tell software how to interpret a disc

An ISO 9660 volume contains descriptors that identify the volume and describe its structure. A reader scans the prescribed area for a volume descriptor sequence, then uses the primary volume descriptor to locate the root directory and other metadata. A supplementary descriptor can express a different interpretation, such as an extension’s filename rules. This arrangement allows one disc to carry additional conventions while retaining a conservative baseline view.

The descriptor model is more robust than assuming that file data begins at a fixed universal location. A reader follows recorded locations and declared sizes to find directories and file extents. This is essential because the file system is a map over sectors, not a physical property of the disc. The optical medium provides recorded sectors; the standard defines how groups of sectors represent a logical volume.

The distinction between logical and physical structure matters when diagnosing a damaged or unusual image. An ISO image may contain multiple descriptors, padding, directory records, and file extents. A sector can be readable while its metadata is inconsistent. Conversely, a file may appear absent to one reader because it does not understand an extension, even though another reader can interpret it.

Interchange levels traded freedom for compatibility

ISO 9660 defined nested levels of interchange. Lower, more restrictive levels limited naming and file structure so a wider range of systems could read discs consistently. Level 1 is commonly associated with a conservative filename form of up to eight characters plus a three-character extension and a restricted character repertoire. More permissive levels allowed longer names or more complex organization, but did not imply that every early operating system would handle them equally.

These restrictions should not be described as a universal property of every CD-ROM. An authoring program might create a disc using a later level or an extension, and a particular operating system might expose names differently. Readers also applied compatibility rules such as uppercasing names or translating punctuation. User-visible paths were therefore a presentation of the on-disc identifiers, not always a byte-for-byte copy of them.

The standard’s tradeoff was deliberate. If every platform could invent arbitrary names and metadata, exchange would fail. If the format limited itself to the smallest shared subset, it would be less expressive. Nested levels let producers choose a compatibility target, although consumers still needed to know which level they supported.

Directories and path tables were designed for optical access

CD-ROM drives have different access characteristics from magnetic disks. ISO 9660 recorded directory data and file extents in a way that readers could locate without rewriting metadata in place. A directory record describes an entry and points to the sectors containing its data. Path tables provide another representation of directory relationships to support navigation.

The file system is effectively read-only on a pressed CD-ROM. That property changes assumptions about updates: a producer authors a new volume or session rather than modifying a file in place as on a disk. Read-only media simplified distribution and preservation of a shipped release, but it also meant that a disc was a snapshot. A correction generally required a replacement disc or separate update mechanism.

Optical media’s slower seek behavior also influenced access patterns. A program that opened many small files across distant extents could be slower than one reading contiguous data. The standard did not guarantee performance. Disc layout, drive technology, caching, and application behavior determined whether a workload felt responsive.

Extensions expanded names without replacing the base

The original naming limits became a visible user problem as software and multimedia titles needed descriptive filenames and international character sets. Extensions offered ways to preserve a readable base volume while expressing richer names. Joliet, associated with Microsoft, used supplementary volume descriptors and Unicode-based names. Rock Ridge added Unix-oriented metadata such as longer names and permissions on top of ISO 9660-compatible discs.

Extensions have compatibility consequences. A reader that understands only the primary volume descriptor can still list the basic names, while a more capable reader can expose the richer representation. This duality helped maintain interoperability, but it could produce different names or metadata on different systems. Two machines might read the same disc and show different pathnames without disagreeing about the underlying sectors.

ISO 9660 therefore should not be treated as synonymous with Joliet, Rock Ridge, or UDF. UDF became an important format for rewritable optical media and later disc workflows, but it is a distinct file system standard. The historical standards page and the relevant extension documents should be consulted when a claim depends on a specific naming or metadata feature.

Software distribution made the standard visible

CD-ROM capacity and low per-disc replication cost changed software distribution. Vendors could ship large collections of programs, documentation, fonts, datasets, and multimedia assets on a single read-only disc. The file system made that content navigable across personal computers and workstations. Before broad-band downloads became routine, a boxed application could include a disc whose directory structure was an important part of the product experience.

The disc did not automatically install software. Operating systems differed in auto-run behavior, executable formats, installers, and permissions. ISO 9660 solved the problem of locating files; it did not make binaries portable or decide whether they were safe to execute. Users could copy files from a disc, but the software still depended on processor architecture, system libraries, and installation conventions.

Optical distribution also aided archival exchange. A data set encoded on a standard volume could be read by different systems if they supported the chosen interchange level. Preservation still required validation: check the disc or image, document extensions, preserve checksums, and retain the software needed to interpret the content. A directory listing alone cannot guarantee that files remain semantically usable.

A standard was only as interoperable as its readers

The promise of ISO 9660 was cross-system interchange, but that promise depended on implementation quality and selected features. An authoring application could write records in a way a tolerant reader accepted and a stricter one rejected. A system might ignore an extension, truncate names, or present a different case. Testing on more than one platform was essential for publishers who expected broad compatibility.

The format also inherited physical-media constraints. Scratches, mastering errors, drive incompatibilities, and the limits of an aging optical drive could prevent access even when the volume structure was correct. Conversely, a good image file can preserve sector contents without preserving the original disc’s physical characteristics. These are separate preservation questions.

ISO 9660 was durable because it addressed a clear boundary: how to organize computer information on a read-only optical volume so independent systems could exchange it. It did not solve every problem of software deployment, multilingual naming, or long-term archiving. Extensions evolved around those gaps while keeping the base format useful.

What ISO 9660 changed

The standard transformed CD-ROM from a medium that could merely hold data into a medium that could carry a recognizable, navigable file hierarchy across platforms. That made reference works, software libraries, and commercial applications practical to distribute on disc. Its conservative rules demonstrate a recurring standardization choice: restrict expression enough to gain a dependable common denominator, then evolve through explicit extensions.

Ecma’s edition archive and the standard itself are the primary sources for exact structure and version history. Contemporary platform documentation is needed for how particular operating systems exposed names and extensions. These sources support the claim that ISO 9660 standardized interchange, not the broader claim that every data CD had identical behavior on every computer.

The enduring lesson is that media compatibility requires both physical and logical agreement. A drive can read sectors, but only shared descriptors, directory conventions, and file rules make those sectors useful to different systems. ISO 9660 provided that layer for an era when shipping a library of bits on a disc could be easier than sending it over a network.

Related:

Sources: