A plain-text workflow that takes you from blank file to finished ebook
Writing a book in markdown means drafting your manuscript as plain text files with a handful of simple formatting marks — # for a chapter heading, *italics*, **bold** — instead of in a word processor. You keep one chapter per file, store book details in a small metadata block, and convert the whole thing to EPUB, DOCX, or PDF when you're done. Authors use this workflow for real, full-length books: novelist P.D. Workman has published over 70 books drafted in markdown. This guide covers why it works, which editor to pick, how to structure the manuscript, the honest limitations, and how to turn the finished files into an ebook.
Markdown's appeal for long-form work isn't aesthetic — it's structural. A few things matter more over the months it takes to finish a book than they do for a quick document:
The most freeing fact about markdown is that switching editors costs almost nothing — your files don't live inside the app, so you can try one for a month and move on if it grates. With that pressure off, here's the landscape for book-length writing:
| Editor | Cost | Best for |
|---|---|---|
| Obsidian | Free (personal use) | A plain-file workspace with backlinks and plugins; strong for series, research, and one-file-per-chapter projects |
| iA Writer | One-time | Distraction-free drafting; focus mode dims everything but the current sentence |
| Ulysses | Subscription (Apple only) | A library and word-count goals built for long-form; publishing to WordPress/Ghost/Medium |
| Typora | One-time (~$15) | A clean, minimal live-preview editor; no plugin ecosystem |
| Zettlr | Free | Academic writing — Zotero citations, Pandoc export, footnote-heavy work |
| VS Code | Free | Writers already comfortable in a code editor who want git and extensions in one place |
If you're undecided, start with Obsidian (free, plain files, scales to a whole series) or iA Writer (if pure focus is what you're after). You can change your mind later without touching your manuscript.
One reason markdown suits prose is that the syntax a novelist needs fits on a postcard. You are not learning a markup language; you're learning about six marks. Here's essentially the entire toolkit for fiction:
# Chapter One → a chapter title (one per chapter)
The morning was cold. → a normal paragraph; blank line between paragraphs
*italic* or _italic_ → emphasis (thoughts, ship names, stress)
**bold** → strong emphasis (use sparingly in fiction)
--- → a scene break within a chapter
> A quote, or an → a blockquote (epigraphs, letters, excerpts)
> epigraph at a chapter
> opening.That's it for the vast majority of novels. Non-fiction adds a few more — ## Section and ### Subsection headings, - bullet lists, 1. numbered lists, and links — but you can write tens of thousands of words knowing only the marks above. Anything fancier (footnotes, tables) is where markdown's edges show up, which the next section covers. Notice the scene break: a lone --- on its own line. Leave it as plain text and a naive converter prints three literal hyphens mid-chapter; a book-aware tool turns it into a styled, centered separator.
A book is just a folder of text files if you set it up deliberately. The pattern that holds up across 3 chapters or 50:
Give each chapter its own file with a zero-padded number at the front so they always sort in reading order, on any device:
my-novel/
├── 00-front-matter.md
├── 01-chapter-one.md
├── 02-chapter-two.md
├── 03-chapter-three.md
└── 99-about-the-author.mdThis is exactly how high-volume authors work — Workman keeps "one chapter per Markdown file" with numbered names — and it pays off at export time, when the files are concatenated in order into a single book.
Start your first file (or a dedicated metadata file) with a YAML front-matter block. Conversion tools read it to set the title, author, and language of the finished ebook:
---
title: My Novel
author: Jane Author
language: en-US
---A single top-level heading (#) marks each chapter title. Most conversion tools split the book into chapters on those H1s and build a navigable table of contents from them — so keep them consistent and don't sprinkle extra H1s inside a chapter. Use ## and ### for sections within a chapter.
Markdown is excellent for prose and weak at a few things worth knowing before you commit a whole book to it:
None of these are dealbreakers for straight narrative writing. They're reasons to decide your export path early rather than discover a gap the week before launch.
Writing is only half the workflow; at some point the plain text has to become a book a reader can open. You have two honest routes:
Either way, the lesson from authors who do this at scale is the same: write in plain text, keep the structure clean, and leave the formatting until the end.
Yes — full-length books are written in markdown routinely. Novelist P.D. Workman has published over 70 books drafted in markdown using Obsidian. You write plain text with light formatting marks, keep one chapter per file, and export at the end.
There's no single best one, and switching costs almost nothing because your files aren't locked in the app. Obsidian (free, plain-file, plugins), iA Writer and Ulysses (focus and goals on Apple devices), Typora (clean one-time purchase), VS Code (developers), and Zettlr (academic) all work — pick the one whose grain matches how you write.
One file per chapter with numbered filenames so they sort in order, book metadata in a YAML front-matter block, and a single # heading per chapter. Conversion tools split on those H1s and build the table of contents.
No single standard (footnotes and tables vary by flavor), weak support for complex layout, and no native tracked changes — export a DOCX when an editor needs to redline. For plain prose, none of these get in the way.
Manuscript ready? Convert it to a Kindle-ready EPUB in seconds — no account. New to the structure? Start with the Formatting Guide, or read how to convert markdown to EPUB.