Compare versions
Put any two versions of a file side by side, or read them as one merged document.
How to reach it
Compare Versions in the version rail.
Choosing versions
The panel header has two rows: the newer version on top, the older one below, separated by vs. Each row shows chips for the five most recent versions, with a … to reach older ones.
Unified vs. side-by-side
A toggle switches between Unified and Side-by-side; your choice persists across files.
For Markdown files, Unified renders the merged result as a formatted document with additions and
removals marked inline, so you can read the change the way it will actually look. .yaml and
.json files only offer source views in either mode — there is no rendered form for them.
Navigating
Click any marker on the rail to scroll straight to that change, landing it in the top quarter of the viewport.
When a version is only a rename
If the two versions you're comparing sit at different paths — the file (or a folder it's in) was
renamed or moved between them — the panel says so above the diff: "Only the file was renamed:
<old path> → <new path>" when nothing else changed, or "Renamed from <old path>" alongside
the normal diff when it did. Paths are shown relative to the repository root.
When to use it instead of View last changes
Compare Versions lets you pick any two versions, not just the current one against its baseline — useful for checking what changed between two specific points in a file's history. It works the same way whether the versions are Git commits or automatic snapshots; see Versions and Git history for how those are recorded.
Limits
- No rendered Unified view for
.yamland.jsonfiles — see YAML and JSON files. - For a quick look at only what's new since the last version, without picking two versions yourself, use View last changes instead.