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; filter them by severity 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. Ask the assistant to explain or fix a specific problem — or all of them — straight from the Problems list.
5. While a compile runs, click Compiling… in the status bar or on the PDF pane's build button to stop it.
6. Open the compile menu beside the Compile button and choose Clear cache and recompile when a build seems to be reusing stale auxiliary files.

Ctrl+S or Ctrl+Enter compiles the project; Ctrl+Alt+S stops a running compile; F8 and Shift+F8 go to the next and previous problem.

Check the PDF before you submit

Project checks has four tabs: Source checks reads the source without compiling, References verifies the bibliography, PDF reads the compiled PDF itself, and the last compile's warnings, for what a publisher's checker or a reader would notice, and Last compile lists the compile's own errors and warnings.

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. Turn on Anonymous submission on the Source checks tab 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.

How to do it

1. Open Project settings and set the root .tex file — the one 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; 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 that apply only to their browser.

How to do it

1. Turn on Auto compile to rebuild after you stop typing, or leave it off and build deliberately.
2. 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 click anywhere in the PDF to jump back to its source line.
4. Download the compiled PDF from the project menu or open it in its own browser tab for printing.

Ctrl+J 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 Ctrl+J jumps back to the source from the selected text or the middle of the view; Ctrl+F opens Find in PDF.