What do EPUBCheck and PDF/X preflight actually check?

The file opened for you. That is only the first check.

An EPUB can open in one reader while containing structural, metadata, navigation, accessibility, or packaging problems that appear elsewhere. A PDF can display correctly on a laptop while using the wrong page size, missing production requirements, or failing a printer’s workflow. Independent authors often discover these issues late because the product that generated the file called it ‘ready’ without naming what was checked.

Tie the report to the edition you inspected

Preflight checks a particular exported file against defined expectations before submission or production. A meaningful report explains what was checked, the result, and any unavailable validation. BookSemantic keeps review information with the edition being prepared. That helps the author avoid assuming that yesterday's passing result covers a file changed today. The report does not compel retailer acceptance or establish every aspect of accessibility. Inspect the actual exported book, use the destination's preview, and consult its current submission guidance. If you replace an image or revise a section, review the new edition rather than reusing an old approval.

What EPUBCheck contributes

EPUB 3.3 is a W3C Recommendation defining conformance requirements for EPUB publications. The official EPUBCheck project checks EPUB files against the specification and reports errors and warnings. It can identify many package-level problems that casual opening will not reveal. BookSemantic's EPUB packages use native checks for document structure, navigation, resources, and links. Those checks are not an EPUBCheck result, third-party validation, or accessibility certification. Authors can seek an independent EPUBCheck review where their publication or destination requires it.

A passing EPUBCheck result is important evidence, not a complete reading-quality guarantee. The checker cannot decide whether a chapter heading is beautiful, an image is emotionally appropriate, alternative text conveys the intended meaning, a table is pleasant on a particular phone, or a retailer has added a proprietary intake rule. Authors should inspect navigation, change font size, test representative reading systems, review images, and run the destination platform’s preview. BookSemantic describes the result as validation against a named standard, not universal approval.

PDF/X is a family of print-production standards

PDF/X refers to ISO 15930 standards for graphic-technology exchange. Conformance involves more than readable pages. The appropriate variant and printer requirements affect color management, fonts, transparency, output intent, and other production properties. A product that merely checks page count and dimensions should not label the file PDF/X certified. That language creates false confidence at precisely the stage where reprints are expensive.

BookSemantic's native press workflow supports a bounded KDP paperback path with reviewed interior and full-wrap files and native PDF/X-1a checks for supported print profiles. It does not offer every printer profile or claim independent PDF/X certification. A normal PDF proof and a press package serve different purposes. Read the actual capability and preflight report for your selected edition, resolve its findings, and check the printer's current requirements. Do not infer that a supported KDP package is automatically appropriate for another printer, binding method, paper choice, or color workflow.

The report should belong to the artifact

Validation becomes stale as soon as the file changes. Replacing an image, adjusting a margin, updating metadata, or regenerating the interior produces a new artifact. A report that says ‘passed last Tuesday’ is ambiguous unless it can be tied to the file now being uploaded. A SHA-256 digest acts as a fingerprint: any changed byte produces a different digest. This is related to the fixity practices recommended in digital preservation guidance from the Library of Congress.

BookSemantic records the artifact digest in the preflight report included with the package. The practical benefit is traceability. The author, production partner, or support team can verify which output the messages describe. A digest does not prove authorship, copyright, or long-term preservation by itself. It answers a focused production question: is this report associated with this exact file?

Publishing preparation includes more than the manuscript file

Self-publishing portals ask for metadata, rights information, categories, keywords, price, publication date, cover assets, and—in some cases—information about AI-generated content. Requirements differ and can change. No honest package generator should claim a permanent universal disclosure rule. BookSemantic shows guidance for the selected platform, records the author’s actual text and image provenance choices, and asks the author to verify the current portal before submitting.

The platform also separates layout from submission. Authors choose book-appropriate trim, typography, paragraph treatment, chapter openings, and running elements; then they download files for manual upload. This respects the current reality that major self-publishing services do not offer a general public API for an independent third party to upload every author’s book. The author remains in control of the retailer account and final confirmation.

A practical pre-publication checklist

Build the package only after the manuscript, cover, metadata, and disclosure choices are current. Read the preflight report and resolve blocking findings before rebuilding. If the requested print profile is unavailable, preserve your work and use an appropriate printer workflow rather than treating a proof as a validated press file. Confirm trim and cover specifications with the selected destination. Preview the ebook on multiple screen sizes and the print interior page by page. Check navigation, front matter, chapter order, images, captions, alternative text, blank pages, running heads, references, and final metadata. Review a physical proof before committing to a print run.

BookSemantic does not market this work as one magical click. It markets a clearer handoff: the book’s approved content and design decisions remain connected, the package contains the expected components, validation is named rather than implied, and the author receives the files and evidence needed to make the final submission. A download is simply a file transfer. A preflight is a documented quality gate. Independent authors deserve to know the difference.

That clarity also protects the author when requirements change. The package preserves the metadata and disclosure answers used for a particular build, while the interface reminds the user to verify current destination guidance. If a platform changes a keyword limit, cover specification, or content questionnaire, the author can update the publishing record and rebuild rather than assuming an older package remains current. Preflight evidence, artifact identity, platform guidance, and human preview solve different problems; none should be presented as a substitute for the others. A professional workflow makes each boundary visible and gives the author the final submission decision.

The result is not merely a cleaner archive. It is a calmer launch: fewer unnamed files, fewer unsupported assumptions, and a clear record of the checks that were actually performed.

Use the report to find the next repair

An EPUBCheck validation guide is most useful beside the actual file and its report. Start with the named error, locate the affected item and understand what the check is telling you. An EPUB validator examines a particular exported artifact. Its result does not establish that the book is well edited or comfortable to read.

If you are learning how to fix EPUB validation errors, work through related problems together, export again and check the new file. Then open it in a reading application and inspect the table of contents, images and reading order. Keep technical validation and a reader's proof as complementary steps, not competing definitions of finished.