31 / Optimize · EPUB → Report

EPUB publish check

Know what to fix before you upload.

Uploading a book only to have it rejected — or published with a missing language or a 300-pixel cover — costs a day and a review cycle. This check walks the package the way a store will: it reads the metadata, measures the cover, parses the table of contents, confirms the reading order, follows every internal link, looks for fonts that are not embedded, images without alt text and scripts that reading systems block, and lists external links without opening them. Each result says where the problem is and how to fix it, and the verdict tells you how many items stand between the book and publishing. It is a practical pre-flight, not a replacement for EPUBCheck.

All tools
Opening your workspace…

From file to finished

How to use this tool

  1. Choose a DRM-free EPUB, or try the sample book.

  2. Read the verdict and the error, warning and note cards; each card names the file or OPF line and the fix.

  3. Download the JSON for a full machine-readable record or the HTML report to keep, print or share.

The checks that block an upload

Missing title, language, identifier or author; a missing, small, oddly shaped or oversized cover; no table of contents; an empty spine; internal links to files that are not in the book; unembedded fonts; images without alt text; <script> elements; and a list of external http links.

A location and a fix for every finding

Errors, warnings and notes are separated, and every card gives the evidence (OPF element or line, chapter file, image path, URL) plus a concrete repair step instead of a bare rule number.

JSON and a self-contained HTML report

The JSON contains summary counts, the verdict and the full check table for your own tooling. The HTML report inlines its styles, uses severity colours and stays readable on a phone, with no remote assets.

A little more detail

Frequently asked questions

Is my book uploaded?

No. The EPUB is opened, measured and reported in this browser; nothing is sent to a server and the file is not changed.

Does this replace EPUBCheck?

No. EPUBCheck validates the EPUB specification in depth. This tool answers a narrower question — what a store is likely to reject or ask you to fix — and says so on the page and in both reports. Run EPUBCheck and the store’s previewer before publishing.

What is the difference between an error, a warning and a note?

An error blocks publishing in this check: a missing required metadata field, no cover, a broken internal link, a script, or an unreadable chapter. A warning should be reviewed before uploading: a cover below 600 px on its short edge, an off-2:3 ratio, a missing author, an unembedded font, a missing anchor or an empty table of contents. A note is optional: images without alt text, external http links, or an identifier that is not an ISBN, UUID or URL. Errors and warnings count toward the “items to publish”; notes do not.

How is “distance to publish” counted?

It is the number of errors plus warnings. The verdict is “Not ready to publish” with any error, “Almost ready to publish” with warnings only, and “Ready to publish” when both are zero. Notes remain visible but do not block the verdict.

What does the JSON report contain?

The tool name and version, the generation time, the file and book details, a summary with error, warning, note and passed counts, the verdict, and a checks array. Every check has a title, severity, location, problem, fix and optional detail list.

Are the external links opened?

No. The report lists each external http(s) URL with its chapter and line so you can review it, but the check makes no network requests.

Which cover sizes pass?

The short edge must be at least 600 px, the ratio should be 2:3 within a small tolerance, and the file must be 2 MB or less. A larger cover, a different ratio or a smaller short edge is reported with the recommended target.