What’s in your EPUB?
Choose an EPUB to inspect its package metadata. This tool reads metadata locally; it does not edit the file, upload the book, or render its text. You can download the extracted fields in a branded PDF report.
What metadata can tell you
The title printed on a cover and the title stored in a package can differ. Readers often use the package fields for sorting. Inspecting them explains why a sensible filename still produces an unexpected library entry.
What this viewer checks
The viewer locates the EPUB package, extracts common descriptive fields, and lists structural observations. Series metadata is not equally represented in all books; an absent field does not prove the book is not in a series.
Use the result carefully
Missing fields are a reason to review the source, not to guess an author or edition. Keep the original file and use a trusted editor if you want to correct it. This tool deliberately leaves your book unchanged.
The details, at a glance.
| Consider | What to look for |
|---|---|
| Identity | Title, author, identifier, and language |
| Organization | Series and sequence when present |
| Package | EPUB version and reading-order entries |
| Export | Download metadata as PDF |
A few things worth asking.
Are my books uploaded?
No. File inspection runs in this browser. File contents and names are not sent to analytics.
Does it modify the EPUB?
No. The downloaded PDF is a separate report. Your original ebook is untouched.
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.