Find a useful place to start.
Select a batch of EPUBs to produce a local review report. The audit checks useful metadata and basic package structure. It does not edit files, assign invented metadata, or judge the quality of the writing.
Prioritize finding books
Start with missing titles and creators, then package errors that prevent inspection. Those affect basic retrieval. An optional field can be useful without being a defect when absent.
Read warnings as review tasks
A missing cover declaration does not necessarily mean the file contains no image. A missing series field may be entirely appropriate. Inspect the actual book before treating every observation as a correction.
Work in manageable batches
Use the PDF report as a small task list. Correct a few records in your chosen library editor, then re-run the audit on the exported copies. Keep a backup so cleanup remains reversible.
The details, at a glance.
| Consider | What to look for |
|---|---|
| Essential metadata | Title, creator, language, identifier |
| Cover declaration | Check for a declared cover resource |
| Series | Show available sequence metadata |
| Output | PDF findings per selected file |
A few things worth asking.
Is a missing series field an error?
No. Standalone books do not need one; it is displayed as context rather than a required correction.
Does this modify my metadata?
No. It reports observations. Use a separate editor to apply reviewed corrections.
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.