How to Create a Digital Book: Complete Technical Workflow 2026

Last updated: July 31, 2026

The question "how to create a digital book" has a much more technical answer today than it did a year ago. In 2026, editorial standards have consolidated (EPUB 3.2 is the baseline), accessibility is a legal requirement in Europe (European Accessibility Act), and platforms have introduced stricter validation checks. Creating a digital book no longer means just writing and exporting to PDF: it means mastering a technical workflow that goes from manuscript structuring to multi-format validation, through standards compliance.

This guide focuses on the operational and technical aspects of creation: which standards to use, which formats to produce, how to validate files and which tools to integrate into your workflow. It's not a guide to creative writing or marketing (you'll find specific links at the bottom): it's the technical manual for those who want to produce a digital book that passes platform checks and works correctly on every device.

The technical landscape of digital books in 2026
Editorial standards: EPUB 3.2 as baseline
Formats: the complete matrix
Technical workflow step by step
Accessibility: EAA compliance
Validation tools
Technical metadata and ONIX
AI disclosure and platform compliance
How this differs from other blog articles
FAQ - Frequently Asked Questions

The Technical Landscape of Digital Books in 2026

The global digital book market is worth approximately $18 billion in 2026, with steady 4-5% annual growth. But the numbers matter less than the technical rules governing production. Here are the three main changes that directly impact the creation workflow:

EPUB 3.2 is the de facto standard. The IDPF (International Digital Publishing Forum) merged into W3C in 2017, and EPUB 3.2 is now a W3C Recommendation. All major platforms support it, and many explicitly require this standard for new uploads.
Accessibility is legally mandatory in Europe. The European Accessibility Act (EAA), which came into force on June 28, 2025, requires all ebooks sold in the European Union to meet specific accessibility requirements. It's no longer a matter of best practice: it's legal compliance.
Platforms have tightened validation checks. Amazon KDP, Apple Books and Kobo automatically reject files with structural errors. An EPUB that passes a visual check but fails epubcheck gets discarded without appeal.

These three factors make the technical creation workflow more rigorous than in the past. If in 2024 a Word export and an upload were enough, in 2026 you need a structured process with multi-level validation.

Editorial Standards: EPUB 3.2 As Baseline

EPUB 3.2 isn't a minor evolution from EPUB 2.0.1: it introduces features that change how you structure and produce content.

What EPUB 3.2 supports

Embedded audio: you can embed audio files directly in the EPUB, useful for guided readings, pronunciations or multimedia content.
Native MathML: for technical, scientific or academic books with mathematical formulas.
SVG for charts and vector illustrations: perfect quality at any zoom level, ideal for manuals and illustrated books.
Fixed and reflowable layouts: fixed-layout (similar to PDF but with EPUB advantages) for books with critical pagination, reflowable for fiction and non-fiction.
Limited JavaScript scripting: for light interactivity (quizzes, calculators, widgets).
WCAG 2.1 compliance: the standard requires metadata and structure that support accessibility.

How to produce a compliant EPUB 3.2

The most reliable approach is to start from a well-structured Markdown or HTML manuscript and use a converter that generates native EPUB 3.2. Pandoc (version 3.x) is the most robust command-line tool:

pandoc manuscript.md -o book.epub --epub-metadata=metadata.xml --epub-cover=cover.jpg --toc

If you use a visual editor, Calibre 7.x supports EPUB 3.2 export with integrated validity checking. Avoid producing in EPUB 2.0.1 and then "upgrading": the result is almost always a file with structural errors.

Formats: The Complete Matrix

In 2026, creating a digital book means producing at least three formats to cover all platforms and devices. Here's the updated matrix:

Platform	Required format	Generated from	Tool
Apple Books	EPUB 3.2	EPUB master	Pandoc / Calibre
Amazon KDP	KF8 (.kpf)	EPUB 3.2	Kindle Previewer 3
Kobo	EPUB 3.0+	EPUB master	Calibre / Sigil
Google Play Books	EPUB 3.2	EPUB master	Pandoc / Calibre
Bibliotheca / OverDrive	EPUB 3.2	EPUB master	Pandoc / Calibre
Own website (download)	PDF + EPUB	EPUB master	Calibre (EPUB→PDF)

The master format is EPUB 3.2

The correct strategy is to produce a single master file in EPUB 3.2 and generate all other formats from it. This avoids maintaining multiple sources and ensures consistency across versions. From this master:

Kindle Previewer 3 converts to KF8 for Amazon.
Calibre converts to EPUB 2.0.1 for legacy platforms (if needed).
Calibre or PrinceXML generates PDF for direct download.

PDF remains useful, but with limitations

PDF is the universal format for print and for those who want fixed pagination, but it's not an optimal digital reading format. On e-readers and smartphones, text doesn't resize and the experience is inferior to EPUB. Produce PDF as a complementary format, not as your base.

Technical Workflow Step by Step

Here's the operational flow for creating a digital book in 2026, from source to upload-ready file.

Phase 1: Manuscript preparation

Start from a well-structured Markdown or HTML file. The structure must respect a clear hierarchy:

# Book Title

## Chapter 1: Introduction
### 1.1 Context
### 1.2 Objectives

## Chapter 2: Fundamentals
### 2.1 Basic concepts
### 2.2 Required tools

## ...

If you start from Word or Google Docs, export to Markdown before proceeding. Direct conversion from DOCX to EPUB often produces structure errors.

Phase 2: EPUB master generation

Use Pandoc or Calibre to generate the EPUB 3.2 from the manuscript:

pandoc manuscript.md \
  -o book.epub \
  --epub-metadata=metadata.xml \
  --epub-cover=cover.webp \
  --toc \
  --toc-depth=2 \
  --epub-chapter-level=2

The metadata.xml file contains Dublin Core metadata (title, author, language, identifier, date). Example:

<metadata xmlns:dc="http://purl.org/dc/elements/1.1/">
  <dc:title>Book Title</dc:title>
  <dc:creator>Author Name</dc:creator>
  <dc:language>en</dc:language>
  <dc:identifier id="BookId">urn:uuid:XXXXX</dc:identifier>
  <dc:date>2026-07-31</dc:date>
</metadata>

Phase 3: Structural validation

Run epubcheck 5.x on the generated file:

java -jar epubcheck.jar book.epub

epubcheck identifies structural errors, XHTML validity issues, missing metadata and broken links. Fix all errors before proceeding: platforms reject files with epubcheck errors.

Phase 4: Accessibility verification

Use Ace by DAISY for accessibility audits:

ace book.epub -o accessibility-report

Ace verifies presence of text alternatives, correct heading structure, accessibility metadata and WCAG 2.1 compliance. Reports indicate critical errors, warnings and suggestions.

Phase 5: Derivative format generation

From the validated EPUB 3.2 master:

Kindle: open the file in Kindle Previewer 3, verify rendering on Paperwhite/Scribe/Oasis, export to KPF.
PDF: use Calibre or PrinceXML to generate a professionally paginated PDF.
EPUB 2.0.1 (if required): Calibre converts with ebook-convert book.epub book-epub2.epub --epub-version=2.

Phase 6: Upload and final verification

Upload each format to the target platform and verify rendering on a real device (not just in preview). A technically valid file can still have rendering issues on specific readers.

Accessibility: EAA Compliance

The European Accessibility Act (EAA) came into force on June 28, 2025 and imposes precise requirements for ebooks sold in the EU. In 2026, compliance is not optional.

EAA technical requirements for ebooks

Structured navigation: the book must have a working table of contents (TOC) and semantically correct heading hierarchy (H1, H2, H3).
Resizable text: content must adapt to increased text sizes without loss of information or functionality.
Text alternatives for images: every image must have descriptive alt text (or aria-label for interactive elements).
Accessibility metadata: the EPUB file must include schema:accessibilityFeature, schema:accessMode and schema:accessibilitySummary metadata.
Adequate contrast: text and background must respect WCAG 2.1 AA contrast ratio (4.5:1 for normal text).

How to verify compliance

Use Ace by DAISY (see Phase 4 of the workflow) to generate an accessibility report. Ace automatically identifies:

Images without alt text.
Headings not in sequence (e.g., H1 → H3 without H2).
Missing accessibility metadata.
Contrast issues (if the file includes inline CSS).

EAA compliance is the publisher's (or self-published author's) responsibility. Sanctions vary by member state, but can include store removal and fines.

Validation Tools

The essential toolkit for creating a professional digital book in 2026:

epubcheck 5.x

The de facto standard for EPUB validation. Verifies standard compliance, file structure, metadata and links. Available as command-line tool (Java) or as Calibre and Sigil plugin.

Installation:

# Download from https://github.com/w3c/epubcheck/releases
java -jar epubcheck-5.1.0.jar book.epub

Ace by DAISY

Accessibility audit tool developed by the DAISY Consortium. Generates detailed HTML reports with errors, warnings and suggestions.

Installation:

# Download from https://daisy.github.io/ace/
ace book.epub -o report

Kindle Previewer 3

Official Amazon tool for verifying rendering on Kindle devices. Converts EPUB to KF8 and allows preview on Paperwhite, Scribe, Oasis and Kindle apps.

Download: free from Amazon KDP.

Calibre 7.x

Complete ebook manager with conversion, metadata editing and validation features. Useful for EPUB→PDF conversions, EPUB 3.2→EPUB 2.0.1 and quality checks.

Sigil

Open source EPUB editor for manual modifications to the EPUB's XHTML and CSS code. Useful for specific fixes that automatic converters don't handle correctly.

Technical Metadata and ONIX

Metadata isn't just "title and author": in 2026 it includes technical, accessibility and distribution information that affects discoverability and compliance.

Dublin Core metadata (in the EPUB's OPF file)

<metadata xmlns:dc="http://purl.org/dc/elements/1.1/"
          xmlns:opf="http://www.idpf.org/2007/opf">
  <dc:title>Book Title</dc:title>
  <dc:creator opf:role="aut">Author Name</dc:creator>
  <dc:language>en</dc:language>
  <dc:identifier id="BookId">urn:uuid:XXXXX</dc:identifier>
  <dc:publisher>Publisher Name</dc:publisher>
  <dc:date>2026-07-31</dc:date>
  <dc:subject>category1</dc:subject>
  <dc:description>Book description</dc:description>
</metadata>

Accessibility metadata (required by EAA)

<meta property="schema:accessibilityFeature">tableOfContents</meta>
<meta property="schema:accessibilityFeature">readingOrder</meta>
<meta property="schema:accessibilityFeature">structuralNavigation</meta>
<meta property="schema:accessibilityFeature">alternativeText</meta>
<meta property="schema:accessMode">textual</meta>
<meta property="schema:accessMode">visual</meta>
<meta property="schema:accessibilitySummary">This ebook complies with WCAG 2.1 AA requirements and includes structured navigation, text alternatives and resizable text.</meta>

ONIX for advanced distribution

If you distribute through aggregators (Draft2Digital, StreetLib, IngramSpark), you may need to provide metadata in ONIX format (ONline Information eXchange). ONIX is the international standard for editorial metadata and includes information on price, rights, format, subject codes and target audience.

Most aggregators handle the conversion from EPUB metadata to ONIX automatically, but for direct distribution to bookstores you may need to provide a complete ONIX XML file.

AI Disclosure and Platform Compliance

In 2026, all major platforms require mandatory disclosure of AI-generated or AI-assisted content.

Amazon KDP

KDP requires you to declare whether content is:

AI-generated: text was generated entirely by AI without substantial human modification.
AI-assisted: AI was used as a support tool, but the final content was reviewed and modified by the author.

Disclosure occurs during the KDP upload process. Failure to declare can lead to book removal or account suspension.

Apple Books and Kobo

Apple Books and Kobo have also introduced similar policies in 2025-2026. The trend is toward total transparency on AI use in editorial content creation.

How to handle disclosure

If you used AI tools in the creation process:

Always declare AI use during upload.
Document your workflow: keep track of which parts were AI-generated and which were revised.
Maintain creative control: even if you use AI, the final content must reflect your voice and expertise.

Disclosure doesn't penalize sales: readers in 2026 are accustomed to AI use and appreciate transparency.

How This Differs From Other Blog Articles

This article focuses on the technical-operational aspect of creating a digital book. If you're looking for information on other aspects of the editorial process, here are the specific guides:

How to write and sell an ebook: focus on idea validation, pricing strategy, launch and marketing.
What is AI writing and how to use it: focus on prompt engineering, AI writing techniques and maintaining authorial voice.
AI book maker: complete guide: focus on using the booksmaker.ai platform to create books with AI.
How to sell books on Amazon: focus on KDP, ranking strategies and product page optimization.

This article is the technical complement: it tells you how to produce the files you then upload to platforms. The other articles tell you what to write, how to sell it and how to promote it.

Conclusion

Creating a digital book in 2026 requires technical competence as well as creative skill. The EPUB 3.2 standard, EAA accessibility compliance and platform validation checks require a structured and rigorous workflow. But once the process is mastered, production becomes repeatable and scalable: you can create a system that turns every manuscript into a professional digital book, ready for global distribution, in days instead of weeks.

The starting point is simple: download epubcheck and Ace by DAISY, produce your first compliant EPUB 3.2 and validate it. From there, the workflow refines with practice.

FAQ - Frequently Asked Questions

What EPUB standard should I use to create a digital book in 2026?

The current standard is EPUB 3.2, adopted by the IDPF (now part of W3C). It supports embedded audio, MathML, SVG, fixed and reflowable layouts, and requires WCAG 2.1 compliance for accessibility. EPUB 2.0.1 is still accepted by platforms but is deprecated: produce directly in 3.2 to ensure future compatibility and access to stores that require accessibility metadata.

How to create an accessible digital book under the European Accessibility Act?

Since June 28, 2025, the European Accessibility Act (EAA) requires all ebooks sold in the EU to be accessible. You must include: structured navigation via table of contents (TOC NCX and nav), resizable text without content loss, text alternatives for images, accessibility metadata (schema:accessibilityFeature, schema:accessMode) and adequate contrast. Tools like Ace by DAISY automatically verify compliance.

How to create a digital book for Kindle in 2026?

Amazon requires the KF8 (Kindle Format 8) format for new titles. You can generate it from EPUB 3.2 using Kindle Previewer 3 or kindlegen from the command line. The classic MOBI/AZW3 format is no longer accepted for new uploads since 2024. Kindle Previewer also validates rendering on specific devices (Paperwhite, Scribe, Oasis) and automatically generates the KPF file ready for KDP.

What validation tools should I use for a digital book?

The essential toolkit in 2026 includes: epubcheck 5.x for EPUB structural validation, Ace by DAISY for accessibility audits, Kindle Previewer 3 for Amazon device rendering verification and Calibre for quality checks and conversion. Always run all four checks before uploading: every platform rejects invalid files and some blocks are irreversible.

How long does it take to create a digital book in 2026?

With AI tools and preconfigured templates, a short ebook (15,000-25,000 words) can be created in 1-2 weeks, including the technical validation cycle. A substantial manual or illustrated book requires 4-8 weeks due to layout, image and metadata complexity. The technical phase (formatting, validation, error fixes) accounts for about 20-30% of total time.

📌 Have more questions? Check out our complete FAQ on how to create books with Books Maker to find all the answers about features, pricing, publishing, and more.

About Books Maker: Our team is made up of AI professionals. Together with expert writers and authors, we created booksmaker.ai to help our users achieve their publishing dreams by leveraging the power of Artificial Intelligence tools for every stage of the process, from idea to book creation.

Stay updated with our newsletter

Table of Contents