Convert TEX to PDF: Compile LaTeX Source Reliably

A TEX File Describes Pages; a PDF Captures the Pages TeX Actually Built

A .tex file is source for the TeX typesetting system, often using the LaTeX macro format. It contains readable prose mixed with commands such as \section, \cite, and \includegraphics. A PDF is the finished page description that a browser, printer, or submission site can display without knowing those commands. Converting TEX to PDF is therefore normally compilation, not a simple filename change: an engine reads the source, loads packages and fonts, resolves included material, places boxes and lines on pages, and writes the resulting PDF.

The engine choice changes what input is accepted. The TeX Users Group's LaTeX material notes that pdflatex produces PDF directly, while modern workflows may use XeLaTeX or LuaLaTeX when a document needs system OpenType fonts or more advanced Unicode handling. A source that works under one engine can fail under another because package drivers, font declarations, and image formats differ. Preserve the original project folder, not only the main TEX file: a paper may depend on .bib bibliography data, .sty packages, figures, custom class files, and files named by \input or \include.

Why Compilation Often Needs a Sequence of Runs Rather Than One Button Press

LaTeX does not know every page number on its first pass. It writes auxiliary information to files, then uses that information on a later pass to settle cross-references, contents entries, lists of figures, and citations. The LaTeX reference manual says a run produces the main output plus at least two auxiliary files, and that cross-reference information is among the data stored there. A common bibliography route is: run LaTeX to create an .aux file with citation requests, run BibTeX or Biber to create formatted bibliography output, then run LaTeX again, often twice, so labels and in-text references agree with final page positions.

This explains the familiar warning that a reference is undefined even though the label exists in the source. It is not always an error in the label; it can simply mean the project has not completed its required later pass. Conversely, running repeatedly cannot repair a misspelled label or a missing bibliography entry. Read the log for the first meaningful warning, confirm that \label comes after the counter-changing command such as \section or \caption, and make sure the cited key exists in the active .bib file. Then run the correct sequence again rather than guessing from the PDF alone.

Six Preflight Choices That Protect a TEX-to-PDF Submission

• Compile the root file: find the TEX file containing \documentclass and \begin{document}, not a chapter fragment intended for \input.
• Keep relative paths intact: figures and bibliography files are commonly named relative to the project folder; moving one TEX file alone breaks those links.
• Use the intended engine: an engine selected for Unicode fonts or a publisher class should not be replaced casually with another compiler.
• Run the bibliography tool when needed: BibTeX and Biber are separate processing steps, not packages that PDF compilation silently invents.
• Inspect warnings after success: a generated PDF can still contain unresolved citations, overfull lines, or substituted fonts.
• Archive the sources too: PDF is a good distribution artifact, while TEX, figures, class files, and a build note are the reproducible source record.

PDF Compatibility Depends on Fonts, Images, and the Exact Build Environment

The PDF may be portable, but it only reflects what the compiler could find. An image named results.png in the source must be present at the declared path and in a form the selected engine supports. A missing file usually produces a clear log message such as “File ... not found”; the fix is to restore the asset, correct its case and path, or change the source reference. Do not replace a missing diagram with a blank box just to get a clean-looking PDF unless the document owner explicitly accepts that loss. It may make a scientific result or contract materially incomplete.

Font behavior deserves the same check. TeX's classic Computer Modern family and package-supplied fonts are not the same thing as an arbitrary font installed on one author's laptop. If an engine cannot locate the requested font, it may stop or substitute something that changes line breaks and page count. Open the completed PDF on a second viewer, zoom in on equations and punctuation, and inspect the document properties or preflight report when a publisher requires embedded fonts. For a reusable workflow, write down the engine and package distribution version rather than calling the output merely “compiled with LaTeX.”

A reproducible build also separates generated clutter from source evidence. Files such as .aux, .log, .toc, and bibliography outputs help one compilation finish, but the main TEX, bibliography database, figures, and locally supplied class or style files are the inputs another machine needs. Keep the log when troubleshooting because it records the selected engine, package warnings, and failed path; do not mistake it for a substitute for the missing image or style file. Once a clean PDF exists, reopen the project from its archive folder and build it once more as a final completeness test. Record the result in the delivery notes.

How to Distinguish a Fatal TeX Error From a PDF That Merely Needs Page Review

A fatal error stops the run and usually points to a file and line near the first impossible instruction. “Undefined control sequence” commonly means a command was misspelled, a package defining it was never loaded, or a custom macro file was not found. The reliable fix is to examine the first error in the log and its surrounding source, then add the intended package or repair the macro name. Later log noise can be a cascade from that first failure. A missing closing brace can make TeX report trouble well after the actual typo, so count braces in the immediately preceding command before changing unrelated text.

An overfull \hbox warning is different: TeX completed the PDF but could not break one line within the chosen width. It often creates text protruding into a margin, particularly with a long URL, identifier, formula, or unhyphenatable word. Locate the reported line in the source and use an appropriate solution: allow a URL to break with a URL-aware command, revise the wording, add a legitimate discretionary break, or adjust a local layout rule. Do not globally shrink the entire document to hide one overflowing line. Separately, a “rerun to get cross-references right” warning calls for another build pass, not a layout edit.

LaTeX Source and Final PDF Compared at the Point of Delivery

Questions Before You Hand Off a Compiled TeX Document

Why are my citations shown as question marks?
Usually the bibliography step or a later LaTeX pass has not completed. Verify the citation keys and bibliography file, run the required bibliography tool, then compile again until the unresolved-reference warning clears.

Can I convert only one TEX file if the project uses figures and chapters?
Not reliably. The main file can pull in chapters, images, custom styles, and bibliography data by relative path. Send or preserve the full project tree with its original folder structure.

Does a PDF without errors mean it is ready to submit?
No. Check page margins, figure captions, URLs, references, page count, and font behavior. Warnings such as an overfull box can leave a PDF that opens correctly but has visible defects.

Should I use pdfLaTeX for every project?
Use the engine required by the document class, publisher, or font setup. pdfLaTeX produces PDF directly, but XeLaTeX or LuaLaTeX may be necessary for a project built around modern system fonts or wider Unicode support.

Is PDF enough for long-term preservation?
Keep it for access, but retain the TEX source, figures, bibliography, class files, and a note of the build engine. Those files allow a later reader to reproduce or update the document.