How to Write a Book in Markdown: A Complete Workflow
From first outline to finished EPUB — a workflow that scales to a full book.
Plenty of authors draft books in Markdown, and for good reason: it's plain text, so it's future-proof, works in any editor, plays nicely with version control, and never traps your manuscript in a proprietary file. This guide lays out a complete, practical workflow — from your first outline to a finished EPUB you can read on any device.
Why write a book in Markdown?
- It's plain text. No corrupted files, no version lock-in, readable in 20 years.
- You focus on writing, not formatting. A few symbols handle structure; the styling comes later.
- It's portable. The same file works in dozens of apps and converts cleanly to EPUB, HTML, or PDF.
- It plays well with backups and Git. Track every change and never lose a draft.
Step 1: Pick an editor
Any text editor works, but a few make long-form writing far more pleasant:
- Obsidian — great for research-heavy books with lots of cross-linked notes.
- iA Writer — a calm, focused environment built for prose.
- VS Code — ideal if you're already technical and want split preview.
- Typora — a clean "what you see" Markdown editor.
The right choice is the one you'll actually open every day. Don't overthink it.
Step 2: Structure the book
Decide early how you'll split the manuscript. Two approaches work well:
- One file per chapter — easier to reorder and manage while drafting.
- One master file — simplest when it's time to export.
Use headings consistently: # for the book title,
## for each chapter, and ### for sections
within a chapter. This hierarchy becomes the navigable table of
contents in your EPUB, so keep it clean.
If you draft one file per chapter, name them with a number prefix
(01-intro.md, 02-chapter.md) so they sort
correctly and are trivial to concatenate at the end.
Step 3: Write the front and back matter
A finished book is more than chapters. Plan for a title page, copyright
notice, dedication, and a table of contents at the front, and
acknowledgments, an author bio, and any appendices at the back. In
Markdown these are just more headings and paragraphs — separate major
parts with a horizontal rule (---).
Step 4: Handle images the right way
Keep images in a dedicated folder (for example ./images/)
and reference them with relative paths:
When you export, load the Markdown together with its image folder so everything gets bundled into the EPUB. Local files embed reliably; remote URLs may not be included for offline reading.
Step 5: Keep backups (and consider Git)
Plain-text files are perfect for version control. Even a simple Git repository lets you see every change, recover deleted passages, and write fearlessly knowing nothing is ever truly lost. If Git feels like overkill, at minimum keep the folder in a synced location and make dated copies at milestones.
Step 6: Export to EPUB
When the manuscript is ready, combine your chapters into one Markdown document (if you split them), then convert it to EPUB. Set the book title, author name, and language so your ebook shows up correctly in any library. Review the live preview, fix anything that looks off in the source, and export.
From there, send the EPUB to your Kindle, Kobo, or Apple Books and read your own book the way your readers will.
A workflow that lasts
The beauty of this approach is that every step uses open, durable tools. Your manuscript stays plain text from first word to final export, and the conversion to EPUB happens entirely in your browser — private, instant, and free. Open the converter when you're ready to see your book take shape.
Turn Your Markdown Into an Ebook
Free, private, and instant — the converter runs entirely in your browser. No account, no upload.
Open the Converter →