Browse your Notion backup offline

A backup is useful only if you can still read it. Open your copy with Notion closed and the network off.

The question no backup tool answers in time

Every backup tool reports that the copy succeeded. None of them can tell you whether the copy is complete, because the only way to know is to read it back. Most tools turn that into a restore, on a day when something has already gone wrong. Silent failures look like this: a page you forgot to share, a database that returned half its rows, a file that was listed but never fetched. The backup log reports success either way.

NotionManager does it differently. Every finished backup is something you can open. The local copy is browsable as soon as it exists, and even while the backup is still running. NotionManager renders it to look as close to Notion as it can. You find the gaps on a Tuesday afternoon while you are reading, not during an incident while you are restoring.

What you get

The backup repository is not just a folder of files. You can open it and read your workspace as it stood at each run.

  • Pages as pages

    Read any backed-up page with its text, its nesting and its subpages intact. The colours, the styles and the layout are the same as in Notion.

  • Databases as databases

    Open a backed-up database and read every view, every data source and every row of each data source in full.

  • Relations intact

    Follow a relation from one page to another inside the copy. Mentions, references, parent and child pages and database relations are all kept, and the copy renders each one with the right style.

  • Every version is a visual history

    Each run is a snapshot of your workspace. Switch between versions easily and read how a page changed over time, so you keep a history and not just the latest state.

  • Reachable from your other devices

    Turn on remote browsing and the machine holding the copy renders it for the browser next to you. Your original data never travels, and only the rendered page does. A laptop, a tablet or a colleague in the same office can then read it, if your licence includes remote browsing.

Opening a copy

Browsing is part of the application, not a separate restore step. It is always available, with nothing to unpack and nothing to import.

  1. 1

    Choose your profile

    Every finished backup sits under its profile, with the pages, databases and versions it holds.

  2. 2

    Double-click the task

    The browsing window opens on that copy. Everything is read from your own disk, with no connection to Notion.

Read it offline, on purpose

Browsing never contacts Notion, and it does not need an internet connection. That is deliberate, not an implementation detail. If you chose not to download external media files, you cannot open those files offline, but the pages themselves are unaffected.

NotionManager renders the copy to match the way Notion looks and behaves, as closely as it can. Browsing locally is almost no different from browsing in Notion.

When the copy needs to travel

Reading at the machine covers only half the cases. The device that needs the copy is often not the one holding it. A laptop across the room, a tablet on the sofa, or a colleague in the same office who needs one page: none of them should have to install anything or wait for somebody to send a file.

That is what remote browsing is for. Switch it on and the machine that already holds the copy serves it to any device on a network you trust. You get the same pages, the same databases and the same versions. The data never leaves the machine it lives on, and only the page you are reading crosses the network. Browsing, opening and full-text search across the whole snapshot all work the same way as they do locally.

Remote browsing is off until you turn it on. When it is on, you choose the network interface it listens on and the password that protects it. Remote browsing uses Basic authentication, so only someone with the password can read the copy. Basic authentication is weak, so use it only on a network you trust: a home or office LAN, or a VPN you already run.

What remote browsing adds

  • Nothing to install

    The other device needs a browser, not a client. Open the address and the snapshot is there.

  • Every local feature, remote

    Browsing, following links and searching across the whole copy all work from the device in your hand, not only from the machine that holds the copy.

  • You choose the port and the IP address

    The listener binds to the network address and port you pick, so you decide which network can reach it.

  • Simple password protection

    Basic authentication protects access with a password you set during configuration, so the copy is not open to everyone on the network. You can switch it off at any time.

See your own backup

Download NotionManager, finish one backup, and then read it locally.

Where to go next

Frequently asked questions

Do I need Notion or an internet connection to browse a backup?

No. Browsing reads the local copy only and never calls the Notion API. Disconnect the machine and everything you backed up is still there to read.

Is the browsable copy editable, so my archive could drift?

No. Browsing only reads the copy. It never rewrites the backup the copy came from, so an old version stays exactly as it was and you can read it at any time.

Can I read a backup from another device?

Yes, that is remote browsing. Turn it on and the machine holding the copy renders the snapshot for the browser on your other device. Nothing is installed there, and your original data never leaves the machine that holds the copy. You can choose the network interface and the port it listens on, and it uses Basic authentication. Remote browsing and its search are part of a paid licence.

Can I check a backup before trusting it?

That is what this feature is for. Open the newest run, look around, then check the numbers against your workspace. If something is missing, you found it in time to run the backup again.