EPUB Validation: Why Your Files Need to Be Right Before You Launch
Publishers
Mar 1, 2026
The File Quality Problem
One of the most consistent findings in publisher reading app implementations is that a significant proportion of EPUB files — even from established publishers with professional production workflows — contain errors that prevent them from being ingested correctly or rendered reliably across devices.
This is not a reflection of poor editorial quality. It is a reflection of the gap between what most EPUB production workflows check for and what the EPUB 3 specification actually requires. Files that display correctly in Adobe Digital Editions or Apple Books may still fail validation — because those reading systems are tolerant of errors that a strict validator would flag.
Understanding what EPUB validation means, what EPUBCheck looks for, and how to resolve common errors is essential preparation for any publisher planning to deliver content through a reading platform.
What Is EPUB Validation?
EPUB validation is the process of checking an EPUB file against the EPUB specification to confirm that it is correctly formed. The standard tool for this is EPUBCheck, an open-source validator developed by the DAISY Consortium and maintained by the W3C EPUB community. EPUBCheck is the reference implementation of EPUB validation — if a file passes EPUBCheck, it conforms to the specification.
EPUBCheck checks for errors at multiple levels: the structure of the EPUB container, the metadata in the OPF package file, the HTML content of each chapter, the CSS, the images, and the navigation document. It reports errors (which must be fixed) and warnings (which indicate potential issues but do not necessarily prevent the file from functioning).
Common Validation Errors
The errors that appear most frequently in publisher EPUB files include:
Missing or incorrect metadata: The OPF package file must include specific metadata fields — title, identifier, language, and modification date. Missing or malformed metadata is one of the most common errors.
Invalid HTML: EPUB 3 content documents must be valid XHTML. HTML that is valid in a web browser may not be valid XHTML — unclosed tags, incorrect nesting, and deprecated elements are common issues.
Missing accessibility attributes: EPUB 3 has specific requirements for accessibility metadata and ARIA attributes. Files produced before accessibility requirements were widely understood frequently lack these.
Oversized images: Images that exceed the recommended size limits can cause rendering problems on devices with limited memory, particularly older e-ink readers.
Broken internal links: Links within the EPUB that reference files or anchors that do not exist will fail validation and may cause navigation problems in reading apps.
Incorrect media types: Each file in the EPUB must be declared with the correct media type in the OPF manifest. Incorrect media types cause reading systems to handle files incorrectly.
How to Validate Your Files
EPUBCheck can be run from the command line or through a graphical interface. The W3C provides an online version at w3.org/publishing/epubcheck that allows files to be uploaded and validated without installing any software. For publishers with large catalogues, running EPUBCheck as part of the production workflow — before files are delivered to any platform — is the most efficient approach.
The EPUBCheck output can be verbose, particularly for files with many errors. The most important step is to distinguish between errors (which must be fixed) and warnings (which should be reviewed but may be acceptable). Errors that affect the EPUB container structure or the OPF package file are the highest priority.
What Happens If Files Are Not Validated
Reading platforms that ingest EPUB files will typically run their own validation as part of the ingestion process. Files that fail validation may be rejected outright, or may be ingested with errors that manifest as rendering problems — missing images, broken navigation, incorrect text flow — in the reading app.
Resolving these issues after ingestion is significantly more time-consuming than resolving them before. Publishers who validate their files before submitting them to a platform consistently experience faster, smoother implementations.
Publish360 does not remediate source files — publishers are responsible for delivering correctly formed EPUB 3 files. If you need guidance on your production workflow or are unsure about the quality of your existing catalogue, speak to the Publish360 team and we can advise on what to check. See also: The EPUB Standard Explained and EPUB 3 Accessibility and the European Accessibility Act.
