Writing a Thesis in Markdown and Submitting It as Word

Plenty of researchers draft in Markdown and submit in Word, because the writing benefits from a distraction-free plain text format while the institution insists on .docx. The workflow is sound, but four things need planning: citations, footnotes, equations and the formatting requirements themselves.

Get those right and the conversion is the easy part.

Why draft in Markdown at all

Plain text is future-proof. A .md file written today will open in twenty years without anything special. Word documents from the nineties already cause trouble.

Version control works properly. Git can show you exactly what changed between two drafts, line by line. With a .docx you get “binary files differ”, which tells you nothing.

You write instead of formatting. There is no temptation to spend an hour adjusting margins when you should be writing chapter three.

Corruption risk is essentially zero. A plain text file cannot become unopenable the week before submission, which is a failure mode that has genuinely ruined people’s months.

Citations

This is where the workflow needs the most thought, and where Pandoc earns its place.

Keep references in a BibTeX file exported from Zotero, Mendeley or your reference manager. Cite in Markdown with a citation key:

Recent work has challenged this [@smith2024].

Then convert with Pandoc and a citation processor, naming the style your department requires. It formats every citation and builds the bibliography automatically.

Browser-based converters do not do citation processing. If your thesis has a bibliography, install Pandoc for the final conversion. For chapter drafts you are circulating to a supervisor, a quick browser conversion is perfectly adequate.

Footnotes

Markdown footnotes look like this:

The methodology follows established practice.[^1]

[^1]: See Appendix B for the full protocol.

Best quality mode turns these into real Word footnotes that renumber themselves when you insert one. A fast conversion keeps the text but places it inline, which is fine for a draft and not for submission. Know which you are getting; a converter that warns you when it has simplified something is doing you a favour.

Equations

Write mathematics in LaTeX, inline with single dollar signs and displayed with double:

The relationship $y = mx + c$ describes the line.

$$
\int_0^\infty e^{-x} dx = 1
$$

Converted properly, these become native Word equation objects your examiner can click and edit. Converted with a fast path, they stay as literal LaTeX, which is unacceptable in a submitted thesis. This is the single strongest reason to use best quality mode or Pandoc for the final version.

Meeting formatting requirements

Universities specify margins, line spacing, font, and often a title page layout. Do not fight this in Markdown; it is not what Markdown is for.

Instead, get the department’s Word template, or build one once from the requirements. Convert your Markdown to Word, then apply the template. Because the conversion produces real Word heading styles, applying a template restyles the entire document at once.

This is precisely why real heading styles matter. If your headings were merely large bold text, the template would do nothing and you would be formatting a hundred pages by hand.

A workflow that works

Write each chapter as its own Markdown file. They stay manageable, and version control diffs stay readable.

Keep the bibliography in one BibTeX file, updated as you read rather than at the end.

Convert drafts quickly with the Markdown to Word converter when a supervisor wants something readable. Speed matters more than perfection for feedback.

Use Pandoc with your reference document and citation style for the final submission. That is when citations, footnotes and equations all have to be exactly right.

Do the final formatting pass in Word. Page numbers, the title page, the declaration, the table of contents. These are Word’s job.

Common problems

Citations appear as raw keys. The conversion ran without a citation processor. Use Pandoc with a bibliography file for the final version.

Equations are literal LaTeX. A fast conversion was used. Switch to best quality mode or Pandoc.

The contents page is empty. Headings are not real Word heading styles. This usually means the document was pasted rather than converted.

Figure numbering is wrong. Markdown has no automatic figure numbering. Pandoc with a cross-reference filter handles it, or number them in Word at the end.

Managing a thesis across many files

A thesis is too long for one file, and splitting it well makes everything downstream easier.

One file per chapter. Name them so they sort correctly: 01-introduction.md, 02-literature.md. Pandoc accepts them in order on the command line and produces a single document.

pandoc 0*.md --reference-doc=template.docx --citeproc -o thesis.docx

Keep heading levels consistent. If each chapter file starts at a first-level heading, chapter titles all sit at the same level and the contents page comes out right. Mixing levels between files is the most common cause of a malformed contents page.

Commit as you write. Every meaningful edit committed to Git means a readable history of how the argument developed, and a guarantee that no version is ever lost. This is the single largest practical advantage of drafting in plain text, and it costs nothing.

Convert regularly, not just at the end. A conversion problem found in month three is a small annoyance. The same problem found the week before submission is not. Convert a chapter early, check the citations and equations came through, and you have de-risked the entire workflow.

Supervisors rarely care what you draft in, provided what lands in their inbox opens in Word and has track changes available.

Frequently asked questions

Will my supervisor need Markdown? No. Send Word files. The format you draft in is your business.

What about track changes? Convert to Word, then use track changes normally. Bringing edits back into Markdown is possible with the Word to Markdown converter, though most people accept changes in Word once review starts.

Is this allowed? Universities specify the submission format, not how you produce it. Submitting a correctly formatted .docx satisfies the requirement.

What if I need LaTeX output instead? Pandoc converts the same Markdown to LaTeX, which is useful if a journal requires it.

A note on submission deadlines

Whatever your workflow, do the full conversion at least a week before the deadline rather than the night before. Conversion problems are quick to fix and slow to discover: a citation style that comes out wrong, an equation that did not convert, a contents page that will not generate.

None of those take long to correct with a week in hand. All of them are a crisis at midnight. Converting early costs an hour and removes an entire category of risk from the most stressful week of the project.