A check before the next chapter.
This is a structural preflight, not a device certification or full EPUB validator. It checks the archive, package metadata, declared reading order, and encryption markers, then explains what to test on your chosen reader.
What a file can reveal
An EPUB packages documents and metadata together. Missing package information or broken reading-order references can explain a failed import. These checks can find obvious issues without rendering the book.
What still needs the device
Fonts, complex layouts, scripts, footnotes, and accessibility behavior depend on the reading system. A structurally readable file can still render poorly. Open several chapters and a navigation link on the real device.
Interpret protection markers carefully
An encryption declaration can describe font obfuscation rather than protected book text. The checker distinguishes known font-obfuscation algorithms from other declarations, but cannot establish every access restriction or reading entitlement.
The details, at a glance.
| Consider | What to look for |
|---|---|
| Archive | Recognizable ZIP and package location |
| Reading order | Manifest references and content files |
| Metadata | Title, creator, language, and identifier |
| Device fit | Reader-specific next steps, not a guarantee |
A few things worth asking.
Does a pass guarantee the book will work?
No. It means these limited checks did not find a blocking issue. Rendering still needs testing.
Does this remove DRM?
No. It reports relevant declarations without changing protection or file content.
Go to the source
Documentation consulted for the routes and terminology on this page. Product behavior can change; verify your exact setup.
W3C EPUB 3.3 specificationWritten by Binge Reader. Our comparisons explain documented workflows and practical tradeoffs; they are not independent product benchmarks.