Using an e-reader? Open the simple Cloud Library

Skip to content

Turn Markdown projects into structured EPUBs.

H1 headings become chapters. Code blocks, lists, links, and images are kept where supported. Add metadata and cover, then export in your browser.

  • H1 headings become chapters you can review
  • Code blocks, tables, and lists preserved
  • YAML frontmatter sets title, author, and language
  • Free Markdown conversion runs locally

How it works

01

Drop Markdown files

A single .md file, multiple files, or a .zip archive. Stays in your browser.

02

Review structure

Chapters detected from H1 headings. Edit metadata, reorder, add a cover.

03

Download EPUB

Export an EPUB draft with TOC, metadata, and cover.

Built for writers and developers.

Headings → Chapters

Every H1 heading splits a new chapter. Subheadings stay inside.

Code & Tables

Fenced code blocks, tables, blockquotes, and lists are kept where EPUB supports them.

Multi-file Books

Drop a .zip of Markdown files. Natural sort order builds the chapter list.

Local by Default

Free Markdown conversion runs in your browser. Cloud Library is optional.

How chapters are detected.

Single file

Every # H1 heading splits a new chapter. The heading text becomes the chapter title in the table of contents. Subheadings (## and below) remain inside the chapter as section markers.

Multiple files / ZIP

Each .md file can contain several H1 chapters; without an H1, its filename becomes the chapter title. Files are sorted naturally, so 02-setup.md comes before 10-end.md. ZIP imports read Markdown files, not bundled image assets.

Metadata from YAML frontmatter.

FieldDescription
titleBook title — overrides H1 if present
authorAuthor name or names
languageBCP 47 tag — en, fr, de, etc.
subjectSubject or genre
keywordsKeywords, separated by commas
descriptionBook description for e-reader stores
isbnISBN identifier
publisherPublisher name
datePublication date — ISO 8601 (2024-06-01)

Already have an EPUB?

Open it in the EPUB Editor to edit chapters, metadata, and cover.

Open EPUB Editor

After export, check your EPUB before sharing or publishing. Want to save your draft and continue later? Explore Library.

Learn about Markdown to EPUB

How Markdown files become EPUB chapters

In each Markdown file, a top-level # heading starts a chapter. Lower-level headings stay inside that chapter. A file without a top-level heading becomes one chapter named from its filename.

You can drop one file, several files, or a ZIP containing .md and .markdown files. E-BOOKA orders paths naturally, so numeric prefixes such as 01-, 02-, and 10- remain useful.

Review chapter titles and order in the editor before export.

Supported YAML frontmatter

E-BOOKA reads simple key: value YAML frontmatter from the first file after sorting. Supported keys are title, author, language or lang, subject, keywords, description, isbn, publisher, and date.

Nested YAML objects and lists are not imported. Unknown keys are ignored. Confirm imported values in the Metadata tab, especially language, publication date, and identifiers.

Markdown formatting and review points

Common Markdown and GitHub-flavored Markdown structures map to EPUB HTML: emphasis, headings, lists, blockquotes, code, tables, horizontal rules, and links.

ZIP imports extract Markdown files, not bundled image assets. Relative image paths are not a supported ZIP asset workflow; review images and add them in the editor when needed. Reader support for complex tables, long code lines, and custom HTML varies.

Use the EPUB Editor to inspect content, add metadata and a cover, then review the exported file in your target reading app or device.