How to export your thesis to LaTeX, DOCX or PDF

Your thesis will spend most of its life as a living draft, but it ends as a file: one artefact, in one format, uploaded to one portal. Which format that should be, and how to produce it without mangling your bibliography or your figures, is a decision worth making early rather than the night before the deadline.

The three formats that matter are DOCX, PDF and LaTeX. Each exists for a different reason, each is required at a different point in the process, and each has failure modes that surface exactly when you have no time left to fix them.

This guide covers when each format is the right target, what to check before you export, and how to compile all three from a single grounded draft without maintaining three diverging copies of your thesis.

Which format does your university actually require?

Start with the regulations, not with preference. Submission requirements are set by your institution, and they are usually explicit:

• PDF is the near-universal requirement for final submission and examination copies, because it freezes layout, pagination and fonts exactly as you intend them.
• DOCX is commonly needed earlier in the process: supervisors who comment with tracked changes, editorial offices, and some repositories ask for an editable file.
• LaTeX source is rarely demanded by universities, but it is the standard working format in mathematics, physics, computer science and adjacent fields, and some publishers ask for it when thesis chapters become journal manuscripts.

Check three documents before you decide

Before committing to a format strategy, read three things: your university's thesis formatting regulations, the submission portal's list of accepted file types, and, if you plan to publish chapters, the author guidelines of your target journals.

These documents disagree more often than you would expect. A department that drafts in Word can still require PDF for examination; a portal that accepts PDF may cap file size in ways that force you to recompress figures; a target journal may want LaTeX even though your university never asked for it. Knowing the full set of destinations early lets you pick a workflow that can hit all of them from one source.

Write the answers down somewhere you will see them again. A one-page note listing each destination, its required format, and any page or size limits takes ten minutes to make and prevents the worst version of format trouble: discovering a requirement for the first time inside the submission portal, after the deadline clock has started.

Exporting to DOCX: for supervisors and tracked changes

DOCX earns its place through collaboration. Tracked changes and margin comments remain how most supervisors and committees give feedback, and a Word file is the format they can mark up without friction.

The classic DOCX failure is the bibliography. References pasted in as dead text drift out of sync with the chapters the moment you revise, and a supervisor who spots a cited-but-missing reference will start checking for more. Export with the bibliography generated from your citation data rather than typed, so every entry corresponds to a real source at the moment of export.

Also confirm that heading styles and numbering survive the export. Reviewers navigate a long document by its structure, and a DOCX whose headings are visually bold but structurally plain paragraphs is painful to work through and breaks automatic tables of contents.

Exporting to PDF: the copy your examiner reads

PDF is the format of record. It is what examiners read, what the portal archives, and what the library keeps. Its whole value is that it looks the same everywhere, which also means every flaw is frozen in place for every reader.

Treat the examination PDF as a print product even if nobody ever prints it. Read it on a different device from the one you wrote on, because viewer defaults differ, and the copy that matters is the one rendered on your examiner's screen, not yours.

Before you generate the final PDF, verify the pieces that go wrong most often:

• Fonts embedded, so the file renders identically on the examiner's machine and the print shop's.
• Page numbering matching your regulations, including roman numerals for front matter where required.
• Figures checked at full zoom rather than fit-to-width, so compression artefacts and fuzzy labels are caught before printing.
• Margins and line spacing per the formatting rules, which many universities specify precisely for binding.
• The table of contents regenerated after your final edit, not before it.

Exporting to LaTeX: full control over the final document

LaTeX is the right target when your field expects it, when your thesis is heavy with mathematics, or when you want deterministic control over layout and typography. It is also the format most likely to be requested when a chapter becomes a journal submission in a technical field.

Getting clean LaTeX out of a writing environment matters, because hand-converting a hundred pages of prose into markup is a week you do not have. A good LaTeX export gives you compilable source: document structure mapped to proper sectioning commands, citations as cite keys rather than baked-in text, and a bibliography your toolchain can regenerate. From there you can drop the source into your university's document class or a journal template and take over by hand where you want to.

One warning for first-time LaTeX users: do not switch formats late in the process for aesthetic reasons alone. If your thesis is nearly complete in another workflow and no requirement demands LaTeX, the typographic gains rarely justify relearning your toolchain against a deadline. LaTeX rewards those who commit early, not those who arrive in the final month.

How the Thesis Assembler compiles all three

In CiteDash, export is the last step of a pipeline rather than a conversion bolted on at the end. The Thesis Assembler compiles your thesis to DOCX, PDF or LaTeX from the same source, with the bibliography generated by citeproc in your chosen citation style.

Because citations in CiteDash are database objects that resolve to real papers, never free text, the bibliography in every export is built from verified citation data: no orphaned entries, no cited-but-missing references, and retracted papers blocked from citation before they can reach the reference list.

Twelve citation styles are supported, including APA, Harvard, MLA, Chicago in both notes and author-date forms, Turabian, IEEE, Vancouver, AMA, Nature and ACS, so a late style change is a recompile rather than a rewrite. For a step-by-step walkthrough of the compile flow itself, see our guide to compiling your thesis to DOCX, PDF or LaTeX.

Keeping the bibliography correct across formats

The bibliography is where multi-format exports most often go quietly wrong, because each format treats references differently: DOCX wants formatted text, PDF wants the final rendering, and LaTeX wants source that a bibliography tool can process into either.

The protection is to keep one canonical citation record and derive all three outputs from it. Style changes, added sources and deleted chapters then propagate everywhere automatically instead of being patched by hand in three files. If your reference data lives in Zotero, Mendeley or a BibTeX file today, import it and keep that single source of truth rather than maintaining parallel lists.

Whatever tooling you use, never edit a generated bibliography by hand. The moment you do, it stops being derivable from your citation data, and every future recompile either overwrites your fixes or silently diverges from them.

Pre-export checklist

Run this list before you generate any file you intend to send anywhere:

• Regulations re-read: file type, margins, spacing, title page wording, page numbering scheme.
• Every citation resolves: no placeholders, no sources cited in text but missing from the reference list, and none listed but never cited.
• Retraction sweep: confirm nothing in the bibliography has been retracted since you added it.
• Figures and tables numbered consecutively and every one referenced in the text.
• Front matter complete: abstract, declarations, acknowledgements, and any required AI use disclosure.
• One full read of the compiled output rather than the editor view, because export is a rendering step and rendering has bugs.

Common thesis export problems and quick fixes

Most export failures fall into a handful of recurring patterns, and knowing them in advance turns a panic into a five-minute fix:

• Broken cross-references: chapter, figure or equation references showing as errors or question marks usually mean the document was compiled before all its parts were updated. Regenerate everything, then recompile.
• Bibliography entries missing or doubled: almost always a citation data problem rather than a rendering one. Fix the source records and recompile; never patch the output file.
• Fonts substituted in the PDF: the viewer's machine replaced a font that was not embedded. Re-export with embedding on and check again on a different device.
• Figures blurry in print but fine on screen: the export downsampled images. Re-export at print resolution and verify at full zoom.
• Page numbers drifting from the table of contents: the contents were generated before final edits. Regenerate the contents as the last step before export, every time.

Export early, export often

Do not treat export as a submission-day event. Compile a full PDF at the end of every chapter: you will surface layout problems, missing figures and bibliography gaps while they are cheap to fix, and you will always hold a complete, submittable artefact if life intervenes near the deadline.

Frequent compiles also change how you revise. When the rendered document is always a minute away, you catch the reader-facing problems (a table split across pages, a heading stranded at the bottom of a page, a figure caption drifting from its figure) that never show up in an editing view.

The chapter-end compile is also a natural moment for the other hygiene work this guide has mentioned: regenerate the bibliography, re-run your citation checks, and confirm the front matter still matches reality. Bundling these into one recurring ritual means none of them is ever more than a chapter out of date.

When the final file is ready, CiteDash also covers the last mile: originality pre-checks, AI use disclosure generation, and Submission Readiness checks that run before you upload anything to the portal. The export is the artefact; the checks are what let you send it with confidence.