Compare two backups, block by block
A backup shows what you had. A comparison shows what changed. Pick any two finished backups and NotionManager lines them up: the page tree first, then the exact blocks, properties and rows behind every difference.
A backup shows what you had. It cannot show what changed.
Two backups of the same workspace differ by everything that happened between them: a page was renamed, a paragraph rewritten, a database row quietly disappeared. Finding that by hand means opening two windows, scrolling in step, and remembering what the other side looked like a minute ago. It works for one page. It does not work for a workspace.
Backup comparison does the reading. Pick two finished backups and NotionManager aligns them by the IDs Notion gives every page and block. What exists only on one side is added or removed; what exists on both but differs is changed; everything else is counted as unchanged. You can stop at the structure, or open any shared page and read the edit in place.
Any two finished backups
The picker lists every finished backup you have, across every profile, newest first. The defaults are the two most recent runs: older on the left, newer on the right, the direction a diff is read. Either side can be replaced without leaving the page.
A run that failed or was cancelled is offered too. It is a fair question what it managed to capture, as long as you remember that whatever it did not reach will read as removed. Comparing across profiles works the same way, but page and block IDs are what make a comparison line up: the closest comparisons are between backups of the same workspace, while two unrelated workspaces will mostly show additions and removals rather than edits.
From two snapshots to one answer
Start from wherever you keep your backups. All three routes end on the same comparison page.
- 1
Set the two sides
In History, select exactly two backups and choose Compare. Or right-click a run in Recent Backups, set it as the left side, then compare another run against it. Both open the pair in the comparison view.
- 2
Read the structure
Each side shows the page and database tree with added, removed and changed nodes. Search both trees, expand the branch you care about, and use the counts in the toolbar to see whether the difference is one page or a hundred.
- 3
Open the page that changed
Double-click a node that exists on both sides. The page opens twice, side by side, with the changed blocks marked and the unchanged ones dimmed on request.
What the structure tells you
Added
A page or database that exists only in the newer backup. Counted in the toolbar and marked in the right-hand tree.
Removed
A page or database that exists only in the older backup. If something disappeared, this is where you see it first.
Changed
The same page exists on both sides, but its title, icon, cover, parent or last-edited time differs. Hovering the node shows the other side’s title.
A change deeper in the branch
A small dot on a branch means the difference is below the node itself. Expand it instead of opening every page in turn.
Unchanged
Counted, not listed as work. The point of a comparison is to let the untouched part recede.
Then read the actual edit
The tree says which page changed; the page comparison says what changed inside it. Both copies are rendered with the same renderer you browse with, each in its own scroll, side by side. Every changed block is highlighted where it sits. Turn on Highlight only differences and the untouched content fades, so one edited block does not hide in a long page.
Databases get the same treatment. The schema is compared property by property, rows are compared by ID, and both lists sit above the two tables: added, removed and changed, with the old and new value side by side. A row page shows its property changes in the same table. Titles, icons and covers are called out in the page header, next to the backup date and the last-edited time each side recorded.
What you want to know, and where the answer is
| Your question | Where to look |
|---|---|
| Which pages and databases appeared or disappeared? | The two structure trees and the added / removed counts. |
| Did this page’s title, icon or cover change? | The node status in the tree, then the tags in the page comparison header. |
| What changed inside the page? | The two rendered copies: added, removed and changed blocks are highlighted in place. |
| Did something change deeper in this branch? | The subtree dot on the branch; expand it and open the page. |
| Did the database schema change? | The schema changes table above the two database views. |
| Which rows were added, removed or edited? | The rows table, with the property diff for an individual row. |
| What did not change? | The unchanged count, and the dimmed content when Highlight only differences is on. |
A diff of snapshots, not a history of edits
A comparison shows the difference between two copies. It cannot show a change that was made and undone before the second copy ran: the two snapshots agree, and the comparison is right to say so. It is a lens on the versions you kept, not a replacement for version history.
That is also why retention matters. Two backups close together answer “what changed this week”; two far apart answer “what changed since the migration”. The comparison is only as useful as the versions you decided to keep.
See what actually changed
Download NotionManager, open Backup comparison, and put two finished backups side by side. The free edition compares as clearly as the paid ones.
Where to go next
Frequently asked questions
Do the two backups have to come from the same profile?
No. The picker covers every profile’s finished backups. Within one workspace is the common case; across profiles is useful when a copy was kept under another profile, but unrelated workspaces will mostly show additions and removals because their page IDs do not line up.
Does comparison change or restore anything?
No. It reads the two local copies and touches neither the backups nor Notion. Nothing is written back.
Which backups can I compare?
Finished runs: successful, failed or cancelled. A failed or cancelled run only contains what it managed to capture, so anything it did not reach will read as removed.
What does “changed” mean in the tree?
The title, icon, cover, parent or last-edited time differs. Content changes inside a page are not guessed from the tree: open the page to see them, and use the subtree dot to find the branch.
Can I compare more than two backups at once?
Two at a time. Replace either side with another run and compare again.
Is backup comparison included in the free edition?
Yes. Visual comparison of two backups is included in every edition, so a free copy can be checked against the next run.
Does it work on very large workspaces?
The comparison loads the page and database index for both sides and only loads a page’s content when you open it. Search and expand are there to narrow the view, but a very large workspace still takes a moment.