What is an EPUB? A practical explainer
An EPUB is a small website in a zip file. That's almost the entire explanation; the rest is detail.
Published 2026-05-26 · All guides
The one-paragraph answer
EPUB stands for Electronic Publication. A file with the .epub extension is a ZIP archive containing XHTML pages, CSS stylesheets, images, fonts, and a few XML manifests that tell the reader what order to display the files in. Rename any EPUB to .zip and your operating system will open it as a folder. Most of what's inside is the same kind of HTML you'd find on a web page from 2008, give or take some namespace declarations. An e-reader is, at heart, a slow web browser that only loads one site — the book.
A short history
The EPUB format descends from the Open eBook Publication Structure (OEBPS), which was first published in 1999 by an industry group called the Open eBook Forum. That body became the International Digital Publishing Forum (IDPF), and in September 2007 the IDPF released EPUB 2.0 as the official successor to OEBPS. EPUB 3.0 followed in October 2011, bringing HTML5, CSS3, scripting, and MathML into scope. EPUB 3.0.1 was a small revision in 2014, and EPUB 3.2 arrived in May 2019.
In January 2017 the IDPF merged into the World Wide Web Consortium (W3C), which is now the steward of the format. EPUB 3.3 became a W3C Recommendation in May 2023, which means it's no longer a draft — it's the standard. The version numbers stop mattering once you understand that every reader since about 2014 quietly supports EPUB 3 features, and the EPUB 2 spec is preserved mainly so old files keep working.
What's inside the container
Unzip an EPUB and you'll see a predictable structure. There's a file called mimetype at the root, which contains the literal string application/epub+zip with no trailing newline. (The spec requires this file to be stored uncompressed and to appear first in the ZIP, so that a reader can identify the format by reading the first thirty bytes.) Then there's a folder called META-INF/ containing container.xml, which points to the package document. The package document — usually called content.opf or package.opf — is the manifest. It lists every file in the book, declares the reading order, and holds the metadata: title, author, language, identifier, publication date.
Alongside the package document you'll find the content itself. A typical EPUB has one XHTML file per chapter (chapter01.xhtml, chapter02.xhtml, and so on), a CSS stylesheet, an images folder, and, in EPUB 3, a navigation document called nav.xhtml that defines the table of contents. EPUB 2 used a separate NCX file (toc.ncx) for the same purpose, and many EPUB 3 files still include an NCX for backward compatibility.
EPUB 2 vs 3 vs 3.2
EPUB 2 is XHTML 1.1, CSS 2.1, no scripting, NCX-based table of contents. It's what you'll find in older ebooks, particularly things scanned from Project Gutenberg or files exported by Calibre with default settings. It's robust, it works on everything from a 2008 Sony Reader to a current Kobo, and it can't do much beyond text, images, and a few hyperlinks.
EPUB 3 added HTML5, CSS3 with media queries, embedded fonts that actually work, SVG, MathML for equations, the SMIL spec for synchronized media (read-aloud), and JavaScript. The navigation document replaced the NCX as the primary table of contents, though most files still ship both. EPUB 3 also introduced fixed-layout mode, which is the format used for picture books, comics, and cookbooks where the page design matters more than reflowing text.
EPUB 3.2 (2019) and 3.3 (2023) are mostly cleanup. They removed some experimental features that nobody used, tightened the accessibility requirements, and pulled the spec into alignment with current web standards. If you're authoring an EPUB today, target EPUB 3 and validate with EPUBCheck. There's no good reason to target EPUB 2 unless you're shipping to a known fleet of pre-2014 devices.
Reflowable vs fixed layout
Most EPUBs are reflowable. The text flows like a web page: change the font size on your device, and the lines rewrap to fit. Page numbers become a fiction, replaced by location identifiers or percentages. This is what novels and most non-fiction prose use.
A fixed-layout EPUB freezes the page. Each XHTML file has a declared viewport (in pixels), and the reader scales it to fit the screen rather than reflowing the content. You'll see this in children's picture books, where the illustration and text are designed together, and in comics, technical manuals, and anything that was originally typeset in InDesign and exported with layout preserved. Fixed-layout EPUBs are essentially a different beast — closer to a PDF in spirit, just wrapped in EPUB's container.
How readers render EPUBs (and why your Kindle is weird)
Apple Books, Kobo, Google Play Books, Adobe Digital Editions, Calibre's viewer, and most third-party readers render EPUB natively. They parse the XHTML, apply the CSS, and lay it out using a stripped-down web engine. The user-visible difference between readers is mostly typography and how they handle edge cases (drop caps, custom fonts, embedded video).
Kindle is the conspicuous exception. Amazon's native formats are MOBI (legacy, retired in 2022) and AZW3 / KF8 (current), and the very latest Kindles use a format called KFX. None of them are EPUB. When you send an EPUB to your Kindle — via the Send to Kindle email address or the web uploader — Amazon's servers convert it to AZW3 or KFX before delivering it to the device. As of late 2022, Amazon's Send to Kindle accepts EPUB directly; before that you had to convert to MOBI first. The conversion is mostly lossless for prose, but heavy CSS, custom fonts, and complex fixed layouts can come out looking different than they did in iBooks.
If you want a PDF version of an EPUB — for printing, for a non-EPUB reader, for sending to someone who insists on PDFs — the EPUB to PDF converter here renders the book in your browser and gives you back a PDF. The reverse trip, PDF to EPUB, is harder because PDFs don't have semantic structure; that converter does its best to recover chapter breaks and text flow from the PDF's positioned text runs.
DRM and what you can't legally do about it
Many EPUBs sold by retailers ship with Digital Rights Management. Adobe ADEPT is the most common scheme — it's what Kobo, Google Play Books, and most public libraries (via OverDrive / Libby) used historically. B&N had its own variant. The DRM wraps the EPUB's content in encryption, and only a reader application authorized for your account can decrypt it.
You'll find tools that strip ADEPT and other DRM. In the United States, the Digital Millennium Copyright Act (17 U.S.C. § 1201) makes circumventing access controls illegal even on books you've purchased, with narrow exceptions reviewed every three years by the Library of Congress. The EU's Copyright Directive (Article 6 of Directive 2001/29/EC) is similar. None of this is legal advice — the rules vary by jurisdiction and by what you intend to do with the file — but be aware that "I bought it" is not, in most places, a legal defense for removing DRM. A DRM'd EPUB is not the same kind of object as a clean EPUB, and most converters (including the ones on this site) will refuse to open it because they don't have the decryption keys, which is the correct behavior.
Validation and accessibility
EPUBCheck is the official validator, maintained by the W3C and DAISY Consortium. It's a Java command-line tool, and there are web frontends. It checks that the package document is well-formed, that all manifest entries exist, that the XHTML is valid, that fonts are properly declared. If you're producing an EPUB for distribution, run it through EPUBCheck first — storefronts like Apple Books and Kobo will reject files with errors.
Accessibility has become a real concern in the format. The EPUB Accessibility 1.1 spec (a W3C Recommendation since 2023) defines what makes an EPUB usable with assistive technology: proper heading hierarchy, alt text on images, language tags, semantic markup. The European Accessibility Act took effect on 28 June 2025 and requires that ebooks sold in the EU meet specified accessibility criteria. Publishers have spent the last few years remediating their backlists in response.
Where to go from here
If you want to look inside an EPUB, the cheapest tool is your file manager: rename the file's .epub extension to .zip and double-click. You'll see the structure laid out exactly as described above. To edit one, Sigil is the free, open-source standard — it understands the package document and can keep the manifest in sync as you add or remove files. Calibre is the all-purpose Swiss Army knife: it'll convert, edit, and manage a library, though its conversion output is sometimes more aggressive about CSS rewriting than you'd want.
If you just need to get an EPUB into another format quickly, the EPUB to PDF and PDF to EPUB tools on this site do the round trip in the browser. And if you're trying to read EPUBs you already own on a Kindle, the situation got considerably better in late 2022 — just email the file to your @kindle.com address and Amazon handles the rest.