Markdown vs LaTeX: when to use each, and how to move between them.

“Markdown or LaTeX?” is usually asked as if the two were rival word processors. They are not. Markdown is a way of writing down the structure of a document so a program can turn it into a web page. LaTeX is a program that sets type, line by line and page by page, from a description of the document. The useful question is not which is better but which output you need, and once you know that, the two work well together.

The short answer

• Use Markdown when the document lives on the web, in a repository, or in a notes app: READMEs, docs, blog posts, meeting notes, anything reviewed in a pull request.
• Use LaTeX when the output is a typeset PDF with rules you do not set: a journal template, a thesis class, a book with cross-referenced figures and a bibliography.
• Use both when you think faster in Markdown but the reader needs a PDF: draft in Markdown, convert once, and finish in LaTeX.

What each one is actually for

John Gruber published Markdown in 2004 with a narrow goal: plain text that reads naturally as it is and converts cleanly to HTML. A # is a heading, a blank line ends a paragraph, a pair of asterisks means emphasis. The original description left many edge cases open, which is why CommonMark later wrote a precise specification, and GitHub extended it with tables, task lists and strikethrough as GitHub Flavored Markdown. Markdown says nothing about fonts, margins or page breaks: that is the renderer’s job, usually a stylesheet.

LaTeX is older and does far more. Donald Knuth wrote TeX in 1978 to typeset mathematics properly; Leslie Lamport built LaTeX on top of it in the 1980s so authors could describe a document’s logic — sections, figures, theorems, references — and let the engine decide line breaks, hyphenation, page breaks and where a float lands. A LaTeX file is a program: it has a preamble that loads packages, environments that open and close, and a compile step that turns it into a PDF.

So the honest comparison is between a markup language and a markup language plus a typesetter. That explains nearly every difference below.

The same section, written twice

Here is one results section — a heading, a table with aligned number columns and a footnote — in both languages. The LaTeX is exactly what our Markdown to LaTeX converter writes for the Markdown beside it.

The extra lines are not noise. {lrrr} states the alignment of each column, \toprule and \midrule are the rules a typographer would draw, \% exists because a bare % starts a comment in LaTeX, and the footnote is written where it is referenced. Markdown implies all of this; LaTeX has to be told. That is the trade in miniature: Markdown is faster to write, LaTeX gives you control over every one of those decisions.

Side by side

Math: the one place they already agree

Markdown has no maths syntax of its own. What GitHub, Obsidian, Jupyter and this site do is find $…$ and $$…$$ in the text and hand the contents to KaTeX or MathJax, both of which read LaTeX math notation. So $\frac{a}{b}$ means the same thing in both worlds, and a formula you type in Markdown survives a conversion to LaTeX untouched.

The agreement stops at the edge of the formula. LaTeX can number an equation and let you write \ref{eq:loss} three pages later; Markdown has no labels. LaTeX lets you define \newcommand{\R}{\mathbb{R}} once and use it everywhere; most Markdown renderers forget macros between formulas. And the delimiters differ in practice: AI tools often write \(…\) and \[…\], which LaTeX accepts but many Markdown renderers do not. Our Markdown cheat sheet lists the maths that renders reliably on the web.

Where Markdown runs out

The limits show up the moment a document has to look like a publication rather than a page:

• Cross-references. “See Figure 3” has to be typed by hand and goes wrong the first time figures move.
• Citations and bibliographies. Core Markdown has no \cite and no reference list. Pandoc adds a citation syntax as an extension, but it is not portable to other renderers.
• Figures and page layout. You cannot ask for an image at the top of the next page, two columns, a running header, or a page break that a renderer is obliged to honour.
• Theorems and numbered environments. Definitions, lemmas and proofs are LaTeX environments; Markdown only has quotes and lists.
• Templates. A journal or university supplies a LaTeX class; there is no Markdown equivalent you can submit.

Where LaTeX gets in the way

LaTeX’s power has a cost that shows up long before the layout matters:

• The first draft is slower. Every list needs \begin{itemize}, every table a column specification, and you check the result by compiling.
• Ordinary characters are special. % starts a comment, & separates table cells, _ and ^ only work in maths, and # is a macro parameter. Prose pasted from anywhere else breaks the build.
• Errors are cryptic. A missing brace on line 12 can surface as ! Missing $ inserted. on line 80.
• Collaborators may not know it. A co-author who writes Markdown or Word fluently can still be locked out of a LaTeX source.
• The web is an afterthought. LaTeX is designed for paper; a responsive web page from the same source needs a separate tool.

Pick by where the document ends up

Put those two lists together and the decision mostly makes itself. Ask where the document will be read and who else will edit it.

The hybrid workflow: draft in Markdown, typeset in LaTeX

The pattern that serves most technical writers is to keep the thinking in Markdown, where it is quick, and move to LaTeX once, when the structure has settled.

1. Write the draft in Markdown. Put the title, author and date in a YAML header so they become a title block later. Write formulas with $…$.
2. Convert it. Paste the draft into the Markdown to LaTeX converter. Article writes a complete document; Body only writes just the content, with a comment listing the packages it needs, for pasting into a template you already have.
3. Compile. The status bar tells you the engine — pdfLaTeX for Latin text, XeLaTeX for Chinese, Japanese or Korean — or click Open in Overleaf and let it build the PDF.
4. Continue in LaTeX. Add the labels, citations and float placement that Markdown could not express. From here the .tex is the source.

That last step matters: the conversion is one way. Going back and forth between Markdown and LaTeX on every edit loses whatever you added on the LaTeX side. If you prefer the command line, Pandoc does the same job:

pandoc draft.md --standalone -o draft.tex

Slides follow the same route. A Markdown outline maps naturally onto a Beamer deck, and Markdown to Beamer covers how headings become frames.

Going the other way: LaTeX to Markdown

Sometimes the paper already exists and you need it on the web, in a README, or as clean input for an LLM. Pandoc reads LaTeX:

pandoc paper.tex -o paper.md

Sections, emphasis, lists, simple tables and maths come through well. Expect to repair the rest by hand: custom macros either expand or vanish, \ref turns into a bare label, multi-row tables flatten, and figure placement is gone because Markdown never had it. Treat the output as a first draft of a web version, not as a second copy of the paper.

Frequently asked questions