Markdown Preview
View > Preview (or the Toggle Preview shortcut) renders the current document the way it will actually look once exported — fonts, sizes, justification, page proportions, and drop cap all come from the currently selected typesetting style, the same one the Export dialog uses. The open document’s title sits at the left of the top bar, same as the Editor pane — the Preview tab itself is just labeled “Preview”, so this is what actually confirms which document you’re looking at. A Style picker at the right of that same bar lets you switch styles live and see the change immediately; picking a style there updates the project’s export style too, so Preview and the Export dialog always agree on what you’ll get switching one from the other.
Headings, quotes, code blocks, verse, lists, and tables still render with sensible on-screen formatting, but no longer in the old color-coded “dev preview” palette — book export is effectively monochrome ink on a page, so Preview reads that way too.
Images work two ways:
- Standard Markdown:
 - Obsidian-style embeds:
![[image.png]]
Relative image paths resolve against the open document’s own folder, and must stay inside the project (a path that tries to escape the project root — via .. or a symlink — is refused). Remote http(s):// images are never fetched.
Zooming
Hold Ctrl and scroll over the Preview pane to zoom the rendered text in and out — handy for proofreading at a larger size or fitting more of a page on screen. Ctrl + + and Ctrl + - do the same from the keyboard, and Ctrl + 0 resets back to 100%. This only scales what’s shown in Preview; it doesn’t change the typesetting style’s actual font sizes, so Export is unaffected, and your zoom level is remembered the next time you open the app.
Verse
A ```verse fenced block preserves its line breaks exactly as typed, unlike an ordinary paragraph (where a single newline collapses into a space):
```verse
Roses are red,
Violets are blue.
It renders — in Preview and every [Export](export.md) format — in its own font, size, and italic setting (a style's `[verse]` table, see [Typesetting Styles](export-typesetting-styles.md); an older custom style predating this falls back to a sensible default rather than failing to load), defaulting to upright, not italic, since a verse block is your own poem rather than a quotation, independent of body text or blockquotes. Text inside a verse block is literal: bold/italic/`[[wikilinks]]`/`#tags` aren't parsed, the same limitation an ordinary fenced code block already has — a verse block is meant for the poem's own words, not for markdown syntax nested inside it. Straight quotes and dashes still curl if [Typewriter Quotes](#typewriter-quotes) is on, since a poem is prose, not code.
Dialogue, by contrast, doesn't need any special syntax — write it as plain paragraphs, and turn on Typewriter Quotes for proper curly quotation marks; see [Typewriter Quotes](#typewriter-quotes) below.
## Typewriter Quotes
**`File > Settings > Editor`** has a **"Typewriter quotes in Preview and export"** checkbox, off by default. When it's on, straight typewriter punctuation is rewritten wherever markdown gets rendered *from* — the Preview pane here, and every [Export](export.md) format:
| Typed | Rendered |
|---|---|
| `"straight double quotes"` | "curly double quotes" |
| `'straight single quotes'` | 'curly single quotes' |
| `--` | — (em dash) |
| `...` | … (ellipsis) |
Your `.md` file on disk is never touched — the source text you type stays exactly as typed, straight quotes and all. Only the rendered *view* of it (Preview, or a compiled DOCX/EPUB/PDF) changes, so switching the setting off later shows your original punctuation again, nothing was lost. Quote direction (opening vs. closing) is inferred from context, the same simple heuristic most word processors use — it isn't guaranteed correct in every edge case (e.g. deeply nested quotes), but handles ordinary dialogue and contractions correctly.