Help Center
Clear, practical guides for writing, compiling, and sharing LaTeX and Typst projects.
Troubleshoot problems
Resolve common compile, access, and workspace issues.
This guide is written for
Start with the details
Error messages normally identify the source file or action that needs attention.
How to do it
- Check the message, its referenced file, and the most recent edit.
- Reproduce it once deliberately, so you know whether it is the document or the moment.
- Try the relevant guide again; contact support with the project name and error details if the issue remains.
When a compile fails or stalls
A failed build and a busy build look similar in the status bar but need opposite responses.
How to do it
- For a failed build, open the Problems panel and start from the first error — later ones are often its consequences.
- Use the AI's Explain or Fix action on a diagnostic when the message itself is unclear.
- Compiles run one at a time per person, so a newer automatic compile replaces a waiting one and an explicit compile may ask you to retry in a moment.
- A message that the compile service could not complete the request points at the service, not at your document — try again, then contact support if it persists.
- A compile that was stopped for taking longer than the time limit, or for using up its space or memory, will not pass on a retry: look for a loop, an expensive package or very large images, or split the document.
- If a build keeps failing on stale auxiliary files, or jumps between the source and the PDF stop working, open the compile menu and choose Clear cache and recompile.
When the project itself is the cause
Some failures come from where files are or how much the project holds, not from the source on the line the error names.
How to do it
- A missing-file error right after you moved or renamed a file usually means a path still names the old place: choose Update on the notice that follows a move, or correct the path yourself (\input or \includegraphics in LaTeX, #include or #image in Typst).
- A warning that the project is near its size limit means new files and edits cannot be saved once it is full; delete files you no longer need or split the project.
- When the compile service is busy or unavailable, the notice points to the desktop app, which can compile with the LaTeX on your own computer; inside the app, a project set to compile on the server is offered Compile on this computer instead.
Access and connection problems
Not being able to open something is usually an account or connection state, not a lost project.
How to do it
- If pointing at the save dot in the status bar says you are working offline, keep writing: edits stay in the browser and sync when the connection returns.
- Avoid signing out while offline — signing out clears those local copies.
- A project you can no longer open reports that it cannot be found; ask the owner whether access changed or the project was moved to the Trash.
- An unverified email address or a suspended account blocks the whole app, not just one project.
When a Typst project behaves differently
A Typst project compiles in the page as you write and, in a browser, on the server for downloads, so most surprises come from which of the two made the preview.
How to do it
- The PDF does not follow your typing, or jumps between the source and the PDF do not work: the server is compiling the preview, not the page. Check Auto compile in the compile menu, update the browser and reload the page. A document with text the page's fonts do not cover is compiled on the server as well.
- A package not found error for an @local import is expected: only @preview packages are available.
- An imported ZIP or repository with several .typ files and no main.typ at its top level takes as its root the .typ file that no other one imports or includes. If that is not your document, open Project settings and choose the .typ root file.
- A message that the compile service cannot compile Typst documents yet comes from the service, not from your document: try again later.