How to Write a Book in Markdown: Complete 2026 Guide

Markdown is a plain text format with lightweight syntax for structuring content. Headings, bold, italic, lists, all written with simple characters. No menus, no toolbar, no formatting that breaks unexpectedly.

For book authors in 2026, Markdown offers a decisive advantage: the source file is clean, portable, can be opened anywhere, version-controlled with Git, written on any device including mobile, and converted to any format (epub, PDF, DOCX) without pre-processing. That's why a growing number of professional authors have adopted it as their primary writing format, and why publishing tools now treat Markdown as a first-class import format alongside Word.

Why Authors Are Switching from Word to Markdown in 2026

The shift from Word to Markdown among serious authors accelerated through 2024-2025 for three concrete reasons.

File corruption no longer accepted as inevitable. Authors who lost weeks of work to corrupted Word files (especially during long writing sessions or after Track Changes accidents) have started looking for safer formats. A .md file is plain text. It can be opened by any editor on any device. It cannot be "corrupted" in the way a .docx can. Even if the editor crashes, the file on disk is still readable.

Cross-device writing became the norm. Authors increasingly want to write on their phone during a commute, on their tablet at a café, on their desktop at home. Word's cross-device story (web Office, mobile Word) is functional but clunky, with formatting drift between platforms. Markdown editors like iA Writer, Obsidian and Typora are native on iOS, Android, macOS, Windows and Linux, and the underlying .md file is identical on every device.

Layout tools accept Markdown directly. The 2026 publishing landscape (Folio Studio, Vellum's import, Atticus, Pandoc, Ulysses) all treat Markdown as a first-class input format. No more "save as DOCX then import then fix the styles". Drag your .md file in, the chapters are detected, the typography is applied, the export is ready.

The end-to-end pipeline (write in Markdown, export to epub via Folio Studio, publish to Amazon KDP) is now cleaner than the equivalent Word workflow, and many authors who tried it once never went back.

Essential Markdown Syntax for a Book

You don't need to learn everything. Here's the 90% of Markdown useful for writing a book.

Headings

# Chapter 1: The Dawn

## I. The Forest

### A sub-section

One hash # = chapter heading (H1). Two hashes ## = subheading (H2). Three = sub-subheading (H3). These headings become the table of contents in your epub.

Bold and Italic

*italic* or _italic_
**bold** or __bold__
***bold italic***

In literary prose, italic is used for inner thoughts, titles of works, and foreign words. Bold is rare in fiction.

Scene Separators

---

Three dashes produce a horizontal rule. In a novel, this creates a visual break between two scenes. Layout tools like Folio Studio can replace these separators with typographic ornaments based on the chosen template.

Quotes and Dialogue

In Markdown, quotation marks aren't handled specially: you type them directly:

She said: "I'm not coming back."

For block quotes (epigraphs, extracts):

> Life is short, art is long.
> -- Hippocrates

Footnotes

The syntax varies between tools, but the most common:

The text[^1] of your paragraph.

[^1]: Your footnote here.

Note: footnotes are well-supported in PDF but their rendering in epub varies across readers. Folio Studio converts them to end-of-chapter notes for epub.

Lists

- First item
- Second item
- Third item

1. First step
2. Second step
3. Third step

Lists are useful for essays, guides and practical books. Less common in fiction, but possible.

Markdown vs Word: Which Is Better for Writing a Novel?

The Markdown vs Word debate splits the writing community. Here's the practical comparison for a book author in 2026.

When Markdown wins: writing a novel from scratch, working across multiple devices, wanting to use Git for version control, preferring distraction-free interfaces, planning to self-publish via Folio Studio / Vellum / Atticus.

When Word wins: collaboration with traditional publishers, working with an editor who only accepts .docx, complex formatting in non-fiction (footnotes per page, bibliographies with Zotero), inherited workflow that's already smooth.

The hybrid approach: many authors write in Markdown and convert to DOCX only when they need to share with a traditional editor. The reverse (writing in Word, converting to Markdown) is messier because Word's hidden formatting cruft doesn't translate cleanly.

Advantages of Markdown for Authors

Focus on the Text

With Markdown, you write plain text. There's no Format menu, no styles to apply, no formatting that shifts based on your mood. The tool disappears; the text remains.

What you see on screen resembles the text you have in mind, with just enough visual cues (the # for headings, the * for italic) to make the structure readable without being intrusive.

Total Portability

A .md file is plain text. It opens in any text editor, on any system. You don't depend on any proprietary software. In ten years, your file will still be readable.

This portability also protects your work: proprietary formats (.docx, .pages) can create compatibility or conversion problems. Markdown doesn't have this problem.

Integration with Modern Tools

Many writing tools handle Markdown natively: Obsidian, iA Writer, Typora, Ulysses (Mac), VS Code with extensions. These tools offer real-time rendering, file management by project, and sometimes features like focus mode, word counting, or cloud sync.

Layout tools like Folio Studio import .md files directly without intermediate conversion. See our guide on creating an epub from Markdown or Word for the full export workflow.

Easy Version Control

Plain text files integrate perfectly with version control systems like Git. For an author who wants to track manuscript evolution, compare versions, or roll back after a rewrite, Git + Markdown is a powerful combination.

Best Tools for Writing in Markdown

Obsidian

Free, all platforms (macOS, Windows, Linux, iOS, Android)

Obsidian is a Markdown-based note editor with a note-linking feature (for creating connections between characters, locations, events). Its popularity among authors comes from community plugins: Longform (for managing a novel chapter by chapter), Dataview (for creating project dashboards), and many others.

Obsidian stores everything locally on your machine. Sync is optional (paid, $8/month) or done via iCloud, Dropbox, or Syncthing.

Best for: authors who want a deeply customisable tool, especially worldbuilders managing many notes on characters, places, and plot threads.

iA Writer

Paid ($30 macOS one-time, $30 Windows one-time, $5 iOS, $5 Android), all platforms iA Writer is often cited as the most elegant Markdown editor. Minimalist interface, focus mode that dims everything except the current sentence, word count and session targets. It includes a real-time rendering preview.

Fewer features than Obsidian, but a more stripped-back writing experience. Ideal for intense writing sessions.

Best for: authors who write long blocks of prose and want zero distraction. Highly recommended for mobile-first writers (iA Writer iOS is best-in-class).

Typora

Paid ($14.99 one-time), Windows/Mac/Linux

Typora takes a unique approach: it doesn't show raw Markdown syntax. When you type **text**, you immediately see the text in bold. This "what you see is what you mean" rendering appeals to those who find raw syntax distracting.

Best for: authors transitioning from Word who want the visual fidelity of a word processor with the file safety of Markdown.

VS Code with Markdown All in One Extension

Free, all platforms (macOS, Windows, Linux)

VS Code is a code editor that works perfectly well for writing books. The "Markdown All in One" extension adds a real-time preview, formatting shortcuts and an automatic table of contents. The advantage is native Git integration.

Not the most accessible tool for authors without technical experience, but for those comfortable with developer tools, it's very efficient. Live Share allows real-time co-editing with an editor or co-author.

Best for: technically inclined authors, those already using VS Code for other work, authors who want maximum customisation and free tools.

Ulysses

Subscription ($6/month or $50/year), Mac/iPhone/iPad only

Ulysses is the reference Markdown editor in the Apple ecosystem. Text library management, writing targets, iCloud sync, direct epub and PDF export. The interface is polished and oriented toward long-form authors.

Apple ecosystem only. No Windows, no Android, no web.

Best for: Apple-only authors who want a turnkey writing + light layout solution.

Honourable mentions for 2026

• Bear (Mac/iOS, $30/year): beautiful interface, less prose-focused than iA Writer but excellent for note-driven writers
• Notion (free for personal use): not pure Markdown but Markdown-compatible, useful for hybrid writers who want a database alongside their prose
• MarkText (free, Windows/Mac/Linux): open-source alternative to Typora with similar WYSIWYG approach
• Logseq (free, all platforms): like Obsidian but outline-first, better for some plotters

Writing on Mobile: Markdown on iPhone, iPad, Android

One of the strongest cases for Markdown in 2026 is mobile writing. Word's mobile apps are functional but heavy, with limited offline behaviour and formatting drift between desktop and mobile. Markdown's mobile story is much cleaner.

On iOS (iPhone and iPad):

• iA Writer for iOS ($5) is best-in-class: native syntax highlighting, focus mode, iCloud sync with the desktop version, hardware keyboard shortcuts
• Obsidian for iOS (free) syncs via iCloud, Dropbox or Obsidian Sync
• Ulysses (subscription) for users in the Apple ecosystem
• Editorial ($10) for power users who want Python automation

On Android:

• Obsidian for Android (free) is the strongest option, with full feature parity with desktop
• iA Writer for Android ($5) brings the same elegant experience as iOS
• Markor (free, open source) is a lightweight alternative for occasional writing

Sync between devices:

The Markdown file is the same on every device. You sync the file (via iCloud, Dropbox, Google Drive, OneDrive, Syncthing) and open it in whatever editor you have on each device. There's no conversion, no formatting loss, no "feature available on desktop only".

Writing on a commute, in bed, at a café: this is where Markdown shines. Pull out your phone, type a few paragraphs in iA Writer or Obsidian, your desktop sees the changes when you come home. No "do you want to open in Word Online?" dialog.

Structuring a Novel in Markdown

Here are two approaches for organising a novel in Markdown.

Approach 1: Single File

All chapters in one file novel.md. Simple, easy to import into Folio Studio or convert with Pandoc.

# Chapter 1: The Dawn

The sun was rising over the silent forest...

---

# Chapter 2: The Meeting

Three days later...

This approach works well for short to medium novels (under 200 pages). For longer novels, the single file can become unwieldy.

Approach 2: One File Per Chapter

A novel/ folder with one file per chapter: 01-the-dawn.md, 02-the-meeting.md, etc. The numbering ensures correct ordering.

novel/
  00-foreword.md
  01-the-dawn.md
  02-the-meeting.md
  03-the-secret.md
  ...

When exporting, files are imported one by one into Folio Studio (which reorders them by filename), or passed in order to Pandoc:

pandoc 01-the-dawn.md 02-the-meeting.md 03-the-secret.md -o novel.epub

Common Markdown Mistakes Authors Make

Five mistakes that produce broken epubs or messy print PDFs.

Using # for emphasis instead of heading

# is reserved for headings (H1). Don't use it as a decoration before a sentence to make it bold. Use **bold** for emphasis. A stray # will be interpreted as a chapter heading and create chaos in your table of contents.

Mixing tabs and spaces in lists

Some Markdown parsers are strict about indentation in nested lists. Use 2 or 4 spaces consistently. Avoid tabs unless your editor is configured to convert tabs to spaces. If your nested list looks broken in the epub preview, this is usually the cause.

Forgetting blank lines between blocks

Markdown needs a blank line between paragraphs, between a paragraph and a heading, between a paragraph and a list. Without blank lines, the parser fuses them together in unexpected ways. When in doubt, add a blank line.

Using underscores _text_ in the middle of words

some_word_here will be rendered as some + italic word + here by some parsers. If you have many underscores in technical vocabulary, use asterisks *italic* instead, or escape underscores with \_.

Including hard line breaks for layout

Markdown doesn't care about line breaks within a paragraph. A line that wraps in your editor is still part of the same paragraph. Don't insert hard breaks to make your editor view look pretty: it makes the source file harder to maintain and doesn't change the output.

From Markdown to Published Book

The typical workflow for an author who writes in Markdown:

1. Write in Obsidian, iA Writer or your editor of choice
2. Edit and revise in the same tool
3. Import into Folio Studio: drag your .md file or import via the interface
4. Choose a template: Folio Studio detects chapters and applies typography
5. Export: epub for digital platforms, PDF for printing

This entire workflow can be completed without ever touching Word or complex layout software. For the detailed export step, see our guide on creating an epub from Markdown or Word. If you're choosing between epub and PDF for distribution, the epub vs PDF comparison guide covers when each format is appropriate.

Markdown Writing Checklist

• Choose a Markdown editor suited to your system and preferences
• Structure chapters with # headings
• Use --- for scene separators
• Typographer's quotes directly in the text (" ")
• Single space after periods (not double)
• Numeric prefix in filenames if using multi-file approach (01-, 02-)
• Version with Git if your technical level allows it
• Sync your .md files across devices (iCloud, Dropbox, etc.)
• Try one mobile writing session to confirm the workflow works for you
• Validate the chapter structure by previewing in your layout tool before final export

* * *

FAQ

Do I need to learn Markdown to use Folio Studio?
No. Folio Studio also accepts Word files (.docx) and PDFs. Markdown is an option, not a requirement. But if you write in a Markdown editor, the import will be even cleaner than a Word file with poorly applied styles.

Can I include images in my Markdown?
Yes, with the syntax ![alt text](path/to/image.jpg). For a text novel, images are rarely needed. For an illustrated guide, images work in epub and PDF, provided the files are available when exporting.

Does Markdown handle em dashes for dialogue?
You can insert an em dash directly into your Markdown file. Markdown syntax doesn't treat it specially: it's a Unicode character like any other. Layout tools will respect your input.

What's the best Markdown editor for Windows?
Typora ($14.99 one-time) and Obsidian (free) are the top choices for Windows. VS Code is excellent if you're comfortable with a code editor. iA Writer ($30 one-time) is cross-platform and works well on Windows too.

Is Markdown really better than Word for writing a book?
For most self-published authors in 2026, yes. Markdown gives you file safety, cross-device sync, distraction-free writing, Git version control, and direct import to modern layout tools. Word retains the advantage if you collaborate with traditional publishers or editors who only accept .docx. See the comparison table earlier in this guide for the full breakdown.

Can I switch from Word to Markdown mid-project?
Yes. Export your Word document as DOCX, then convert to Markdown using Pandoc (pandoc novel.docx -o novel.md) or import into Folio Studio (which auto-detects chapters and lets you continue editing). The conversion is usually clean for plain prose. Complex Word formatting (text boxes, custom styles, embedded images) may need manual fixing.

Does writing in Markdown work for non-fiction with footnotes and citations?
Yes, but with caveats. Footnote syntax works ([^1] and [^1]: text) and Pandoc-style footnotes are widely supported. For academic citations with Zotero, Markdown editors like Obsidian and VS Code support BibTeX integration via plugins. For heavy citation work in a doctoral thesis, LaTeX may still be a better choice.

Can I write on my phone in Markdown?
Yes, and this is one of Markdown's main strengths in 2026. iA Writer iOS ($5), Obsidian (free, iOS and Android), and Ulysses (subscription, iOS only) are all excellent. The .md file syncs cleanly to your desktop via iCloud, Dropbox or any sync tool. Writing 500 words on the train and seeing them on your desktop when you arrive home is friction-free.