How do I read an Obsidian novel as one document?

With nothing but Obsidian

One note per scene is the usual way to draft a novel in a vault, and Obsidian's own embeds will stitch those notes into one reading copy. Make a note called something like Manuscript and give it one line per scene, in order:

![[01 Arrival]]
![[02 The Letter]]
![[03 Harbor Road]]

Switch that note to Reading view and the scenes run on one after another. Want scene five earlier? Cut its line and paste it higher. Edits still happen in the scene notes; the manuscript note only shows them. Obsidian's Export to PDF command renders the embedded text too, which gives you a single file to read on a tablet or send to a friend. Depending on your theme, each scene may keep the frame embeds have in Reading view, so treat it as a working copy rather than a finished page.

Number the scene files as well, with leading zeros. Then the file explorer sorts in story order, and the order survives anything that reads the folder rather than your manuscript note.

With the Longform plugin

Longform is a community plugin written for exactly this. You mark a folder as a project, the scenes appear in Longform's own pane, and you drag them into order there rather than renaming files. Its compile step joins the scenes into one note, ready to read through or export.

Community plugins are maintained by their authors, not by Obsidian, so it pays to look at a plugin's page for recent updates before you build a novel on it, and to keep the vault backed up before updating either Obsidian or the plugin. Longform keeps the scene order in the frontmatter of the project's index note. If you stop using it, the order lives on only in that list, which another tool reading the folder will not know about. Numbered file names are cheap insurance.

In Tabularia

Here the book is one continuous manuscript to begin with, and scenes are divisions inside it, listed in the Outline where a drag reorders them. Reading straight through needs no assembly note.

You can import the vault itself by pointing the folder import at it. The import lists every Markdown note with a checkbox, so the notes that are research rather than story can stay behind. The list starts in folder and file-name order, with numbers sorted as numbers, and each note has Move up and Move down buttons to set the reading order before anything is created.

Three limits to know before you rely on it:

• It does not read Longform's scene order. Set the order in the import list, or rely on numbered file names.
• An embedded note such as ![[02 The Letter]] is not expanded into that note's text; the link's name is kept and the import reports it. Import the scene notes themselves, not the assembly note.
• Canvas and Base files do not become manuscript text, and the import says how many it left out.