How to convert thesis chapters to a print-ready academic pdf
- Step 1Load one chapter — Paste the chapter's Markdown or drop a single
.mdfile. Convert chapters individually; the tool does not combine files into one document. - Step 2Remove the metadata block — If the chapter file begins with a
---YAML block, strip it — the academic renderer does not remove frontmatter and will turn it into a stray rule and a garbled heading at the top of the PDF. - Step 3Render with the academic theme — Run the tool. marked converts the Markdown to HTML and the serif stylesheet is applied, then the result loads into a sandboxed preview frame.
- Step 4Proof the preview — Check that equations and footnote markers (which appear as raw text) are where you expect, and that section headings and tables look right. Fix the source and re-run as needed.
- Step 5Save as PDF — Click 'Print to PDF', then pick 'Save as PDF' in your browser's print dialog. That step, not the tool, creates the actual file.
- Step 6Hand to your advisor — Name the file by chapter and date so your supervisor's annotations map back to a specific draft. Repeat per chapter as your dissertation progresses.
How a chapter's Markdown maps to the academic PDF
The serif theme's fixed styling — none of these are configurable in the tool.
| Chapter element | Markdown | Rendered as |
|---|---|---|
| Chapter title | # Chapter 3: Methods | 2em serif heading with a 2px underline |
| Section heading | ## 3.1 Participants | 1.5em serif heading with a 1px underline |
| Body prose | plain paragraphs | Georgia/Times, 12pt, 1.7 line-height, color #111 |
| Results table | GFM pipe table | Bordered table, header row shaded #f0f0f0 |
| Block quotation | > … | Left 4px border, indented, color #555 |
| Code/output listing | fenced block | Gray #f6f8fa monospace box, no highlighting |
Thesis features: what survives, what does not
Based on the marked v14 default parser the tool uses.
| Feature you might use in a thesis | Status | Result in PDF |
|---|---|---|
| Numbered section headings (typed) | Supported | Rendered as you typed them |
| Methods/results pipe tables | Supported | Real bordered table |
Statistical notation $\sigma^2$ | Not rendered | Prints literally with dollar signs |
Footnote citations [^1] | Not rendered | Prints as raw [^1] marker |
BibTeX @cite keys | Not processed | Keys pass through unchanged |
| YAML metadata header | Not stripped | Becomes rule + garbled heading |
| Figures via relative path | Broken in preview | Use absolute URLs instead |
Chapter size limits by plan
Character count is capped independently of file size.
| Plan | File size | Character limit | Files per run |
|---|---|---|---|
| Free | 1 MB | 500,000 chars | 1 |
| Pro | 10 MB | 5,000,000 chars | 10 |
| Pro-media | 50 MB | 20,000,000 chars | 50 |
| Developer | 500 MB | Unlimited | Unlimited |
Cookbook
Chapter-level scenarios a graduate writer actually hits, with exact source-to-output behaviour.
A methods table renders as a real table
Your participant-demographics or design table in GFM pipe syntax becomes a bordered table with a shaded header — appropriate for a methods chapter.
Markdown source: ## 3.1 Participants | Group | n | Age M (SD) | % Female | |-------|----|-----------|----------| | A | 30 | 21.4 (2.1)| 60 | | B | 28 | 22.0 (1.9)| 54 | PDF output: 3.1 Participants (serif 1.5em, underlined) [ bordered table, gray header row, serif body ]
Statistical notation prints literally
There is no math typesetting. Greek symbols and dollar-delimited expressions in a results chapter survive as raw text — plan around it.
Markdown source: The variance was $\sigma^2 = 4.3$, with $p < .05$. PDF output (literal): The variance was $\sigma^2 = 4.3$, with $p < .05$. Fix: spell out as 'variance = 4.3 (p < .05)', or keep equations as images for the review draft.
Footnote-style citations show as markers
A common thesis pattern — footnote citations — does not render. Markers and notes both print as plain text.
Markdown source: This aligns with prior findings[^2]. [^2]: Patel & Ng (2021). PDF output (literal): This aligns with prior findings[^2]. [^2]: Patel & Ng (2021). Fix: inline as 'This aligns with prior findings (Patel & Ng, 2021).' or preprocess with md-footnote-linker.
Delete the YAML header before exporting
Chapter files committed to a repo often carry a metadata block. Leave it in and the PDF opens with a broken heading.
Markdown source: --- chapter: 3 title: Methods status: draft --- # Chapter 3: Methods PDF output (broken): [ horizontal rule ] chapter: 3 title: Methods status: draft <- garbled H2 Chapter 3: Methods Fix: remove the --- block, or build/keep it separately with md-frontmatter-builder.
One chapter per run — merge first for a full draft
To give your advisor the whole thesis as one PDF, concatenate the chapter files before converting; this tool will not accept several at once.
Step 1 — md-merger (in order): 00-abstract.md 01-intro.md 02-litreview.md 03-methods.md -> thesis-draft.md Step 2 — md-to-pdf-academic: thesis-draft.md -> Print to PDF -> thesis-draft.pdf
Edge cases and what actually happens
Math and statistical notation are not typeset
Not rendered$\sigma^2$, $p < .05$, and $$…$$ print as literal text — no KaTeX/MathJax runs. For a stats-heavy results chapter, spell out values in prose or keep equations as figures. md-math-normalizer only standardises delimiters for a downstream renderer; it does not typeset here.
Footnote citations stay as raw markers
Not renderedThe default parser has no footnote extension, so [^2] and its definition both print verbatim. Convert to inline author-date citations or run md-footnote-linker first.
Chapter frontmatter renders into the body
By design (not stripped)A leading --- YAML block becomes a horizontal rule plus a garbled heading. Strip it from the printable chapter or manage it with md-frontmatter-builder.
Whole-thesis conversion in one go
RejectedThe tool takes one document per run. Assemble chapters with md-merger in reading order, then convert the single merged file.
Chapter exceeds the character limit
ErrorA chapter over the plan's character cap (500,000 on Free) is rejected with the count and limit named — usually caused by embedded base64 figures. Move figures to external URLs or upgrade.
Figures referenced by relative path don't appear
Broken (expected)Relative ./figs/… paths have no base to resolve in the preview frame. Use absolute https:// image URLs, or rewrite paths with md-image-path-rewriter.
Code/output backgrounds print white
Expected (browser-controlled)Browsers drop background colours from print by default. Enable 'Background graphics' / 'Print backgrounds' so code boxes and table-header shading appear in the saved PDF.
Pagination splits a table awkwardly
Expected (browser-controlled)Page breaks follow CSS print rules executed by the browser; the tool does not insert per-table break hints. Reorder content or accept the dialog's pagination — it is the same engine that prints any web page.
Output is print-styled HTML, not a saved file
ExpectedThe tool styles your chapter into a print frame; the .pdf is created when you choose 'Save as PDF' in the browser dialog. There is no server-side renderer, which is why the chapter stays local.
Frequently asked questions
Is it safe for an unpublished, embargoed chapter?
Yes. Conversion runs in your browser through the marked engine and the PDF is produced by your browser's print dialog — nothing is uploaded. This is the main reason graduate writers use it over an online converter that requires a file upload.
Does it render LaTeX-style statistics and equations?
No. $\sigma^2$ and $$…$$ print as literal text; there is no math engine. Spell results out in prose or keep equations as images for the review draft. md-math-normalizer can standardise delimiters for a separate LaTeX/Pandoc step.
Will my footnote citations format correctly?
No. [^1] markers and definitions print as raw text — the default parser has no footnote extension. Use inline author-date citations, or preprocess with md-footnote-linker.
Can I convert my whole thesis at once?
Not in one run — the tool accepts a single document. Merge chapters with md-merger in order, then convert the merged file to one PDF.
Why is there a stray line and broken heading at the top?
That is your YAML frontmatter. The academic path does not strip it, so --- becomes a horizontal rule and the metadata collapses into a garbled heading. Remove the block from the printable body, or manage metadata with md-frontmatter-builder.
Do my methods and results tables survive?
Yes. GFM pipe tables render as bordered tables with a shaded header row. Make sure the pipe alignment is valid Markdown and the table comes through cleanly.
What does the chapter actually look like?
Georgia (Times New Roman fallback) serif body at 12pt with 1.7 line-height, 25mm 20mm margins, underlined H1/H2 headings, and bordered tables. These are fixed by the academic theme.
How do I get page numbers for advisor comments?
Page numbers and headers/footers are browser print-dialog settings, not tool options. Enable them in the dialog before saving so your supervisor can reference specific pages.
My code listings print without their gray box — why?
Browsers strip print backgrounds by default. Turn on 'Background graphics' / 'Print backgrounds' in the print dialog to keep the code boxes and table shading.
How large a chapter can I convert on the free plan?
Up to 1 MB and 500,000 characters in a single file — far more than one chapter needs. Pro raises this to 10 MB / 5,000,000 characters. The character cap is independent of byte size.
Should I submit this PDF to my graduate school?
Most institutions require a specific Word or LaTeX template. Use this for advisor review and working drafts; for an editable Word version, convert with md-to-docx.
What if I want a non-academic look for a public summary?
Use md-to-pdf-modern for a sans-serif, contemporary style from the same Markdown source — the content is identical, only the theme changes.
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.