EPUB 2 vs EPUB 3 comes down to the underlying technology and what each version can do. EPUB 2, standardized in 2007, is built on HTML 4.01 and CSS 2.1 and handles text-heavy books well but lacks support for multimedia, advanced accessibility, or fixed layouts. EPUB 3, released in 2011 and currently at version 3.3 (2022), uses HTML5 and CSS3, supports embedded audio, video, JavaScript, MathML, and full WCAG accessibility compliance. All major self-publishing platforms — KDP, IngramSpark, and Draft2Digital — accept both formats, but EPUB 3 is now the industry default.
- What Changed Between EPUB 2 and EPUB 3?
- Why Does EPUB 3 Use HTML5 Instead of HTML 4?
- What Happened to the NCX Navigation File?
- Does EPUB 3 Support Audio, Video, and Interactivity?
- How Do KDP, IngramSpark, and Draft2Digital Handle EPUB Versions?
- Which EPUB Version Should You Use?
- Frequently Asked Questions
What Changed Between EPUB 2 and EPUB 3?
The core change is the shift from legacy web standards to modern ones. EPUB 2 wraps its content in XHTML 1.1 (a strict variant of HTML 4.01) and styles it with CSS 2.1 — the same technology that powered websites in the mid-2000s. EPUB 3 moved to HTML5 and CSS3, which brought dramatically richer formatting, layout, and media capabilities to the ebook format.
In practical terms, this means EPUB 3 files can include features like embedded fonts with proper CSS3 @font-face declarations, responsive layout techniques, SVG graphics rendered natively, and semantic markup that screen readers and assistive technology can parse correctly. EPUB 2 files can embed fonts too, but rely on older CSS that limits typographic control.
The EPUB specification was originally maintained by the International Digital Publishing Forum (IDPF). When the IDPF merged with the W3C (the organization that governs web standards), EPUB became a W3C specification — which is why the current EPUB 3.3 standard published in 2022 aligns so closely with modern web technology.

Why Does EPUB 3 Use HTML5 Instead of HTML 4?
HTML5 provides native support for multimedia elements, semantic document structure, and accessibility features that HTML 4.01 simply does not have. This single change is what enables almost every other improvement in EPUB 3.
With HTML5, EPUB 3 content documents can use semantic elements like <nav>, <section>, <article>, and <aside> that give reading systems and screen readers a precise understanding of the document structure. EPUB 2’s XHTML content relied on generic <div> elements with class attributes, which reading systems had to guess at.
The CSS3 upgrade matters just as much. EPUB 3 supports CSS3 features like multi-column layouts, transitions, custom properties, and — critically for international publishing — writing-mode properties that enable vertical text (used in Japanese and Chinese ebooks) and right-to-left text (used in Arabic and Hebrew). EPUB 2 had limited support for these global language features.
What Happened to the NCX Navigation File?
EPUB 3 replaced the XML-based NCX (Navigation Control for XML) file with an HTML-based navigation document. The NCX was a proprietary XML format inherited from the DAISY digital talking book standard, and while it worked, it was a separate technology that authors and tools had to support alongside the ebook’s HTML content.
The new EPUB 3 navigation document is a standard HTML file using the <nav> element, which means it can be styled with CSS and displayed directly as a page in the ebook itself — something the old NCX file could never do. If you have read our guide to what an NCX file is and whether you still need one, you will know that EPUB 3 still allows an NCX file for backward compatibility with older reading devices, but it is no longer required.
Most modern ebook creation tools — Vellum, Scrivener, Sigil, and Calibre — generate both the new HTML navigation document and a legacy NCX file automatically, so you get backward compatibility without extra work.
Does EPUB 3 Support Audio, Video, and Interactivity?
Yes. EPUB 3 supports embedded audio and video through standard HTML5 <audio> and <video> elements, JavaScript for interactivity, and MathML for rendering mathematical equations natively. EPUB 2 supports only text and static images.
EPUB 3 also introduced media overlays — a synchronization format that pairs pre-recorded audio with text highlighting, enabling read-aloud functionality. This is especially relevant for children’s books and educational titles where audio narration enhances the reading experience.
For authors writing academic or technical content, EPUB 3’s MathML support means equations render as crisp, scalable text rather than the blurry raster images required by EPUB 2. That said, MathML rendering support varies across reading applications, so testing on your target platforms is important.
One significant caveat: while the EPUB 3 specification supports all of these features, not every e-reader device or app supports them equally. Kindle devices strip out JavaScript entirely, and many dedicated e-ink readers ignore audio and video elements. These multimedia features work best on tablet-based reading apps like Apple Books, Google Play Books, and Kobo’s iOS/Android apps.
How Do KDP, IngramSpark, and Draft2Digital Handle EPUB Versions?
All three major self-publishing platforms accept both EPUB 2 and EPUB 3 files, but each processes them differently. Understanding these differences helps you choose the right format for your distribution strategy.
Amazon KDP accepts EPUB uploads but converts every file to its proprietary KF8 format (Amazon’s internal ebook format derived from EPUB). Because of this conversion step, whether you upload EPUB 2 or EPUB 3 matters less on Amazon — KDP extracts the content and reformats it. However, EPUB 3 files tend to preserve formatting more accurately through the conversion because KF8 itself is based on HTML5 and CSS3. Note that KDP’s delivery fee is calculated on file size, so large EPUB 3 files with embedded multimedia will cost more to deliver.
IngramSpark accepts both EPUB 2 and EPUB 3 for reflowable ebooks. Their specifications require a maximum file size of 100 MB and no single image exceeding 5.6 million pixels (length multiplied by width). IngramSpark distributes to Apple Books, Kobo, Barnes & Noble, and libraries — all platforms with strong EPUB 3 support — so EPUB 3 is the better choice here.
Draft2Digital accepts both formats without modification and distributes to multiple retailers. Their system passes your EPUB file through to each retailer largely unchanged, making the version you upload the version readers receive.
Which EPUB Version Should You Use?
For most self-published authors in 2026, EPUB 3 is the right choice. It is the current industry standard, all major platforms support it, and every mainstream ebook creation tool outputs it by default.
If you are writing a text-heavy novel or nonfiction book with minimal images, you may not notice any practical difference between an EPUB 2 and EPUB 3 file — the reading experience will be nearly identical on modern devices. But EPUB 3 still gives you better accessibility features, improved metadata, and forward compatibility as older EPUB 2 reading systems are gradually retired.
EPUB 3 becomes essential — not optional — if your book includes any of the following: fixed-layout pages (common in children’s books, cookbooks, and graphic novels, as covered in our guide to reflowable vs. fixed-layout ePub), mathematical equations, embedded audio or video, complex tables, or if accessibility compliance matters for your distribution (particularly library systems, which increasingly require EPUB Accessibility 1.1 conformance).
There is no cost difference between producing an EPUB 2 and an EPUB 3 file for standard reflowable text content. Tools like Vellum, Scrivener, and Calibre output EPUB 3 by default. If you are working with a formatter or conversion service, confirm they are delivering EPUB 3 — some older workflows may still default to EPUB 2. And if your book includes images, our guide on why images break when converting Word to EPUB covers the most common pitfalls regardless of which EPUB version you use.
Frequently Asked Questions
Can EPUB 2 readers open EPUB 3 files?
In most cases, yes. EPUB 3 was designed with backward compatibility in mind, so older EPUB 2 reading systems can typically open EPUB 3 files and display the text and images correctly. Advanced EPUB 3 features like embedded video, JavaScript, or media overlays will simply be ignored by older readers.
Do I need to convert my existing EPUB 2 files to EPUB 3?
Not necessarily. If your EPUB 2 files are text-heavy books that display correctly on current platforms, they will continue to work. However, if you are updating or re-releasing a title, converting to EPUB 3 ensures better accessibility metadata, improved navigation, and compatibility with future reading systems. Tools like Calibre can convert between versions.
Does Amazon Kindle support EPUB 3 features like audio and video?
No. Amazon KDP converts all uploaded EPUB files to its proprietary KF8 format, and Kindle devices do not support embedded audio, video, or JavaScript. If your book relies on multimedia elements, those features will only work on platforms that render EPUB directly, such as Apple Books, Kobo, and Google Play Books.
How do I check whether my EPUB file is version 2 or 3?
Open the EPUB file (it is a ZIP archive — rename the extension to .zip to inspect it) and look at the OPF package file inside. The version attribute on the root <package> element will read either "2.0" or "3.0". You can also run the file through the W3C’s EPUBCheck validation tool, which reports the version along with any errors.
Is EPUB 3 required for selling ebooks through library systems?
It is increasingly expected. Library distributors like OverDrive and platforms that serve academic and public libraries are moving toward requiring EPUB Accessibility 1.1 conformance, which is only available in EPUB 3. While EPUB 2 files are not yet rejected outright, EPUB 3 with proper accessibility metadata will give your book the widest possible library distribution.
