From LaTeX to Publication-Ready PDF

The whole reason most people tolerate LaTeX is the output. A clean LaTeX PDF export, with crisp math, consistent typography, and figures that don’t shift when you add a paragraph, is the payoff for all that markup. But getting from source to a file a journal or thesis office will actually accept involves more than clicking compile. Fonts get embedded or they don’t. Figures look sharp on screen and fuzzy in print. A reviewer asks for a single self-contained file and you realise you’ve only ever looked at it in a browser preview. This is a practical guide to producing a publication-ready PDF from LaTeX and avoiding the snags that bite at submission time.

How LaTeX actually becomes a PDF

It helps to know what’s happening under the hood. Modern LaTeX workflows usually run one of two engines:

• pdfLaTeX is the classic, fast default. It reads your .tex and writes a PDF directly. It works beautifully for most documents but has limited support for system fonts and Unicode.
• XeLaTeX and LuaLaTeX are newer engines that handle Unicode natively and let you use any OpenType or TrueType font installed on the system. If you need non-Latin scripts, custom typefaces, or advanced font features, these are the engines to reach for.

A typical compile also runs more than once. The first pass writes references and labels to auxiliary files; the second resolves them so your cross-references and table of contents come out right. Add a bibliography and you’ll run a bibliography pass (Biber or BibTeX) in between. Online editors handle this sequencing for you, which is one of the quiet conveniences of writing in the browser.

In inscrive.io, PDF export is built in and runs the multi-pass compile for you, so the file you download already has references resolved and the bibliography in place.

Getting fonts right

Fonts are the most common reason a LaTeX PDF export looks fine to you and gets bounced by a publisher.

Embed everything

Most journals and thesis offices require all fonts to be embedded in the PDF, so the document renders identically on any machine. If a font isn’t embedded, the reader’s system substitutes something, and your carefully set equations can shift or break. pdfLaTeX embeds fonts by default in nearly all cases, which is one reason it remains popular for submissions. You can verify embedding in most PDF viewers under the document properties or fonts panel: every font in the list should say “Embedded” or “Embedded Subset.”

Choose fonts deliberately

If you stick with pdfLaTeX, packages like lmodern or newtxtext/newtxmath give you clean, fully embedded text and math. If a journal mandates a specific typeface (Times-equivalent is a common one), newtx is a safe choice. With XeLaTeX or LuaLaTeX, you load fontspec and point it at the font you want:

\usepackage{fontspec}
\setmainfont{TeX Gyre Termes}

Whatever you pick, check the embedding before you submit. It’s a thirty-second check that prevents a rejection.

A subtle trap: math fonts and text fonts are configured separately. It’s easy to set a nice text font and leave the math in the default, which can look mismatched in a published article. If a venue cares about typography, make sure your math package matches your text choice. With newtx, loading newtxtext and newtxmath together keeps both consistent.

Figures that survive printing

Figures are the other classic failure point. The rule is simple: vector where you can, high-resolution raster where you can’t.

• Vector formats (PDF, EPS) scale to any size without losing sharpness. Plots from matplotlib, TikZ diagrams, and most charting tools can export to PDF. Use these for anything line-based.
• Raster formats (PNG, JPG) are for photographs and screenshots. If you must use them, supply at least 300 DPI at the final printed size. A 600-pixel-wide image stretched across a page column will look soft in print even if it’s fine on screen.

Include them the standard way and let LaTeX size them relative to the text width, so they stay consistent if the layout changes:

\usepackage{graphicx}
\begin{figure}[ht]
  \centering
  \includegraphics[width=0.8\linewidth]{figures/results.pdf}
  \caption{Measured response across the sample set.}
  \label{fig:results}
\end{figure}

A quick sanity check before submitting: zoom your exported PDF to 400% and look at every figure. Vector art stays crisp at any zoom. A raster image that turns to mush at 400% will look just as rough in a printed journal.

Meeting journal and thesis requirements

Every venue has its own rules, and the smart move is to read them before you write, not after. Common requirements you’ll run into:

• A specific document class or template. Many publishers ship their own .cls file. Use it from the start rather than reformatting at the end.
• PDF/A for archival theses. Some university repositories require PDF/A, a constrained PDF profile built for long-term preservation. You can produce it with the pdfx package, declaring the standard in your preamble.
• Page size and margins. US Letter versus A4 trips up cross-Atlantic submissions constantly. Set it explicitly in geometry rather than relying on a default.
• A single self-contained file. Reviewers usually want one PDF, not a ZIP. PDF export gives you exactly that, with figures and fonts baked in.

If you’re producing a thesis, the consistency of LaTeX is its biggest advantage over a word processor. For the broader case on that, see LaTeX vs Word for academic writing.

A clean export workflow

Here’s a workflow that produces a reliable LaTeX PDF export every time.

1. Pick your engine early. Default to pdfLaTeX unless you need custom fonts or full Unicode, in which case use XeLaTeX or LuaLaTeX.
2. Prefer vector figures, and keep any raster images at 300 DPI or higher.
3. Compile the full sequence so references, citations, and the table of contents all resolve. In an online editor this is automatic.
4. Open the exported PDF and verify: fonts embedded, figures sharp at 400%, page size correct, cross-references not showing up as ??.
5. Check the venue’s checklist one last time: template, PDF/A if required, single file, any size limit.

Do this and submission day is uneventful, which is exactly what you want it to be.

Where your document lives while you export

One thing worth thinking about, especially for unpublished work: where does the file get compiled, and where is it stored? If you’re producing a PDF of a manuscript that isn’t out yet, that source is sensitive. inscrive compiles and stores everything on EU soil, hosted by Hetzner in Germany and Finland in ISO 27001-certified data centres, with full GDPR compliance and no third-country transfers. Your unpublished draft doesn’t leave the EU on its way to becoming a PDF. The details are on the GDPR and security page, and PDF export is included on every tier, including the free one.

Compile headroom helps here too. Big documents with many figures and a long bibliography take time to build. inscrive allows 60 seconds per compile on the free tier and 480 seconds on Pro, so a heavy final export of a full thesis has room to finish rather than timing out at the worst moment.

The bottom line

A publication-ready LaTeX PDF export comes down to a few habits: the right engine for your fonts, embedded fonts you’ve actually verified, vector figures where possible, and a final check against the venue’s rules before you submit. The export itself is the easy part once the document is set up well. Get the fundamentals right and the file you hand to a journal or thesis office is the one they accept the first time.

Ready to write and export without the friction? Start on inscrive.io for free, PDF export included, no credit card, and keep your unpublished work in the EU from first draft to final file.

Further reading

• Overleaf alternatives in 2026: choosing an online LaTeX editor
• Managing your bibliography with Mendeley and LaTeX: get citations right before export
• inscrive pricing: compile times and what’s included on each tier