EPUB Book Metadata & TOC Inspector
EPUB Book Metadata & TOC Inspector: Unzips EPUB container, parses `META-INF/container.xml`, `content.opf`, and NCX/Nav table of contents.
About this epub book metadata & toc inspector
EPUB Book Metadata & TOC Inspector — browser-based utility.
How this tool works
Implements client-side EPUB Book Metadata & TOC Inspector operations. Unzips EPUB container, parses `META-INF/container.xml`, `content.opf`, and NCX/Nav table of contents specifically designed for an e-book publisher inspects the internal metadata, table of contents, and cover image of an epub publication.
- Container Unpacking & XML Navigation: Unpacks the EPUB/iCalendar file stream, parsing root XML structures and calendar VEVENT blocks.
- Metadata & Spine Extraction: Extracts Dublin Core book metadata, manifest items, and spine reading order, or parses recurrence rules (RRULE).
- Content Transformation: Strips HTML formatting from XHTML book chapters to produce clean Markdown, or maps vCard contact fields to QR codes.
- Diagnostic Reporting: Reports broken manifest links, missing spine references, and calendar timezone offsets.
Worked example
Scenario: Inventory a four-entry EPUB-like ZIP.
Sample input:
Processing: Count entries, filter HTML/XHTML names, and check the container path.
Illustrative output:
Limits and verification
DRM-encrypted EPUB books (protected by Adobe Adept or FairPlay) must have encryption removed before inspecting contents. iCalendar parser supports standard recurrence rules (RRULE); complex EXDATE exclusions are noted.
Examples demonstrate an expected workflow; they do not prove every input or every branch of an external specification. Check important results with an independent source before using them for money, security, compliance, safety, or irreversible file changes.
Browser processing boundary
Tool input is processed by code running in the browser and is not intentionally sent to a CZOA processing API. The page can still request ordinary site assets, analytics, or advertising when those services are enabled. Browser extensions and managed-device software remain outside this tool's control.
Relevant references
These references govern or help explain the format, protocol, or calculation used here. Listing a reference does not claim certification or complete implementation of every optional feature.
Content owner: CZOA Tools · Last reviewed: 2026-09-15 · Review methodology
How to use it
- Enter, paste, or select your input data into the EPUB Book Metadata & TOC Inspector workspace controls.
- Review available parameter fields, units, formats, or options configured for your task.
- Click the action button or observe immediate live calculations rendered in your browser runtime.
- Inspect the resulting output and any diagnostic messages, then copy or download the result if needed.
Frequently asked questions
How does EPUB Inspector inspect a selected file?+
It unzips the selected archive, counts every entry name, returns names ending in .xhtml, .html, or .htm as chapters, and reports whether META-INF/container.xml is present. It does not parse the XML contents.
Which controls and result are available?+
The page offers one local file chooser and Process locally. The result is JSON with files, chapters, and hasContainer. There is no title, author, language, ISBN, cover, table-of-contents, spine, metadata, extraction, repair, encryption, or DRM control.
What archive and interpretation limits apply?+
The chapter list is only a filename-suffix filter in archive enumeration order. It does not validate an EPUB package, read content.opf or navigation documents, identify reading order, parse XHTML, inspect media, distinguish real chapters, or recover malformed and encrypted ZIP archives.
What did isolated browser verification establish?+
A local browser run inspected an independently authored four-entry ZIP containing META-INF/container.xml, two OEBPS HTML/XHTML names, and content.opf. It returned files 4, exactly those two chapter names, and hasContainer true; recorded requests carried no fixture data.