Offline Mode

Work saved only in this browser, where a guest's new work starts, and how to move it to and from your account.

Applies To

Every liveworkspace app

Most knowledgebases are saved to liveknowledge's servers so you can reach them from any device and share them. Offline Mode is the opposite choice: a knowledgebase saved only in the browser you made it in, that is never stored on the server. It suits private, local-first work, simply trying liveknowledge out, or wanting a knowledgebase that physically never leaves your machine.

Creating an offline knowledgebase

Offline Mode is chosen per knowledgebase, so you can keep normal knowledgebases and ones kept Offline side by side.

  • If you haven't signed in, your new knowledgebases start Offline. Nothing you try out is sent to our servers until you choose to share it, sync it, or sign in and move it to your account. Everything you make from New Knowledgebase, and from the links that create a knowledgebase straight away (a template from the home page, say), starts Offline. Use Sync Knowledgebase from its Share dialog if you would rather it went to the server now.
  • Once you've signed in, new knowledgebases go to your account. To keep one only in this browser, choose Take Offline from its menu (see below).
  • A knowledgebase made inside a folder or a team goes to the server, whoever makes it, because that is where the folder or team lives.
  • The knowledgebase is written to your browser's own storage (IndexedDB) and opens like any other. In the Explorer each one carries an Offline pill, so you always know which knowledgebases live only in this browser. Hover or focus the pill to read that clearing this browser's site data deletes the knowledgebase. The rest of the Explorer lists only knowledgebases on the server, so Offline, a space of its own in the Explorer sidebar's Spaces group, is where you find them all.

A knowledgebase kept Offline is not synced and not backed up. It lives only in this browser: clearing your site data, or the browser reclaiming storage, will delete it. Keep anything important on the server, or export a copy.

What's Different

A knowledgebase kept Offline is a normal knowledgebase: every editor feature works, including tabs, themes, undo/redo, and export. Only the features that need the server are unavailable, because there's no server copy to power them:

  • Sharing needs a knowledgebase on the server. Opening Share on a knowledgebase kept Offline tells you so and offers Sync Knowledgebase: press it and the knowledgebase uploads, and the Share options appear in the same dialog, with no reload. Embeds are unavailable until it is synced, for the same reason.
  • Live collaboration and teams don't apply; a knowledgebase kept Offline is yours alone. Comments still work, but only you see them.
  • Images you add are stored inside the knowledgebase, so it stays fully local.
  • Add a Tab to Another Knowledgebase is unavailable for a knowledgebase kept Offline in either direction, and Duplicate makes another copy kept Offline rather than uploading one.
  • It is listed under Offline in the Explorer sidebar's Spaces, in Home's Recent once you have opened it, and on the Offline page (/offline, also reached from the Explorer panel), not in My Work, Recent or search, because those list what is on the server.

Offline Folders

New Folder on the Offline page, or the ⋯ menu on its row in the sidebar, makes a folder that lives in this browser too, and folders can hold folders, as in My Work. Move to Folder on a knowledgebase's menu, or a drag onto a folder, files it. A folder's menu has Rename, New Subfolder, Move Folder and Delete Folder; deleting a folder never deletes what is in it, which moves up a level. The folders are kept in this browser alone, like the knowledgebases in them.

Archiving an offline knowledgebase

Move to Archived works on a knowledgebase kept Offline too. It never leaves this browser: it moves out of the Offline list into Archived, and it won't open until you move it out. Opening it shows a Knowledgebase Archived card with Change Folder, which puts it back Offline (or, when you are signed in, moves it into your account). Clearing this browser's data removes it like any other knowledgebase kept here.

Moving to Your Account

You can change your mind at any time, from the knowledgebase's ⋯ menu.

  • When you sign in with knowledgebases kept Offline, we offer to move them to your account. Every one is ticked; untick any you want to keep in this browser, then Move. Not Now leaves them where they are, and we only ask again when there are more.
  • Sync Knowledgebase (in a knowledgebase's Share dialog, signed in or not, and on each knowledgebase under Offline, in the Explorer and on the Offline page, when you're signed in) uploads a knowledgebase kept Offline to the cloud. From the Explorer, the Offline page opens and asks you to confirm. It becomes a normal knowledgebase, shareable and (when you're signed in) reachable from your other devices, and the copy in this browser is removed.
  • A knowledgebase in a folder keeps its place. Sync Knowledgebase offers the My Work folder with the same name (or My Work itself when there is none) and says where it will go. The folder in this browser stays, empty, until you delete it.
  • Take Offline (on a knowledgebase's menu in the Explorer and the Explorer panel) does the reverse: it downloads a cloud knowledgebase into this browser and then removes it from your account and every other device. Because that deletes the server copy for good, we ask you to confirm first.
  • A tab it shares with other knowledgebases (see Add a Tab to Another Knowledgebase) stays in those knowledgebases, and this browser keeps its own copy. From then on the two are separate: edits on one side no longer reach the other, and syncing the knowledgebase back brings your copy in as a new tab beside the original.

Take Offline is deliberate and irreversible on the server side: once a knowledgebase is Offline it exists only in the browser you took it offline in. If it was shared, taking it offline also revokes the share links, and a team knowledgebase leaves the team library. For the owner it is a move, not a delete, so it skips the Trash; a teammate taking a team knowledgebase offline sends the team's copy to the team Trash.

How this works in 5 other apps

Was this article helpful?

Still need help?

Try Troubleshooting, or tell us what you were trying to do.

Contact us