Most Markdown guides are written for programmers. A manuscript uses a small corner of the language, and this is that corner, with what each mark becomes in a book.
Why do writers use Markdown at all?
Because the file holds the text and nothing else. A Word document stores your sentences next to styles, tracked changes and layout decisions, and all of it travels with the file whether you meant it to or not. A Markdown file is plain characters with an .md extension. It opens in every text editor on every computer, it stays small after years of drafts, and two versions of a chapter can be compared line by line.
The cost is that you do not see the finished page while you type. You see the marks. For drafting that tends to be a relief, because there is nothing to fiddle with, and the page becomes a separate step you take once the words are done. Google Docs, Word or Markdown sets out that trade in more detail, and Word to Markdown covers moving a manuscript you already have.
Which marks does a manuscript use?
This is the working set for prose. Anything beyond it is either for programmers or an extension that only some tools understand.
| You type | You get | Where it shows up in a book |
|---|---|---|
# Title | The largest heading | The book title, once |
## Chapter One | A chapter heading | Every chapter |
### A section | A section heading | Subsections in non-fiction |
*word* | Italic | Emphasis, titles of works, foreign words |
**word** | Bold | Rare in prose; labels and key terms |
| A blank line | A new paragraph | Everywhere |
- item or 1. item | A list | Steps, recipes, checklists |
> text | A block quote | Quotations, letters, epigraphs |
[text](address) | A link | Ebooks, and sources in non-fiction |
 | An image | Figures, photographs, maps |
| A backslash before a mark | The character itself | An asterisk you want printed |
Most novels need nothing else. A non-fiction book adds tables and perhaps notes, and a technical book adds code blocks. Nobody needs to memorise the full specification to finish a manuscript.
How do headings become the structure of the book?
Headings carry more weight in a book than anywhere else, because they are the only thing a converter can use to find your chapters. The contents page, the EPUB's navigation menu and the PDF's bookmarks are all built from them.
The convention that works: one # for the book's title, ## for every chapter, ### for sections inside a chapter. Do not skip a level, and do not use bold text as a fake heading, since a line that only looks like a heading is invisible to everything that builds the structure. Headings in Markdown goes through each level and what it becomes.
What about paragraphs and line breaks?
This is where writers get caught. In standard Markdown, pressing Enter once does not start a new line. The two lines are joined into one paragraph, and only a blank line separates paragraphs.
For prose that is harmless, since you leave a blank line between paragraphs anyway. For poetry, song lyrics, addresses and dialogue laid out line by line, it quietly ruins the page. Some tools want two spaces at the end of a line to force a break; others want a backslash. Why Markdown eats your line breaks lists the workarounds tool by tool.
How do you start a chapter on a new page?
Standard Markdown has no idea what a page is. It was written for web pages, which scroll. So a page break is always something a particular tool adds, and each tool picks its own way of writing it: raw HTML in one, a LaTeX command in another, a CSS rule in a third.
The mark many writers already use as a scene or chapter separator is a line of three dashes. In standard Markdown that line draws a horizontal rule, and placed directly under a line of text it turns that line into a heading, so always leave a blank line above it. How to control page breaks in Markdown compares the options.
Which syntax is safe to rely on in a long book?
The core marks in the table behave the same in every tool. The extensions do not, and a book file lives long enough to pass through several tools.
| Feature | Works everywhere? | Safer habit |
|---|---|---|
| Headings, emphasis, lists, links | Yes | Use freely |
| Tables | Most tools | Keep them simple: no merged cells |
Footnotes with [^1] | Only some tools | Number notes by hand at the back |
| Page breaks | No standard at all | Learn your tool's marker |
| Raw HTML | Depends on the output | Avoid in a book |
| Curly quotes and dashes | Depends on the tool | Check the output once |
Notes are the case people trip over most. The footnote syntax is an extension, and a tool that does not support it prints the markers as text. Footnotes and endnotes in a Markdown book explains the method that survives every tool, and smart quotes and dashes covers the punctuation.
What habits keep a book-length file manageable?
A short story fits in one file comfortably. A 90,000-word novel can too, but most writers find a few habits make it easier.
- One file per chapter while drafting, numbered so they sort:
01-arrival.md,02-the-letter.md. Combining them into one book is a single step at the end. - Images in a folder next to the text, linked with relative paths, so the book still finds them when the folder moves.
- Real headings from the first draft. Retrofitting
##onto two hundred pages of bold chapter titles is a miserable afternoon. - An editor you like. Any text editor works. Writing a book in VS Code and Obsidian to PDF cover two popular ones.
How do you start a book in Markdown, step by step?
- Make a folder for the book, with a subfolder called
images. - Create the first chapter file,
01-chapter-one.md, in any text editor. - Type the chapter heading as
## Chapter Oneon the first line, then a blank line. - Write. Leave a blank line between paragraphs and use asterisks for emphasis.
- Start the next chapter in a new file when this one is done, numbered so the files sort in reading order.
- Preview the result in any Markdown viewer once a chapter is finished, to catch a stray asterisk early.
That is the whole setup. Everything else in this guide can wait until you need it.
Turning the Markdown into a finished book
Markdown is half the job. The other half is the page: typefaces, margins, page numbers, where chapters start, and a cover.
That half is what bukpress does. You paste or drop in the .md file, set the typography once, and it exports a typeset A4 PDF from the Markdown, and on the Pro plan a reflowable EPUB from the same file. It also settles two of the problems above in its own way: a line of --- on its own is a hard page break, and a single Enter is a real line break. Syntax it does not document passes through as plain text rather than being guessed at, so footnote markers print as typed. Self-publishing from Markdown walks the whole route from draft to published book.
Common questions
Is Markdown hard to learn?
No. The marks a book uses fit in one table, and most writers are comfortable within a chapter. The only surprises are line breaks and page breaks, because the rules for those vary between tools.
Can I write a novel in Markdown?
Yes. A novel needs headings, paragraphs and italics, which is the most basic Markdown there is. The work comes later, when the file is typeset into pages, and that step is the same however the text was written.
Do I need special software to write Markdown?
No. Any plain text editor works, including the ones already on your computer. Dedicated Markdown editors add a preview pane and shortcuts, which are pleasant but optional.
Can I convert Markdown back to Word for an editor?
Yes. Pandoc converts a Markdown file to a .docx in one command, and many editors export to Word directly. Expect to check tables and images after the trip.