Help Center

Clear, practical guides for writing, compiling, and sharing LaTeX and Typst projects.

Compile to PDF

Build a LaTeX or Typst document, read the log, and choose how it is compiled.

Build and read the result

A compile returns the PDF plus the full log, without leaving the editor.

How to do it

  1. Compile from the keyboard, the status bar, or the PDF pane's build button.
  2. Errors and warnings are grouped in the Problems tab, together with what Source checks and References found; filter them by level or by text, and use Go to source to reach the line.
  3. Open the Output tab for the raw log (latexmk's for LaTeX, Typst's own messages for Typst) when a message needs more context than the grouped view gives.
  4. Open More actions on an error and choose Explain or Fix to ask the assistant about that one, or choose Fix all in the Problems header to have it fix every error.
  5. Some problems come with a button that fixes them in one step, such as Add \usepackage{…} or Switch to XeLaTeX: choose it to make that change to the source.
  6. While a compile runs, click the compile item in the status bar, which shows the stage it has reached, or Compiling… on the PDF pane's build button to stop it.
  7. Open the compile menu beside the Compile button and choose Clear cache and recompile when a build seems to be reusing stale auxiliary files.
  8. If the server does not have a font the document asks for, a notice names the font: upload its font files to the project's fonts/ folder, or compile with the desktop app on a computer that has it installed.

or compiles the project; stops a running compile; and go to the next and previous problem.

Check the PDF before you submit

Project checks has three tabs: Source checks reads the source without compiling, References verifies the bibliography, and PDF reads the compiled PDF itself for what a publisher's checker or a reader would notice, with the compile's own errors and warnings under Compile log at the bottom.

How to do it

  1. On the Source checks tab, press Run checks to scan the root document and its dependencies: duplicate labels and bibliography keys, citations and references that are not defined, files, images and bibliographies that may be missing, and packages that need XeLaTeX or LuaLaTeX are listed.
  2. Compile, then open Project checks and choose the PDF tab.
  3. Fonts that are not embedded and Type 3 (bitmap) fonts are reported; they usually come from a figure exported by another program.
  4. Undefined references and citations, characters a font did not have, lines that run past the margin and pages of a different size are each reported once, with the first place to look.
  5. A figure or table taller than the page, a compile that still asks for another run, and a PDF left over from an earlier compile after a failed one are reported too.
  6. Open Submission settings above the tabs to choose a Submission target, a page limit and a paper size, which the PDF tab then checks, and turn on Anonymous submission to also be warned when the PDF's metadata names an author.

Choose the engine and root file

Compile settings belong to the project, so everyone working on it builds the same way. Each root file keeps its own engine, TeX Live and compile mode.

How to do it

  1. Open the compile menu beside the Compile button, or Settings, and set Root file to the .tex file that holds \documentclass and is passed to the compiler.
  2. Pick the engine: pdflatex, latex, xelatex or lualatex. Fonts loaded with fontspec need XeLaTeX or LuaLaTeX.
  3. Choose the TeX Live release (2024, 2025 or 2026); keeping an older one is the safest way to reproduce an old build.
  4. Set the compile mode: Normal for the real document, Fast (draft) for a quicker structural check.

Tune your own build loop

Alongside the project's settings, each person has compile preferences, under My compile preferences in the compile menu, that apply only to them in this project.

How to do it

  1. Turn on Auto compile to rebuild after you stop typing, or leave it off and build deliberately. Until you choose, it is on for a Typst project compiled in the page and off otherwise.
  2. In a LaTeX project, turn on Stop on first error when a long log makes the real cause hard to find.
  3. Jump from the cursor to the matching spot in the PDF, and double-click anywhere in the PDF, or Cmd/Ctrl-click it, to jump back to its source line.
  4. Choose Download PDF in the project menu to save the compiled PDF, named after the project, or open it in its own browser tab for printing.
  5. The compile's output (its log, PDF and auxiliary files) is kept in the .compile folder at the project root; files you put there yourself are never compiled or synced, so the Explorer does not let you add them.

jumps from the source to the PDF. With focus in the PDF, the arrow keys, Page Up, Page Down, Home, End and Space scroll, + and - zoom, 0 fits the width, and jumps back to the source from the selected text or the middle of the view; opens Find in PDF.

Questions, bugs, and ideasAsk the community, report a bug, or vote on feature requests on the JointTex forum.
Account, billing, or privacy?Email our support team about your account, subscription, or personal data.
[email protected]
JointTex

Browser compatibility

JointTex could not start

The application did not finish loading. Check your connection, then try again.

Supported versions

  • Chrome and Edge 88 or later
  • Firefox 84 or later
  • Safari and iOS Safari 14 or later
Reload