Format & Export Free · in-browser · optional cloud history

Plain Text to Markdown Chapters

Split plain-text fiction on "Chapter X" lines and output Markdown with H1 headings. Free text-to-Markdown converter for writers, Git, and Obsidian workflows.

Runs in your browser. We don’t use your drafts to train models.
0 words 0 chars < 1 min
Ctrl+Enter

Paste your text above, then click Transform — or use Try sample for a quick demo.

About this tool

Markdown plays nicely with Git, static site generators, Obsidian, and some Story Studio-adjacent publishing pipelines. This plain text to Markdown tool splits your manuscript on chapter heading lines and outputs H1 chapter headings with body text — ready for docs, wikis, web serials, or version control. Paste your normalized draft; conversion runs in your browser with no upload.

What you can do

  • Splits on Chapter 1, CHAPTER 2: Title, and Roman numeral heading patterns
  • Outputs H1 Markdown headings for each detected chapter
  • Preserves paragraph breaks in body text
  • One-click copy of Markdown output
  • Pairs with chapter heading formatter for consistent source headings
  • Works for web serials, Git-backed fiction, and Obsidian vaults
  • Private browser transform — manuscript never uploads to servers

Export formatting before KDP upload

Kindle book formatting and print workflows punish inconsistent quotes, scene breaks, and chapter headings. Normalize typography after content edits, then convert Word/DOCX to a KDP-ready EPUB — otherwise you will re-export three times. These transformers run locally in your browser.

Free Kindle book formatter · Publish & launch guide · KDP upload checklist · Export documentation

How to use it

  1. Run chapter heading formatter first if headings are inconsistent.
  2. Paste plain text with Chapter 1, Chapter 2, etc. headings.
  3. Click Transform to convert to Markdown with H1 chapter headings.
  4. Review H1 headings and paragraph breaks in the output.
  5. Click Copy result and paste into GitHub, Obsidian, Hugo, or your wiki.

Tips for fiction authors

  • Markdown version control with Git lets you diff revisions, branch for experiments, and revert bad edits — powerful for long fiction projects and AI draft tracking.
  • Obsidian and other Markdown editors work well for fiction planning. Convert your draft to Markdown and use wiki-links between scenes and characters.
  • Static site generators like Hugo or Jekyll can turn Markdown chapters into a web serial. Convert once, publish chapter by chapter.
  • After converting, check that scene breaks and italics survived. Plain text loses formatting that you may need to re-add with Markdown syntax (*italic*, **bold**).
  • Use manuscript diff on Markdown exports to track changes between AI revision passes in a Git repo.

Related guides

Common questions

What chapter heading patterns work?

Lines like "Chapter 1", "CHAPTER 2: Title", or "Chapter IV" at the start of a line.

Does it add formatting beyond headings?

It adds H1 chapter headings and preserves paragraph breaks — no bold or italic inference from plain text.

Can I convert back from Markdown?

This tool is one-way to Markdown. Use your editor's export for reverse conversion.

Does this work with Story Studio exports?

Yes. Export or paste text with Chapter headings from Story Studio, normalize headings first if needed, then convert.

Is my manuscript uploaded?

No. The text-to-markdown converter runs entirely in your browser on Entangled Text.

Comments (0)

Share a tip, question, or experience — keep it useful for other writers.

Prefer a public profile and edit access? Sign in or create a free account.

5,000 left

No comments yet. Be the first to share a thought.