Reference Formats
ISO Disc Image
A sector-for-sector byte copy of an optical disc's contents and filesystem, named for the ISO 9660 standard that defines how CD-ROM (and by extension DVD/Blu-ray) file systems are structured.
Extension
.iso
Full name
ISO 9660 Disc Image
Introduced
1988 (ISO 9660 standard)
Vendor
International Organization for Standardization (ISO), based on the High Sierra Group proposal / ECMA-119
What is inside the container
An .iso file is not a compressed archive but a raw, uncompressed image of an entire disc's data area, preserving the exact filesystem structure (directory tree, file locations, volume metadata) so it can be mounted and browsed exactly as the physical disc would be, or burned back to a new one. Because it mirrors optical-disc structure specifically, an ISO image has known limitations inherited from the standard itself — the original ISO 9660 restricted filenames and depth more than modern filesystems, though extensions like Joliet and Rock Ridge relaxed those limits for Windows and Unix filenames respectively.
How to open it
For archives
ISO images are a reasonable way for a DAM to preserve the exact original structure of legacy optical media (installer discs, archival CD/DVD-ROM masters) since they're a faithful, standardized, uncompressed copy rather than a lossy re-packaging. For general asset bundling, however, ISO is the wrong tool — it's built around disc-filesystem semantics, not efficient storage, so a DAM should reach for it specifically when preserving disc provenance matters, and use ZIP or 7z for everyday multi-file bundling.
The structure that ISO images preserve traces back to the High Sierra Format, a 1986 industry proposal for a common CD-ROM filesystem, which the European Computer Manufacturers Association adopted as ECMA-119 and which the International Organization for Standardization then ratified as ISO 9660 in 1988. The standard defined how directories, filenames, and volume metadata had to be laid out on a CD-ROM so any compliant drive and operating system could read it — solving the same interoperability problem for optical media that a common filesystem solves for hard drives. “ISO image” and the .iso extension became the generic shorthand for any disc image, even discs that use extensions to the base standard like Joliet (long Windows filenames) or Rock Ridge (Unix permissions and symlinks).
For a DAM, ISO images turn up mainly where physical media provenance matters: preserving an old software installer disc, an archival CD-ROM of scanned documents, or a DVD deliverable exactly as it was pressed, rather than re-extracting and re-bundling its contents into a modern archive format. Because an ISO is an uncompressed, byte-for-byte structural copy rather than a compressed container, it’s larger than a ZIP of the same files would be, but it’s the only format that faithfully reproduces bootability and disc-specific metadata — which is exactly why a DAM handling legacy media assets keeps ISO as a distinct, purpose-specific format rather than converting everything to ZIP.
Frequently asked
Is an ISO file compressed the way a ZIP file is?
No — an ISO image is an uncompressed, sector-for-sector copy of a disc's data, which is why it's typically larger than a ZIP archive of the same files; its purpose is structural fidelity, not space savings.
Can Windows and macOS mount ISO files without extra software?
Yes — both have had native ISO mounting built in for years (Windows since Windows 8, macOS via Disk Utility), so double-clicking an .iso opens it as a virtual disc without installing anything.
Why would a DAM keep something as an ISO instead of extracting its files?
When the physical disc's exact structure matters for provenance or bootability — an original software installer disc or an archival disc image — an ISO preserves that faithfully, which simply re-zipping the extracted files would lose.
What are Joliet and Rock Ridge in relation to ISO 9660?
They're extensions to the base ISO 9660 standard that relax its original restrictive filename rules — Joliet adds long Unicode filenames for Windows compatibility, Rock Ridge adds Unix-style permissions, ownership, and symlinks.
Can an ISO image contain a bootable operating system installer?
Yes — ISO images are the standard way OS installers and recovery media are distributed, since the format can preserve the boot sector information needed to make a burned disc or mounted image bootable.
How would a DAM extract files from an ISO without mounting it as a drive?
Tools like 7-Zip (GUI) or libraries such as Python's pycdlib can read an ISO's filesystem and pull out individual files programmatically, useful for headless server-side ingest pipelines.
What's the origin of the ISO 9660 standard's name?
It comes from the ISO 9660 standard published in 1988 by the International Organization for Standardization, itself based on the 1986 'High Sierra Format' industry proposal that ECMA had adopted as ECMA-119.
Is ISO still relevant for a DAM given physical discs are largely obsolete?
Yes for archival and legacy-media use cases specifically — organizations digitizing old CD/DVD-ROM libraries or preserving original software distributions still rely on ISO images as the faithful representation of that original media.
Sources
- ISO 9660 was published in 1988 by the International Organization for Standardization, based on ECMA-119, which itself derived from the 1986 High Sierra Format proposal for CD-ROM filesystems. checked 2026-08-07 — Wikipedia — ISO 9660
- ISO 9660 defines the volume and file structure of CD-ROM for information interchange, and gave rise to the generic term 'ISO image' for optical disc images. checked 2026-08-07 — ISO — ISO 9660 (ISO images for computer files)