Find an earlier version

JointTex records versions automatically while you edit, so the question is never whether a moment was saved but how to find it.

How to do it

1. Open History in the Activity Bar to see recent activity, who made it, and whether it came from the web editor, the desktop app, Git, or the AI assistant.
2. Label a version as a milestone when you may need to find it later — a submission, a co-author handoff, a working draft.
3. Open a file's diff from a version to see exactly what changed rather than guessing from the timestamp.
4. Use the author and source to narrow a long list when several people and the assistant have been working.
5. Use Filter files and Filter authors to narrow the list, and switch History layout between Grouped and Detailed.
6. Right-click a milestone and choose Rename milestone… or Delete milestone…; deleting removes only the label, and the version it tags stays in history.

Restore what you need

Restoring is a normal edit, not a rollback of the world — it is recorded like everything else.

How to do it

1. Use Restore on a version to bring back the whole project when a whole direction was wrong.
2. Restore only one file when the rest of the project has moved on since.
3. Expect restoring to need edit access, and to appear in history itself, so it can be undone in turn.
4. Read the diff before restoring; the version you remember is not always the one you want.
5. Right-click a version or a milestone and choose Download as ZIP to get the project exactly as it was then, without changing anything; this works for viewers too.

Compare two versions as a marked-up PDF

A marked-up PDF shows what changed between two versions in the typeset document: additions are underlined and deletions struck through, in a PDF you can send with a revision.

How to do it

1. In History, choose Generate marked-up PDF…, or right-click a version or a milestone and choose Compare with current as a marked-up PDF. The Command Palette has the same thing as Compare versions (marked-up PDF)…, and the project menu as Download marked-up PDF….
2. Pick the Older version and the Newer version (Swap versions exchanges them), check the Root file if the dialog shows one, and choose Generate. It uses the project's compile settings.
3. Under Advanced, set Markup style to Underline and strike-through, Colour only, or Colour with margin bars, and set Equations to Mark whole equations, Mark inside equations, or Don’t mark equations.
4. When the notice says Marked-up PDF ready, choose Open to read it in a tab or Download to save it. The tab shows a Legend for Added and Deleted, and offers Download .tex, Regenerate, and Change versions….
5. Only changes in .tex files are marked. Other files that changed, a figure for example, are not marked, and when no .tex file differs there is nothing to mark.
6. If the marked-up PDF does not compile, choose View log to see why, or Retry in compatibility mode. If it takes longer than the time limit, try compatibility mode or compare fewer changes.
7. In a Typst project, typdiff does the marking: every changed .typ file of the project is marked, and a new file is marked as added throughout. There is no Advanced section, so no markup style to choose, and no compatibility mode; the tab offers Download .typ in place of Download .tex.
8. typdiff replaces equations, raw text and other code as a whole rather than marking inside them. A change that is only in code, an image path or a page margin for example, is not marked, and content removed from inside a call, such as a deleted table row, leaves no trace.

Track changes and comments

The Review section collects tracked changes and comment threads for the file you have open.

How to do it

1. Turn on Track my edits in Review so your changes arrive as suggestions instead of silent edits.
2. Accept or reject suggestions one at a time, or use Accept file and Reject all changes in this file for the file you have open.
3. While anything is pending, the strip under the editor shows how many changes wait in how many files: its arrows go to the previous or next change in any file, and its buttons accept or reject this file, or every file at once.
4. Select text and choose Comment to start a thread anchored to it. Tracking edits and deciding suggestions need edit access; commenting needs Can comment or Can edit, and a viewer can only read.
5. Replies stay attached to that text until someone resolves the thread.
6. On a thread, Draft reply has the AI write a reply for you to edit and send, and Address has the AI edit the manuscript to address the comment.
7. A resolved thread moves to Resolved comments, where Reopen brings it back. Show in PDF jumps to the passage in the preview.

With text selected, Ctrl+Alt+M adds a comment. On a line with a suggestion, Ctrl+Alt+Enter accepts the one nearest the cursor and Ctrl+Alt+Backspace rejects it.