How to Create an Epub from Word or Markdown in 2026

Creating an epub from your manuscript is the first step to publishing an ebook on Kindle, Kobo, Apple Books or any self-publishing platform in 2026. Yet most authors don't know where to start: which software to use, how to structure the file, why their epub displays incorrectly on some readers, what to do when KDP rejects the upload.

This guide covers everything from manuscript preparation to exporting a valid epub, choosing between Folio Studio, Calibre, Pandoc and Sigil, uploading to each major platform, fixing the most common validation errors, and ensuring your ebook displays correctly across Kindle, Kobo, Apple Books, and dozens of other readers.

Quick Answer: How to Create an Epub in 2026

In short: the fastest path is to import your Word or Markdown manuscript into Folio Studio, Vellum (Mac) or Atticus, pick a template and export as EPUB3. Free alternatives include Calibre (DOCX or Markdown to epub conversion) and Pandoc for command-line workflows. Once exported, validate with EPUBCheck before uploading to KDP, Kobo or Apple Books. The full guide below walks through manuscript preparation, the 4 main tools compared, platform-by-platform upload tips and the most common validation errors with their fixes.

What Is an Epub File?

An epub (Electronic Publication) is a compressed archive containing your book's text, layout, metadata (title, author, language) and table of contents. It's the standard ebook format, used by Kobo, Apple Books, Barnes & Noble, and most digital libraries.

Amazon Kindle historically used its own format (MOBI/KFX), but since 2022 KDP accepts epub directly. You no longer need to convert your epub to MOBI to publish on Amazon.

A valid epub conforms to the EPUB3 specification, the most widely supported version today. A malformed epub may be rejected by a platform or display incorrectly. The 2025 European Accessibility Act (EAA) also added accessibility requirements for ebooks sold in the EU, which EPUB3 supports natively when produced with a quality tool. For more on this, see our epub vs PDF complete guide.

Preparing Your Manuscript Before Export

Regardless of the method used, a few preparation rules apply.

Chapter structure

Each chapter must be identifiable by a title. In Word, use the "Heading 1" style for main chapters. In Markdown, start each chapter with a # Chapter title line. Without this structure, the epub's table of contents will be empty or broken. See our Markdown guide for authors for the full syntax reference.

Minimal formatting

Avoid complex formatting: tables, text boxes, multiple columns. These don't translate well to epub. Keep: bold, italic, scene separators (three asterisks *** or dashes ---), lists where necessary.

Metadata

Prepare your book's exact title, your author name, the language and ideally an ISBN if you have one. This information will be embedded in the epub file and displayed by online retailers. See our ISBN guide if you need one.

Images

If your manuscript contains images (illustrated novel, cookbook, guide), confirm they are embedded in the Word file (not linked to an external folder). Each image should be saved at 72-150 DPI for epub (higher DPI inflates file size without improving on-screen quality).

Typographic quotes

Convert straight quotes (") to curly quotes (") before exporting. Most modern tools auto-correct on input; verify the auto-correct is enabled in your editor.

Which Method Should You Use? Folio Studio vs Calibre vs Pandoc vs Sigil

Choosing the right tool saves hours of debugging. Here's the quick comparison.

For most self-published authors: Folio Studio is the recommended path. The free tier covers basic epub export, and the $9/month Pro tier adds print-ready PDF and DOCX exports. It accepts Markdown, Word and PDF as input, applies typographic templates, validates output, and produces EAA-compliant epubs by default.

For Mac authors with budget: Vellum is the historical reference. Pricier but excellent quality. See our Vellum alternatives guide for cross-platform options.

For technical authors automating a workflow: Pandoc + a custom CSS stylesheet, integrated into a CI/CD pipeline.

For one-off conversion without quality requirements: Calibre is fine.

Creating an Epub from Word

Method 1: Folio Studio (recommended)

Folio Studio accepts .docx file imports directly.

1. Open Folio Studio and create a new project
2. Click "Import" and drop your .docx file
3. Folio Studio automatically detects your chapters (H1/H2 headings) and structures them
4. Choose a typographic template from the 15 available
5. Adjust the preview if needed (fonts, spacing, ornaments)
6. Click "Export to epub"

The generated epub includes an automatic table of contents, project metadata and the chosen layout. It's EPUB3-compliant by default and passes EPUBCheck validation.

Method 2: Calibre (basic conversion)

Calibre is a free ebook manager that can convert .docx to epub. The typographic quality is limited: no templates, generic layout.

1. Open Calibre, drag your .docx in
2. Right-click > "Convert books"
3. Choose epub as output, adjust metadata
4. Run the conversion

Calibre works if you need a quick conversion without layout requirements.

Method 3: Sigil (for advanced users)

Sigil lets you edit an epub directly in HTML/CSS. It's the ideal tool if you want total control, but the learning curve is steep. Not suitable for authors who want a simple workflow.

Typical use case: you produced an epub with Folio Studio or Calibre, but want to tweak a specific page's CSS, fix an obscure validation error, or add a custom feature (manual page list, complex semantic markup).

Creating an Epub from Markdown

Markdown is a plain text format with lightweight syntax. An author who writes in Markdown (in Obsidian, Typora, iA Writer or VS Code) can export to epub without going through Word.

Method 1: Folio Studio

Folio Studio imports .md files natively.

1. Create a new project in Folio Studio
2. Import your Markdown file (or drag it to the import area)
3. Chapters are detected by # and ## headings
4. Select a template, preview in real time
5. Export to epub

If your manuscript is split across multiple Markdown files (one per chapter), import them one by one: Folio Studio adds them in order and handles numbering.

Method 2: Pandoc (command line)

Pandoc is a universal command-line converter. Powerful but technical.

pandoc manuscript.md -o book.epub --metadata title="My Book" --metadata author="First Last"

For an epub with table of contents:

pandoc manuscript.md -o book.epub --toc --toc-depth=2 --metadata title="My Book"

With a custom CSS stylesheet:

pandoc manuscript.md -o book.epub --css=style.css --metadata title="My Book"

Pandoc produces a valid epub, but the layout is minimal. For polished typographic output you need to provide a custom CSS stylesheet, which requires CSS knowledge.

Pandoc suits technical authors who want to automate epub generation in a pipeline.

Handling Images, Tables and Special Characters in Your Epub

These three areas cause the most epub headaches. Here's how each tool handles them.

Images

In Word (Folio Studio import): images embedded in your .docx are extracted automatically and included in the epub. Folio Studio resizes oversized images (anything above 1500px wide) to save file size without visible quality loss on e-readers.

In Markdown: use the syntax ![alt text](path/to/image.jpg). The image file must be accessible at the path when you import. Folio Studio reads relative paths from the import folder.

Best practices: 800-1200px wide is plenty for e-readers. JPG for photos, PNG for diagrams with text. Always add meaningful alt-text for accessibility (EAA 2025 requirement).

Tables

Tables are problematic in reflowable epub because the table width is fixed but the screen width is variable. On a smartphone Kindle app, a 4-column table is unreadable.

Best practices: avoid tables in novels. For non-fiction, restructure as bullet lists when possible. If a table is essential, keep it to 2-3 columns max with short cell content.

Folio Studio: tables are rendered as semantic <table> elements in epub. They display correctly on tablets but degrade on small phone screens.

Pandoc: handles Markdown table syntax (pipe tables) directly and outputs clean HTML tables.

Special characters

Unicode characters (curly quotes, em dashes, foreign accents, em spaces): all handled natively in EPUB3 with UTF-8 encoding. Folio Studio, Calibre and Pandoc all default to UTF-8.

Mathematical symbols: use MathML for equations in EPUB3. Pandoc supports this via --mathml flag. Folio Studio renders MathML in supported readers (Apple Books, some Kobo) but falls back to image rendering for Kindle.

Emojis: supported in modern epub readers, fall back to character codes on older devices. Avoid for narrative text in fiction (readers may see boxes instead of emojis).

Uploading Your Epub to Amazon KDP, Kobo, Apple Books

Each platform has its own quirks for epub uploads. Here's what to expect.

Amazon KDP

1. Log in to kdp.amazon.com
2. Click "+ Create" > "Kindle eBook"
3. Fill in title, author, description, keywords, categories
4. Upload your epub in the "Manuscript" section
5. KDP runs automatic validation (checks file size, basic structure)
6. Preview using Kindle Previewer (downloadable from KDP)
7. If valid, KDP converts your epub to internal Kindle format (KFX) automatically

KDP quirks: file size limit 650 MB. KDP's "spell check" sometimes flags character names as errors (you can ignore). KDP doesn't accept DRM-protected epubs.

Kobo Writing Life

1. Log in to writinglife.kobobooks.com
2. Click "Create a New eBook"
3. Fill in metadata, upload your epub
4. Kobo accepts EPUB2 and EPUB3
5. Preview is automatic

Kobo quirks: very lenient on validation. Even epubs with minor errors are usually accepted. Royalty: 70% in standard price ranges.

Apple Books

1. Sign in to iTunes Connect (or use a publishing aggregator like Draft2Digital)
2. Use iTunes Producer (Mac only) or an aggregator to upload
3. Apple runs strict validation: EPUB3-compliant, EAA-compliant, no broken images

Apple quirks: the strictest validation of the three. An epub that passes Apple Books is virtually guaranteed to pass everywhere else.

Draft2Digital (aggregator)

1. Sign in to draft2digital.com
2. Upload your epub or Word file (D2D will convert)
3. Choose distribution platforms (Apple, Barnes & Noble, Kobo, Scribd, OverDrive, etc.)
4. D2D handles upload to each platform

Best for: authors who want maximum distribution without managing 5+ platform accounts.

Validating Your Epub Before Publishing

Before submitting your epub to a platform, check it with these two free tools.

EPUBCheck

EPUBCheck is the official EPUB specification validator. It flags any error that might prevent your epub from being accepted on KDP, Kobo or Apple Books. Available online at validator.idpf.org or as a command-line tool.

Calibre or Foliate

Open your epub in Calibre (Windows/Mac/Linux) or Foliate (Linux) to check the actual display: table of contents, chapter navigation, font rendering, scene separators.

Kindle Previewer

Free Amazon tool that shows how your epub will render on different Kindle devices (Paperwhite, Oasis, Kindle app on iPhone/Android). Catches Kindle-specific issues that EPUBCheck misses.

An epub that passes EPUBCheck and displays correctly in Calibre + Kindle Previewer will work on virtually all readers and platforms.

Common Epub Validation Errors and How to Fix Them

The five most common EPUBCheck errors and their fixes.

Error: "OPF file does not declare a valid identifier"

Cause: missing or malformed metadata (no title, no language, or invalid ISBN format).
Fix: in Folio Studio, re-enter the project metadata. In raw epub editing, ensure <dc:identifier> is present in content.opf.

Error: "Image file does not exist"

Cause: an image referenced in the HTML doesn't exist in the epub package.
Fix: re-export from the source tool. If using Pandoc, verify all ![](path) references point to existing files at the time of conversion.

Error: "Invalid character in identifier"

Cause: special characters (spaces, accents, colons) in chapter file names or anchor IDs.
Fix: rename source files using alphanumeric only (e.g. chapter-01.md not Chapter 01.md). Folio Studio handles this automatically.

Error: "Table of contents references missing target"

Cause: a TOC entry points to a chapter that doesn't exist (often after renaming or deleting a chapter).
Fix: regenerate the TOC. Folio Studio rebuilds the TOC on every export.

Error: "RSC-005: Element 'meta' is missing required attribute 'property'"

Cause: outdated EPUB2 metadata in an EPUB3 file. Common when converting old epubs.
Fix: re-export to EPUB3. Folio Studio, Vellum and modern Pandoc all default to EPUB3.

Common Mistakes to Avoid

Empty table of contents
Cause: chapters aren't structured with headings (H1/H2). Make sure every chapter starts with a title.

Missing images
If your Word manuscript contains images, they must be embedded in the .docx file (not linked from an external folder). Folio Studio extracts and embeds them in the epub.

Incorrectly encoded special characters
Epub must be in UTF-8. Modern tools (Folio Studio, Pandoc) handle this automatically. If you're using an older tool, check the encoding.

Epub file too large
Platforms like KDP have file size limits (e.g. 650 MB for KDP). A text-only novel never exceeds a few hundred kilobytes. An oversized epub usually means uncompressed images.

Not testing on a real device before publishing
Software validators can miss readability issues that are obvious on a Kindle Paperwhite or iPhone. Always download a preview and read at least the first chapter on the device you expect your readers to use.

Checklist Before Submitting Your Epub

• All chapters have a title (Heading 1 in Word, # in Markdown)
• Metadata filled in (title, author, language, ISBN if applicable)
• Table of contents is present and correct
• Epub opens without errors in Calibre
• EPUBCheck shows no critical errors
• Images are embedded (if applicable)
• Filename contains no spaces or special characters
• Tested on Kindle Previewer (if publishing on KDP)
• First chapter read on actual e-reader or app
• Cover image attached (separately from the epub on most platforms)

* * *

FAQ

Which format is best for importing into Folio Studio?
Markdown if you write in a text editor, DOCX if you use Word. Both are imported with the same quality of result.

Will my epub be accepted on Amazon KDP?
Yes, provided it passes EPUBCheck validation without critical errors. KDP has accepted epub since 2022. Folio Studio generates EPUB3-compliant epub files.

Can I create an epub from multiple Markdown files?
Yes with Folio Studio: import each file separately, reorder chapters if needed, then export. With Pandoc: list all files in order in the command (pandoc ch1.md ch2.md ch3.md -o book.epub).

Will my epub layout look the same on all readers?
No, and that's by design. Epub readers (Kindle, Kobo, Apple Books) apply their own typographic rules and let readers change font and size. Epub is inherently adaptive. Folio Studio templates are designed to behave well across all devices.

How do I convert from PDF to epub?
PDF-to-epub conversion always gives poor results because PDF is a fixed-page format and epub is reflowable. The better path: find the source manuscript (Word or Markdown), or copy-paste the PDF text into Word, clean the formatting, then export to epub. Calibre can do direct PDF-to-epub but expect messy output.

Why was my epub rejected by KDP?
Common reasons in 2026: EPUBCheck errors (run the validator before upload), broken image references, missing chapter structure (no TOC), DRM applied (KDP rejects DRM-protected epubs), or file size over 650 MB. The KDP rejection email usually pinpoints the issue.

How big should my epub file be?
A text-only novel: 200-500 KB. A novel with a few images (cover, chapter ornaments): 1-3 MB. An illustrated book or photo book: 10-50 MB (consider EPUB Fixed Layout). Anything over 50 MB for a text-driven book means oversized images that need compression.

Can I make money selling my epub directly from my website?
Yes, via platforms like Gumroad, Payhip, or your own Stripe-powered checkout. The advantage: 100% royalty (minus processor fees, ~3%). The disadvantage: you have to drive all the traffic yourself. Most authors combine direct sales for newsletter subscribers with platform distribution for discovery.