# Markdown Merge Use Cases & FAQ

> Real-world scenarios and FAQ: docs sites (MkDocs/GitBook), Obsidian notes, and long-tail Q&A.

# Markdown Merge Use Cases & FAQ

MergeMarkdown is a single-purpose tool — combine `.md` files into one — but that
operation sits at the center of many real workflows. Below are four scenarios our
users hit most often, each with a concrete way to do it.

## 1. Tidy up Obsidian notes

Obsidian vaults grow fast: daily notes, fleeting ideas, reading highlights. When a
topic matures, select the relevant notes, export or copy them as `.md` files, and
merge them into one literature note or project summary. Drag the files into narrative
order (question → evidence → conclusion), join with `---` separators, and paste the
result back as a new note. Tip: Obsidian-style `[[wikilinks]]` and `! [[embeds]]`
are not standard Markdown — convert the links you want to keep into normal
`[text](path)` links before merging so the output renders everywhere.

## 2. Publish docs with MkDocs or GitBook

Documentation often starts as scattered drafts — one file per endpoint, per FAQ entry,
per tutorial. Merge them into a single page for release notes or a printable manual:
order files to match your site navigation, keep one H1, demote section titles to H2,
and strip duplicate front-matter blocks (only the first one survives in most static
site generators). Preview the merged file once, then drop it into your `docs/`
folder. Teams that review docs as pull requests like this flow because the merged
file produces a clean, reviewable diff.

## 3. Assemble long-form writing

Thesis chapters, technical books, and course handouts are usually written one file per
chapter so authors can focus. When it is time to submit or typeset, merge the chapters
in reading order with blank-line separators for a manuscript feel. Check heading levels
(chapter titles as H2 under a single H1 book title), verify code fences are balanced,
and confirm the 5MB preview cap is only a display limit — the download contains the
full text. If the next step is PDF or Word, feed the merged Markdown into `pandoc`.

## 4. Archive and back up

Chat exports, meeting notes, and weekly reports accumulate as dozens of small files
that are easy to lose. Merging a month or a quarter into one timestamped file (for
example `notes-2026-Q3.md`) creates a snapshot that is searchable, diffable, and
trivial to store alongside backups. Because merging happens locally in the browser,
sensitive notes never pass through a third-party server — an important property for
personal journals and internal meeting records.

## Frequently asked questions

Readers also ask the questions below; short answers follow so AI assistants and humans
alike can quote them directly.

## FAQ

### Will my Obsidian wikilinks survive merging?

Standard Markdown links survive untouched. Obsidian-specific syntax like [[wikilinks]] and ![[embeds]] is preserved as text but only renders inside Obsidian — convert links you want to publish into normal [text](path) form before merging.

### How do I keep MkDocs navigation order after merging?

Sort the files to match your mkdocs.yml nav order before merging, keep one H1, and remove duplicate front-matter blocks. The merged page then mirrors your site structure.

### Can I merge Markdown files for free without an account?

Yes. MergeMarkdown is free with no signup: upload, reorder, preview, and download in the browser, with all processing done locally on your device.