Choose EPUB 3 as your default for any new ebook. The one exception is a plain reflowable novel aimed at very old proprietary readers that never updated their rendering engines. Either way, run EPUBCheck before you submit, and preview the file on your target stores to confirm the result renders the way you expect.
Key Takeaways
EPUB 3 offers a superior, feature-rich standard for ebooks that enables better accessibility, media support, and layout flexibility compared to EPUB 2.
| Point | Details |
|---|---|
| Use EPUB 3 by default | Choose EPUB 3 for new ebooks to access advanced features and ensure future compatibility. |
| Support for multimedia | EPUB 3 natively supports audio, video, SVG graphics, and MathML, enhancing rich content presentation. |
| Enhanced accessibility | EPUB 3 includes ARIA roles and richer metadata to improve accessibility for assistive technologies. |
| Verify with EPUBCheck | Always run EPUBCheck validation before publishing to prevent store rejections and ensure compliance. |
| Leverage EPUB 3 features for fixed layout and STEM content | Fixed-layout and academic publications benefit from EPUB 3's native support for layout properties and MathML. |
Table of Contents
- Core differences between EPUB 2 and EPUB 3
- How do retailers and reading systems handle EPUB 3?
- Which EPUB format fits your type of book?
- How to convert and validate your EPUB files
- How a formatting studio handles EPUB 3 readiness
- A formatter's take on when EPUB 3 features are worth the effort
- Getting validated EPUB 3 exports without the guesswork
- FAQ
- Sources
Core differences between EPUB 2 and EPUB 3
EPUB 2 relies on XHTML 1.1 and a limited CSS set, with navigation handled through a single NCX file. EPUB 3 replaces that foundation with HTML5 and CSS3, and it uses a toc.xhtml navigation document instead of (or alongside) the NCX. That shift opens the format to features the web has had for years: native audio and video, scripting, MathML for equations, SVG graphics in the spine, and fixed layouts for illustrated books. EPUB 3 also carries richer metadata and ARIA roles, which support text-to-speech and other assistive technology in ways EPUB 2 never could. The EPUB 3.3 specification documents each of these additions and confirms that EPUB 3.3 stays backward compatible with earlier EPUB 3 files, so moving up a minor version rarely forces a rebuild.
Packaging structure changed too. EPUB 3 tightened how the OPF package file declares spine order, fallbacks, and rendition properties, which matters once you start mixing media types or fixed-layout pages.
| Feature | EPUB 2 | EPUB 3 |
|---|---|---|
| Markup | XHTML 1.1 | HTML5 |
| Styling | Basic CSS | CSS3 |
| Navigation | NCX only | toc.xhtml, NCX optional |
| Media | Limited, plugin-dependent | Native audio, video, SVG |
| Math | Not supported | MathML |
| Accessibility | Minimal semantic support | ARIA roles, richer metadata |
| Fixed layout | Workarounds only | Native rendition properties |
A few practical notes worth keeping in mind as you format:
- Fixed layout in EPUB 3 uses rendition properties in the package file, which removes most of the manual positioning tricks EPUB 2 required.
- Image-heavy books benefit from SVG support, since vector graphics scale cleanly across screen sizes; our guide to images in EPUB covers the practical side of that.
- Text-only novels rarely need any EPUB 3 feature beyond better navigation and accessibility metadata, so the upgrade costs little.
How do retailers and reading systems handle EPUB 3?
Support for EPUB 3 is no longer the gamble it was a few years ago. Amazon KDP accepts both EPUB 2 and EPUB 3 files and handles most EPUB 3 features correctly, though you should always confirm behavior with Kindle Previewer before publishing, according to the EPUB 3.3 specification and current retailer guidance. Apple Books supports EPUB 3.3 directly, and Google Play Books expects EPUB 3.3 compliance as well, a requirement we detail in our Google Play Books preflight guide.
Older or lower-end reading systems tend to ignore features they don't recognize rather than fail outright, so a book built with EPUB 3 markup still opens on an EPUB 2 era device, just without the audio clip or MathML rendering. That graceful degradation is why defaulting to EPUB 3 carries so little risk.
Before you upload anywhere:
- Validate the file with EPUBCheck, the industry standard validator.
- Preview on Kindle Previewer and each store's own preview tool, since rendering engines differ even within EPUB 3 support.
- Add fallback content for any audio, video, or script element, so readers on older systems still get something usable.
Pro Tip: Keep a toc.ncx alongside your toc.xhtml if you expect readers on very old dedicated e-readers; it costs nothing and closes the compatibility gap.
Which EPUB format fits your type of book?
The right format depends less on preference and more on what your book actually contains. Answer a few questions about your project and the choice becomes obvious.
- Is your book a plain reflowable novel? EPUB 3 is still the better default, since it costs nothing extra and adds accessibility metadata; EPUB 2 is only defensible if you must support an unusually old proprietary reader.
- Does your book rely on illustrations or a fixed page layout? Choose EPUB 3. Its rendition properties give you predictable, cross-platform fixed-layout behavior that EPUB 2 could only approximate with workarounds, as EDRLab's production guidance notes.
- Does your book include equations, STEM content, or academic notation? EPUB 3 is the only realistic option, since MathML support and richer metadata simply don't exist in EPUB 2.
- Is accessibility a priority for your readers? EPUB 3's ARIA roles and semantic markup align with modern accessibility expectations in a way EPUB 2 cannot match; our EPUB accessibility checklist walks through the specific items to check.
- Do you need audio, video, or interactive elements? EPUB 3 supports these natively; EPUB 2 requires fragile plugin-based workarounds that most modern readers no longer honor.
Run through those five questions before you format, and the decision usually resolves itself before you open your first export dialog.
How to convert and validate your EPUB files
Converting EPUB 2 to EPUB 3, or the reverse, is rarely necessary once you're formatting from scratch, since most authoring tools now export EPUB 3 by default. When you do need to convert an older file, the safest path is re-exporting from your source manuscript rather than patching the existing EPUB 2 markup by hand.
Whichever direction you go, validation is the step that actually prevents store rejections. EPUBCheck release 5.3.0 validates against EPUB 3.3, and running it before submission catches the errors that cause the most rejections: malformed navigation documents, missing metadata fields, and absent fallbacks for media elements.
The latest EPUBCheck release validates specifically against the EPUB 3.3 specification, which means a file that passes today also meets the current retailer baseline, according to the EPUBCheck release notes.
Typical fixes once EPUBCheck flags something:
- Malformed manifest entries: usually a missing file reference or an incorrect media type declaration.
- Navigation errors: often a toc.xhtml that doesn't match the spine order.
- Missing fallbacks: add a static image or text alternative for any audio, video, or script element.
Our guide to fixing EPUBCheck errors walks through each error type with examples. Finish with a pass through Kindle Previewer and Apple Books preview before you call the file done.
How a formatting studio handles EPUB 3 readiness
Professional formatting workflows build validation into the process instead of treating it as a final gate. A preflight pass that runs EPUBCheck live while you work catches a malformed manifest or a missing fallback the moment it appears, not after a store rejection email arrives days later.
That approach pays off most on fixed-layout and accessibility-heavy projects, where small markup errors compound quickly across dozens of pages.
- Live validation during formatting means fewer rounds of corrections after export.
- A typesetting engine built for both reflowable and fixed-layout EPUB 3 handles rendition properties correctly the first time.
- Accessible export paths bake in semantic markup and metadata instead of requiring a separate accessibility pass.
Pro Tip: Validate early and often rather than once at the end. Catching a navigation error on page three of your workflow is a thirty-second fix; catching it after a store rejection can cost you a day.
A formatter's take on when EPUB 3 features are worth the effort
Not every book needs the full EPUB 3 feature set, and chasing interactivity on a plain novel wastes time you could spend editing. Weigh the actual payoff: a fixed-layout picture book needs EPUB 3's layout properties, but a text-only thriller mostly needs clean navigation and solid metadata.
If you're on a tight deadline and your manuscript is plain reflowable text, export validated EPUB 3 and move on. If you're unsure where your book lands, validate against both specs and test on your target stores, or bring in a formatter who does this daily.
— James
Getting validated EPUB 3 exports without the guesswork
We support the idea that formatting shouldn't mean guessing whether a file will pass store review. A typesetting engine running live validation against publishing standards as you work helps surface manifest errors, missing fallbacks, and navigation problems while still editing, not after a retailer bounces the file back.
- Cross-platform formatting on multiple operating systems so your workflow isn't locked to one operating system.
- Validation-first exports aimed at EPUB 3.3 compliance, designed to reduce the back-and-forth that store rejections usually cause.
- An integrated shop interface for publishing once your file passes checks, alongside export paths for major ebook retailers.
Browse our ebook formatting software to see how the export workflow handles EPUB 3 from manuscript to store-ready file.
FAQ
How do I convert EPUB 3 to EPUB 2?
Re-export from your original manuscript using settings that target EPUB 2 markup, since hand-editing an EPUB 3 file down to EPUB 2 risks breaking navigation and metadata. This direction is rarely needed today, since nearly every modern store and device accepts EPUB 3.
What is the EPUB 3 format used for?
EPUB 3 is the current standard for reflowable and fixed-layout ebooks, built on HTML5 and CSS3 so it can carry native audio, video, MathML, and SVG graphics. It also supports richer accessibility metadata and ARIA roles, which is why it's the recommended format for accessibility-first publications, per the EPUB 3 overview.
Does Kindle prefer MOBI or EPUB?
Amazon KDP now accepts EPUB files directly and has moved away from requiring MOBI, with EPUB 2 and EPUB 3 both supported through the EPUB 3.3 specification's retailer guidance. Always confirm rendering with Kindle Previewer before you publish, since previewer results reflect what shoppers will actually see.
Which eBook format is best for Kindle?
A validated EPUB 3 file is the safer default for Kindle, since it carries better navigation and metadata while still degrading gracefully on older Kindle devices. Run the file through EPUBCheck and Kindle Previewer before upload to confirm it behaves as expected on your target device range.
How does text-to-speech work with EPUB 3 accessibility features?
EPUB 3's semantic markup and ARIA roles give screen readers and text-to-speech tools clearer structure to work from than EPUB 2 ever provided. For background on how text-to-speech systems use that kind of structured text, see this guide to text-to-speech for reading.