Tools/EPUB Inspector
EBOOK STRUCTURE & QUALITY

EPUB Inspector

Open an EPUB and understand what’s inside. Explore the reading order, table of contents, metadata, embedded resources, and potential packaging issues—all on your device.

✓ EPUB 2 & 3✓ No uploads✓ Export findings
▤

Inspection workspace

Choose one EPUB file to inspect its internal publication package.

Files never leave your browser

Drop your EPUB here

Or select an .epub file stored on your device.

ZIP-based EPUB · up to 100 MB · no account required

BUILT FOR REAL EPUB WORKFLOWS

Know your publication, inside and out.

A practical companion for authors, editors, publishers and ebook QA teams.

≡

Follow the reading order

See the spine and chapter excerpts, inspect EPUB 3 navigation and legacy NCX tables of contents.

▧

Audit archive resources

Explore images, fonts, stylesheets, documents and media files with file sizes and manifest paths.

◎

Spot common problems

Find missing package files, broken references, invalid metadata, navigation gaps and suspicious ZIP structures.

Frequently asked questions

Will PixelOkay upload or store my EPUB?

No. The file is read locally by your browser. The inspector does not send the book to any endpoint.

Does the inspector support EPUB 2 and EPUB 3?

Yes, it reads both EPUB 2 NCX navigation and EPUB 3 XHTML navigation where present. DRM-protected files and some encrypted resources cannot be decrypted.

Can I use this instead of EPUBCheck?

No. PixelOkay highlights common structural issues and helps explore contents; it does not perform full specification and accessibility conformance testing. Use official EPUBCheck for release certification.

Are chapters rendered as a reader would display them?

No. Chapter excerpts are deliberately plain text. Scripts, CSS, remote assets and embedded HTML are not executed or rendered by the preview.

Using EPUB Inspector

Inspect EPUB package structure, metadata, reading order and embedded resources, preview supported chapter text as inert content, and export findings.

Workflow

  1. Open a local EPUB and review package warnings
  2. inspect metadata, spine, navigation and available resource previews without activating book content
  3. export a structural report and download only the original resources you need.

Example

Inspect an EPUB spine and its navigation document, preview an available chapter as text, then export JSON findings and compare the reading order in a separate ebook reader.

Limits and data handling

This is bounded structural inspection, not EPUBCheck conformance, DRM removal or active ebook rendering. Chapter markup is inert and external book resources are not fetched. ZIP entry, CRC, expansion and resource caps can leave partial findings. Source text, images and reports may be confidential. Local module Worker and decompression behavior require browser/hosting acceptance.

FAQs

Does the inspector render an interactive ebook?

No. It previews supported content as inert text and does not run book scripts or follow actions.

Does a clean report certify EPUB standards compliance?

No. Use a dedicated conformance checker such as EPUBCheck for independent validation.

Related tools