Reference Formats
EPUB
An open, XML-and-ZIP-based e-book format standardized by the IDPF (now W3C) as the reflowable successor to the earlier Open eBook standard.
Extension
.epub
Full name
Electronic Publication
Introduced
EPUB 2.0 approved by IDPF in September/October 2007; EPUB 3 released in 2011
Vendor
International Digital Publishing Forum (IDPF); standard now maintained by the W3C after the IDPF-W3C merger in 2017
What is inside the container
An EPUB file is a ZIP archive containing XHTML content files for each chapter or section, a CSS stylesheet for styling, an OPF package file describing metadata and reading order, an NCX or nav document for the table of contents, and embedded fonts or images. It builds on three combined specifications — Open Packaging Format, Open Publication Structure, and Open Container Format — meaning an EPUB is essentially a self-contained mini-website packaged for offline, reflowable reading.
How to open it
For archives
EPUB is a well-suited archival format for e-book and long-form document assets in a DAM, since it's an open standard maintained by the W3C with broad reader support and a transparent ZIP/XML/XHTML structure that doesn't require the originating authoring tool to inspect or extract content. The main practical note is version awareness: EPUB 3 (2011 onward) added significant capabilities over EPUB 2 (fixed layouts, media overlays, better accessibility metadata), so a DAM should record which EPUB version an asset conforms to, since not all reading systems handle EPUB 3-specific features identically.
EPUB grew directly out of the Open eBook standard that SoftBook Press had developed in 1999, which the newly formed International Digital Publishing Forum inherited and modernized. The IDPF approved EPUB 2.0 as an official standard in September/October 2007, combining the Open Publication Structure, Open Packaging Format, and Open Container Format specifications into a single, ZIP-based package format. EPUB 3 followed in 2011 with substantially expanded capabilities — fixed-layout support, embedded multimedia, and richer accessibility metadata — and in 2017 the IDPF merged into the W3C, which now maintains the standard going forward.
For a DAM handling publishing or long-form content assets, EPUB behaves much like the other ZIP-and-XML formats on this list: chapter text lives as ordinary XHTML files that can be indexed for full-text search directly, and the OPF package file exposes structured metadata (title, author, language, identifiers) that a DAM can extract without any e-reader software. The format’s reflowable design — text that resizes and re-paginates to fit the reading device rather than being locked to fixed page dimensions — is precisely what makes it suitable for the wide range of screen sizes a DAM’s downstream consumers might use, in contrast to a fixed-layout format like PDF.
- XHTML content files — one per chapter or section
- CSS stylesheet — styling
- OPF package file — metadata and reading order
- NCX or nav document — table of contents
- Embedded fonts and images
Frequently asked
Can a DAM full-text index the content of an EPUB file directly?
Yes, since chapter content is stored as plain XHTML files inside the ZIP archive, a DAM's indexer can extract and search that text without needing an e-reader application.
Why doesn't Amazon Kindle open EPUB files directly?
Kindle devices use Amazon's own proprietary formats (historically AZW/MOBI, now KFX), so EPUB files need to be converted — commonly with Calibre — before they can be read on a Kindle.
What's the difference between EPUB 2 and EPUB 3 that a DAM should track?
EPUB 3, released in 2011, added fixed-layout support, embedded multimedia, and richer accessibility metadata beyond EPUB 2, so a DAM should record the version since not all reading systems support EPUB 3 features identically.
Can a DAM extract the table of contents from an EPUB without opening it in a reader?
Yes, the navigation structure is stored as a dedicated nav document (EPUB 3) or NCX file (EPUB 2) inside the archive and can be parsed directly.
Is EPUB a good long-term archival format for digital publications?
Yes, it's an open standard now maintained by the W3C with wide reader support and a transparent, inspectable ZIP/XML structure, comparable in durability to other openly documented office formats.
Why is EPUB described as 'reflowable' and what does that mean for a DAM's preview generation?
Reflowable means text automatically re-paginates to fit whatever screen or window size it's displayed in, rather than being locked to fixed page dimensions like a PDF — a DAM's EPUB preview needs a reading-system-style renderer rather than simple page rasterization.
Can embedded fonts and images be extracted from an EPUB file directly?
Yes, since EPUB is a ZIP archive, fonts and images stored within it can be extracted with any archive tool without needing e-reader software.
Does an EPUB file store metadata like title and author in a structured way?
Yes, the OPF package file inside the archive contains structured Dublin Core metadata fields (title, creator, language, identifier) that a DAM can extract programmatically.
Sources
- EPUB 2.0 became an official IDPF standard in 2007, combining the Open Publication Structure, Open Packaging Format, and Open Container Format specifications, superseding the earlier Open eBook standard. checked 2026-08-07 — EDRLab - EPUB 3
- The Open eBook Publication Structure that EPUB succeeded was originally developed in 1999, and the IDPF merged into the W3C in 2017, which now maintains the EPUB standard. checked 2026-08-07 — Wikipedia - EPUB