Toolosaurus

Amazon KDP EPUB Validator & Kindle Checker

Inspect EPUB files 100% locally for Amazon KDP compliance: OPF container, table of contents (NCX/NAV), cover resolution, and formatting issues.

UtilityUpdated: October 2026

EPUB E-Book für Amazon KDP & Kindle validieren

Überprüft mimetype, OPF-Paket, Inhaltsverzeichnis (NCX/NAV), Cover-Auflösung & HTML/CSS-Reflow-Kompatibilität direkt im Browser.

Step-by-step

How Amazon KDP EPUB Validator & Kindle Checker Works

Inspect EPUB files 100% locally for Amazon KDP compliance: OPF container, table of contents (NCX/NAV), cover resolution, and formatting issues.

1

1. Upload or Drop EPUB E-Book File

Drag and drop your completed .epub publication into the validator window or select it via file explorer. The internal package contents and file manifest parse instantaneously.

2

2. Execute Comprehensive EPUB 3.3 Compliance Scan

The validation engine performs an in-depth audit: verifying the OPF package document, inspecting NCX and nav.xhtml navigation trees, validating MIME-type integrity, and parsing XHTML5 syntax.

3

3. Review Detailed Diagnostic Report & Warnings

Examine categorized technical errors and warnings regarding forbidden scripts, broken internal hyper-references, undeclared manifest items, or accessibility gaps.

4

4. Verify Kindle Previewer & Ingestion Compatibility

Ensure your e-book adheres to Amazon KDP ingestion requirements including reflowable responsiveness, fixed-layout metadata, RGB cover resolution, and E-Ink typography.

5

5. Export Validated, KDP-Ready EPUB

Apply automated structural fixes or update highlighted code sections and download your certified EPUB ready for seamless publication on Amazon KDP.

Key Benefits & Data Privacy

Full compliance testing against official W3C EPUB 3.3 and IDPF EPUB 2.0.1 specifications
Tailored Amazon KDP validation rules for flawless KFX and KF8 format conversion
Precise ZIP archive byte-structure inspection (mimetype at byte 0 without compression)
Comprehensive package verification: OPF manifest items, spine order, and dual NCX / nav.xhtml navigation
Detection of disallowed CSS styles, fixed pixel traps, and embedded executable scripts
Image asset analysis: sRGB vs. invalid CMYK profiles, dimension checks, and cover declarations
Automated accessibility conformance checks including WAI-ARIA roles and alt-text audits
100% confidential browser-based execution with zero remote server data transfers

Verified & Developed by the Toolosaurus Engineering Team

GDPR compliant processing • Strict browser privacy • Secure European server hosting

GDPR VerifiedISO 27001 Data Center
Practical Guide & Technical Insights

Everything You Need to Know About Amazon KDP EPUB Validator & Kindle Checker

The Architecture of EPUB 3.3: Understanding Modern E-Book Packaging

An EPUB 3.3 e-book is not a single file format, but an encapsulated web ecosystem packaged inside a ZIP archive. At the foundation of the e-book lies the Open Packaging Format (OPF) document, which acts as the master manifest. It inventories every XHTML text chapter, CSS stylesheet, embedded font, and visual image. The Spine element dictates the linear reading flow of chapters. In EPUB 3.3, navigation is driven by a semantic HTML5 file (nav.xhtml), which is interpreted by screen readers and reading software to build dynamic tables of contents and landmark menus. If even one file is declared in the manifest but missing from the archive—or conversely, if unmanifested orphan files reside inside the container—the e-book is deemed invalid. Our validator parses every XML node, namespace declaration, and schema constraint to guarantee perfect structural integrity.

Kindle Ingestion Mechanics: KFX, KF8, and Enhanced Typesetting Criteria

Uploading an EPUB to Amazon KDP triggers an automated cloud conversion pipeline that converts the source into Amazon’s proprietary formats, primarily KFX (featuring Enhanced Typesetting) and legacy KF8 (AZW3). Generic EPUB validators often miss Kindle-specific pitfalls. For instance, Amazon strongly expects both modern EPUB 3 nav.xhtml and backward-compatible EPUB 2 toc.ncx to ensure consistent navigation across decades of legacy Kindle hardware. Furthermore, Amazon’s ingestion system strictly flags uppercase characters or special symbols in internal file paths. Hardcoding font sizes in absolute pixels disables Enhanced Typesetting features such as hyphenation, drop caps, and kerning pairs. Our validator replicates these KDP ingestion checks, flagging hidden incompatibilities before you initiate publishing.

Reflowable vs. Fixed Layout: CSS and Viewport Engineering for Kindle

Choosing between Reflowable and Fixed Layout (FXL) dictates how your e-book responds to different reading environments. For novels, narrative non-fiction, and poetry, Reflowable Layout is the gold standard, granting readers full autonomy to adjust font size, margins, and background lighting. To support this fluidity, CSS stylesheets must avoid fixed pixel heights or rigid container widths that cause overlapping text blocks on smaller screens. Images must be engineered using responsive percentages (`max-width: 100%; height: auto;`). In contrast, children picture books, graphic novels, and complex technical manuals require Fixed Layout (FXL). This demands explicit OPF metadata declarations, such as `rendition:layout = pre-paginated` and strict viewport coordinates. Our validator audits your CSS and metadata to prevent rendering defects on both E-Ink paper displays and high-resolution tablet screens.

Digital Accessibility and Validation Security: EAA Compliance and WAI-ARIA

With the enforcement of the European Accessibility Act (EAA) and global publishing mandates, digital accessibility is now a vital publishing requirement. EPUB 3.3 provides powerful semantic tools to empower readers with visual impairments. Incorporating WAI-ARIA roles (`role="doc-chapter"`, `role="doc-footnote"`) and structural HTML5 elements allows assistive text-to-speech engines to navigate footnotes, sidebars, and subheadings effortlessly. Missing descriptive alternative text on critical graphics or language mismatches (`xml:lang`) between chapter files directly impair accessibility. Our validator inspects accessibility declarations across the entire file package. Because the entire auditing process runs strictly on-device inside your browser using WebAssembly, your valuable literary works and unreleased commercial manuscripts remain 100% private.

FAQ

Frequently Asked Questions

Topic Cluster

Related Tools

View all 50 tools