Chapter Batch Export helps you save Longform roots as separate chapter files

Name: Chapter Batch Export
Author: theluckystrike

Export Longform scene groups as chapters.

Install in Obsidian

Directory page Source on GitHub

MIT · no telemetry · core features free

Three chapter outputs and their source scenes in manuscript order. — Open larger

version: 1.1.0
released: 2026-10-21
downloads: 23
review: Passed
health: Excellent
license: MIT
listed for: Desktop, Mobile
obsidian: 1.13.4 or later

The README reports desktop app tests. Physical phones and tablets were not tested.

Directory facts fetched 2026-10-23 07:28 UTC from community.obsidian.md/users/theluckystrike.

About Chapter Batch Export

You want to save Longform roots as separate chapter files in your vault.

Open your Longform manuscript index to preview one Markdown file per root chapter. Chapter Batch Export joins each parent scene before its children in saved order. It also writes an index linking the outputs to their sources.

Preview three chapters, inspect joined text and open the export index.

Free features

Preview chapter files

Review output filenames and source scene paths in manuscript order. Each root becomes a chapter with its child scenes.

Join scene text

The exporter removes initial scene frontmatter and joins bodies with blank lines. The free export adds a chapter heading above that text.

Joined introduction text with the research question and study scope. — Open larger

Check missing scenes

A missing selected scene disables Save chapters and shows its expected path. Fix the source path, then refresh the preview.

The Obsidian window shows a missing interview scene blocks chapter export. — Open larger

Create a linked export index

The new output folder receives chapter notes and an index linking outputs to source scenes. An existing output folder blocks export.

The saved index links to chapter files and source notes. — Open larger

Pro features

Pro costs $5 a month or $15 one time through GitHub Sponsors. One sponsorship turns on Pro in every plugin that has it.

Select ranges and formats Pro

Pro selects root chapter ranges while keeping manuscript order. Separate heading and filename formats accept the title and padded chapter number.

The second chapter selected with a custom heading and filename format. — Open larger

Save named presets Pro

Pro saves up to 50 named sets of export options in local settings. Reusing a preset name replaces that entry.

A named Method review preset loaded from local settings. — Open larger

See how Pro works

Set up Chapter Batch Export

needs

Obsidian 1.13.4 or later
A manuscript index using the supported Longform scenes format.

steps

Save scene edits and open the manuscript index note.
Run Preview chapter export from the command palette.
Check filenames, source paths and the text preview.
Choose a new output folder whose parent exists.
Select Save chapters and review the output index.

If the app can't find a new plugin yet, try again later. Obsidian says a plugin that passes the review shows in the app within 24 hours.

How to export Longform chapters as Markdown

Known limits of Chapter Batch Export

The exporter writes Markdown inside the vault and does not run document conversion tools.
Single-scene projects and legacy project data outside the index are unsupported.
Scene trees above 64 levels or 10,000 entries are rejected.
Scene paths must match exactly; the exporter does not search for similar names.
The output folder must be new and its parent must exist.
A write failure can leave incomplete output, and simultaneous sync writes were not tested.

Questions about Chapter Batch Export

Does this make Word or PDF files?

The exporter writes Markdown chapters in your vault. It doesn't run PDF, DOCX, LaTeX or Pandoc conversion.

Does Longform need to be enabled?

The exporter can read its supported index format without Longform enabled. The index needs scenes format, a sceneFolder string and a nonempty scenes array.

Can I overwrite an earlier draft?

Use a new output folder for another draft. Existing output folders block the export.

What remains after a failed write?

Created chapter files can remain in the incomplete folder. The exporter writes the index last, so inspect the folder before retrying.

Network use

After you select Sign in with GitHub, the plugin sends its client ID, read:user scope and device-flow requests to github.com. Due checks and Refresh send your token to api.github.com to read your sponsorship tier and total payment. No note text, filenames or other vault data goes to either host.

Read the full network disclosure