How to combine thesis chapters into one
- Step 1De-collide footnotes across chapters first — The merger concatenates text without touching footnotes, so reused labels like
[^1]in multiple chapters will clash. Before merging, renumber footnotes to be unique across the whole thesis (for example[^1-1],[^2-1]per chapter) so references and definitions stay paired. - Step 2Switch to Upload mode and gather chapters — Use the Upload file tab — paste mode handles only one document. The drop zone accepts
.md,.mdx,.markdown, and.txt, so chapters drafted in different editors all work. - Step 3Order chapters with numeric filename prefixes — The merge follows the order of the selected file list and has no reorder control. Prefix chapters
01-,02-,03-(zero-padded) so introduction, literature review, methodology, results, and discussion sort into the correct submission order before you select them. - Step 4Keep filename titles on — Leave Add H1 from filename when missing on so any chapter without a
#heading is titled from its filename. Chapters that already begin with their own# Chapter 1: Introductionkeep that heading untouched. - Step 5Generate the contents outline — Leave Generate Table of Contents on to prepend
## Table of Contentslinking every heading. Use it as a structural checklist against your faculty's required chapter order before you export. - Step 6Run, then convert to the required format — Click Run MD Merge and download
merged.md. Then run it through md-to-pdf-academic or md-to-docx to produce the PDF or Word file your submission portal expects.
Thesis-merge options and what they affect
The merger offers two controls. Footnote renumbering, citation handling, and heading numbering are not among them — handle those before or after the merge.
| Concern | Handled by the merger? | Detail / where to handle it |
|---|---|---|
| Chapter separators | Yes | A --- horizontal rule is inserted between every pair of chapters |
| Untitled chapter files | Yes (useFilenames, default on) | Prepends # <filename> when a chapter has no # heading |
| Contents outline | Yes (includeToc, default on) | Prepends ## Table of Contents linking every heading H1–H6 |
| Heading levels | Preserved, not changed | Use md-heading-shifter beforehand if you need to demote chapter headings |
| Footnote numbering | No | Concatenated verbatim — renumber [^n] labels to be unique across chapters before merging |
| Output format (PDF / DOCX) | No | Merger outputs Markdown only — convert with a sibling tool afterwards |
Tier limits for a thesis merge
Real markdown-family caps. A standard 5–8 chapter thesis fits Pro; an unusually long dissertation with many appendix files may need a higher tier.
| Plan | Chapters (files) per merge | Per-file size / characters |
|---|---|---|
| Free | Cannot merge | 1 MB / 500,000 |
| Pro | Up to 10 | 10 MB / 5,000,000 |
| Pro + Media | Up to 50 | 50 MB / 20,000,000 |
| Developer | Unlimited | 500 MB / unlimited characters |
Cookbook
Thesis-shaped merges. Chapter filenames follow a typical PhD structure.
A five-chapter thesis with a contents outline
Five chapters, prefixed in submission order, merge into one file. The TOC reproduces the chapter outline you can check against faculty requirements.
Selected (in order): 01-introduction.md 02-literature-review.md 03-methodology.md 04-results.md 05-discussion.md merged.md starts: ## Table of Contents - [Introduction](#introduction) - [Literature Review](#literature-review) - [Methodology](#methodology) - [Results](#results) - [Discussion](#discussion)
Footnote collision to fix before merging
Both chapters reused [^1]. The merger concatenates them as-is, so the merged file now has two [^1] definitions — ambiguous in any renderer. Renumber first.
Before (collision after a naive merge): ...as argued previously.[^1] [^1]: Smith, 2019. ... ...the method follows.[^1] [^1]: Jones, 2021. Fix before merging — make labels unique per chapter: ...as argued previously.[^1-1] [^1-1]: Smith, 2019. ... ...the method follows.[^3-1] [^3-1]: Jones, 2021.
An untitled appendix file is auto-titled
appendix-a.md was drafted without a heading. With filename titles on, it merges in as # appendix-a and appears in the contents outline.
Input (appendix-a.md, no H1): Survey instrument used in Study 2... In merged.md: # appendix-a Survey instrument used in Study 2...
Section sub-headings nest in the TOC
Methodology's sub-headings appear indented under the chapter in the contents, mirroring the section hierarchy your committee expects.
03-methodology.md: # Methodology ## Research Design ## Participants ## Data Analysis TOC entries: - [Methodology](#methodology) - [Research Design](#research-design) - [Participants](#participants) - [Data Analysis](#data-analysis)
Merge then produce the submission PDF
The submission portal wants one PDF. Merge the chapters, then convert the combined Markdown.
Step 1 md-merger → merged.md (TOC + 5 chapters) Step 2 /markdown-tools/md-to-pdf-academic → thesis.pdf (If the portal requires Word: /markdown-tools/md-to-docx → thesis.docx)
Edge cases and what actually happens
Footnotes collide after merging
Not de-collidedThe merger preserves text verbatim and does nothing special with footnotes. Chapters that each define [^1] will both carry that label into the merged file, producing ambiguous references. Renumber footnotes to be unique across chapters before merging — the tool will not do it for you.
Chapters land out of order
By designOrder follows the selected file list; there is no reorder control. Use zero-padded numeric prefixes (01-, 02-, ...) on chapter filenames and reselect so the submission order is correct before merging.
Free plan can't merge chapters
Pro requiredMerging multiple files requires Pro. On the free plan, selecting more than one chapter stops with Merging multiple files requires a Pro subscription.
Too many chapter and appendix files
Batch limitIf chapters plus appendices exceed your plan's per-merge cap (Pro 10, Pro + Media 50), the merge stops with Batch limit is N files for your plan. Pre-merge appendices into one file first, or upgrade.
Repeated section names across chapters
Duplicate anchorAnchors come from heading text only. If multiple chapters each contain ## Summary, the TOC links all point to #summary and resolve to the first. Make repeated section headings distinct (## Results Summary, ## Discussion Summary).
A chapter already has its own H1
PreservedThe filename-title option only acts on files lacking a # line. A chapter opening with # Chapter 1: Introduction keeps that heading and is not given a second filename title.
Citations and cross-references
Not resolvedThe merger does not process bibliographies, citation keys, or cross-references — it concatenates text. Anything that needs renumbering or resolving (footnotes, \ref style links, citation managers) must be handled in your authoring toolchain before or after the merge.
An over-long single chapter
Char limitEach chapter is checked against your plan's per-file character cap (Pro 5,000,000; Pro + Media 20,000,000). A very long chapter over the limit stops the merge with a per-file error; split it with md-splitter first.
Frequently asked questions
Does the merger preserve my footnotes?
It preserves them as text — but only as text. The merger concatenates chapters verbatim and does not renumber or de-collide footnotes. If two chapters both use [^1], those labels and definitions clash in the merged file. Renumber footnote labels to be unique across chapters (for example [^1-1], [^3-1]) before merging.
How do I set the order of my chapters?
Chapters merge in the order of the file list you select, and there is no drag-to-reorder control. Prefix chapter filenames with zero-padded numbers (01-introduction.md, 02-literature-review.md) so they sort into submission order before you select them.
What separates one chapter from the next?
A Markdown horizontal rule — the merger joins files with \n\n---\n\n, so a --- line divides each chapter. Chapter titles come from each file's own H1 or, when missing, from the filename.
Will an untitled chapter get a heading?
Yes, with Add H1 from filename when missing on (the default): a chapter file with no # line gets # <filename> prepended, extension removed. Chapters that already have their own H1 are left unchanged.
Does it change my section numbering or heading levels?
No. Heading levels are preserved exactly. If you need to demote chapter headings — say, so every chapter H1 becomes an H2 under a single thesis title — run each chapter through md-heading-shifter before merging.
Can I merge chapters on the free plan?
No. md-merger is a Pro tool, and merging multiple files requires a Pro subscription. The free plan supports single-file markdown operations only.
How many chapters can I merge at once?
Pro allows up to 10 files, Pro + Media up to 50, and Developer is unlimited. A typical thesis of five to eight chapters fits Pro; if chapters plus appendices exceed the cap, pre-merge the appendices or use a higher tier.
How do I get a PDF or Word file for submission?
The merger outputs Markdown only. Convert the merged file with md-to-pdf-academic for a submission PDF, or md-to-docx for the Word file many university portals require.
Is my unpublished research uploaded anywhere?
No. Markdown tools run entirely in your browser. Chapter files are read locally and merged in the page — nothing is sent to a server, which matters for unpublished work under embargo.
Does it handle my bibliography or citations?
No. The merger does not resolve citation keys, build a bibliography, or renumber cross-references. Manage those in your citation tool or authoring pipeline; the merger only concatenates the Markdown text.
How is the contents outline built?
After merging, the tool scans every heading H1–H6 (ignoring headings inside code fences) and prepends ## Table of Contents with a - [Heading](#anchor) link for each, indented two spaces per level. Anchors are the heading text lowercased with spaces turned into hyphens.
Can I split a combined thesis back into chapters?
Yes. md-splitter breaks one file into several at a chosen heading level — split at H1 to recover one file per chapter, the inverse of this merge.
Privacy first
All Markdown processing runs locally in your browser using JavaScript. No file is ever uploaded to JAD Apps servers — only metadata counters are saved for signed-in dashboard stats.