Mastering LaTeX for Academic Papers: A Practical Guide
LaTeX is non-negotiable in most STEM fields, yet most graduate students learn it by copy-pasting and crashing. Here is the minimum LaTeX you need, the workflow that prevents 2 a.m. compile errors, and the templates worth keeping.
1. Why LaTeX Is Worth Learning Once and Properly
In math, physics, computer science, statistics, and most engineering fields,
conferences and journals expect LaTeX submissions. Word breaks on long
equations, stops being reliable past 60 pages, and makes citation management
a nightmare. LaTeX is the opposite: ugly to start, but stable at 200 pages,
mathematical typesetting that nothing else matches, and bibliography management
that scales to a PhD thesis. The investment is one focused weekend; the
payoff is the rest of your career.
When to Use LaTeX (and When Not To)
- Use it: papers with equations, theses, anything submitted to a STEM venue
- Use it: anything you will revise for years (thesis, book chapter)
- Skip it: one-off memos, slide decks (use Beamer only if you already know it), grant cover letters
- Skip it: documents your collaborators must edit and they only know Word
2. The Minimum Preamble You Should Memorize
Most LaTeX problems come from copy-pasting an unfamiliar preamble. Build
your own minimum and reuse it. For a typical paper you need: a document
class (`article` or the venue's class file), `inputenc`/`fontenc` for
encoding, `amsmath`/`amssymb` for math, `graphicx` for figures, `booktabs`
for tables, `hyperref` (load it last) for links, and `cleveref` for smart
cross-references. That is roughly ten lines and covers 80% of papers.
Add packages only when you hit a real need — never preemptively.
Packages You Actually Need
- amsmath, amssymb — equations and symbols
- graphicx — including figures
- booktabs — readable tables (toprule, midrule, bottomrule)
- hyperref — clickable cross-references and DOIs (load last)
- cleveref — write \cref{eq:1} instead of Equation~\ref{eq:1}
- siunitx — numbers and units (3.5\,\si{\meter\per\second})
- biblatex with biber — modern citations, far better than plain bibtex
3. Set Up the Workflow Once, Stop Fighting It
Decide between Overleaf and a local install in week one and stop relitigating.
Overleaf wins for collaboration, advisor edits, and zero install pain — and
its free tier handles most papers. A local install (TeX Live on Linux/macOS,
MiKTeX on Windows) wins for speed, version control, and working offline. If
you go local, use VS Code with the LaTeX Workshop extension or TeXShop, set
`latexmk -pdf` as your build command, and never compile with `pdflatex` by
hand again. Both setups should be wired to a Git repo from day one — no
exceptions.
4. Math Typesetting: The 20% That Covers 80%
You do not need to memorize the whole `amsmath` reference. The constructs
you will actually reuse: inline math with `$...$`, display math with
`\\[ ... \\]` (never `$$...$$` — it breaks spacing), numbered equations with
`equation`, multi-line equations with `align`, matrices with `pmatrix`/`bmatrix`,
cases with `cases`, and `\\text{}` inside math for words inside formulas.
Learn `\\operatorname` for custom operators, `\\mathbb{R}` for blackboard
bold, and `\\mathcal{L}` for caligraphic — that is 90% of paper-grade math.
Math Style Rules Reviewers Notice
- Variables in italic, operator names (sin, log, argmax) upright
- Use \,\mathrm{d}x instead of dx for differentials
- Use \left(...\right) only when delimiters need to grow
- Number only equations you reference; otherwise use equation*
- Punctuate display equations as if they were sentences
5. Figures and Tables That Do Not Embarrass You
Figure rules: vector formats (PDF, EPS) over raster (PNG) whenever possible;
use `\\includegraphics[width=\\linewidth]{...}` so figures resize with the
column; always include a `\\label{fig:name}` immediately after `\\caption{}`,
not before. Table rules: never use vertical rules; use `booktabs` with
`\\toprule`, `\\midrule`, `\\bottomrule`; right-align numerical columns; and
put units in the column header, not in every cell. The single biggest table
improvement is replacing `\\hline` everywhere with three booktabs rules.
6. Citations Without Tears: BibLaTeX + Biber
Stop using plain BibTeX in 2026. BibLaTeX with the Biber backend handles
Unicode, modern citation styles, and large `.bib` files without choking.
Pick one citation manager (Zotero, JabRef, Bibdesk) and let it own your
`.bib` file — never edit by hand for long. Use a stable citation key
convention: `lastnameYEARkeyword`, e.g. `vaswani2017attention`. Cite with
`\\textcite{vaswani2017attention}` for narrative citations and
`\\parencite{...}` for parenthetical. Most of the "weird citation rendering"
stories you have heard come from mixing styles or letting your manager
auto-overwrite the `.bib`.
Bibliography Hygiene
- One .bib file per project, version-controlled
- Stable lastnameYEARkeyword keys — never auto-generated UUIDs
- Title fields wrapped in {{Double Braces}} to preserve capitalization
- Pre-print + published version: keep both, cite the published one
- Run a 'find unused entries' check before submission
7. Collaboration, Version Control, and Conflict Avoidance
LaTeX plays well with Git only if you write it Git-friendly. Hard rules:
one sentence per line in the source (so diffs are sentence-level, not
paragraph-level), never let your editor auto-wrap, and put figures, the
`.bib`, and the `.tex` files in the same repo. For multi-author papers,
agree up front on whether comments live as `% TODO(name): ...` lines or as
`\\todo{}` macros. When merging, conflicts on line-wrapped paragraphs are
the single most common pain — switching the whole project to one-sentence-
per-line removes it. If you collaborate on Overleaf, still link it to a
Git repo so you have history outside Overleaf's UI.
8. Compile Errors: A 60-Second Triage
When the build fails, do not scroll through the log line by line. Search
for the first `! ` (exclamation-space) — that is the actual error; everything
after is downstream noise. Most errors are in three families: a missing
package (install or `\\usepackage`), a missing closing brace (look at the
line number, then the previous five lines), and a citation key that does
not exist in the `.bib`. If `hyperref` is unhappy, make sure it is loaded
last. If math fails inside a footnote or caption, wrap the whole math
expression in `\\protect`. Beyond these, delete the `.aux` and `.bbl` files
and rebuild — that fixes a surprising number of phantom errors.
PhD graduate who spent years tracking conference deadlines across computer science and engineering. Built ScholarDue after missing a submission window in the final year of candidacy and realizing no single tool tracked CFPs, extensions, and notification dates in one place.
Learn more→