Short answer: Offline is only useful when the app opens, your work is still there, and you can export it, so judge whiteboards on those three things rather than on a badge. Canvasola is built that way: a progressive web app that reopens without a connection, autosaves the document and workspace tabs locally, and exports to files you can carry away.

What offline has to mean to be useful

Offline is not a feature you switch on. It is a set of conditions, and a tool can satisfy one of them and fail the others. The useful definition is simple: the app opens, your work is exactly where you left it, and you can get the work out while the network is still down. The offline guide shows how to check that in Canvasola.

A tool that only satisfies the first condition is more annoying than one that fails honestly. An interface that loads from a cache and then quietly refuses to save your drawing gives you a blank canvas and a false sense of safety, which is the worst outcome on a train.

  • The app opens with no network at all
  • Work is stored on the machine, not waiting for a server
  • Exports still produce a real file
  • Nothing is lost when the tab closes

Three levels of offline support

Most tools that mention offline fall into one of three levels. Level one is the cached shell: the page opens, but a drawing you make is not stored and the tool asks for a connection to keep it. Level two stores your work locally, so you can draw, but the export or share action still needs the network.

Level three is the one that changes how you work. The app opens, the work is saved on the machine as you go, and every export produces a file you can email or archive. Canvasola is built for level three, so the difference between it and a cached whiteboard is not a matter of degree.

Level three still does not make a team tool of anything. There is no shared editing inside a document and nothing published for other people to open, so the offline story is about your own work.

  • Level one: the interface opens, the work does not save
  • Level two: work saves locally, exporting needs the network
  • Level three: opens, saves and exports with no connection
  • Canvasola is built for level three

The app shell problem

The shell is the part of an app that the browser caches: the code, the fonts, the icons and the layout. Caching it is straightforward, and it is why so many web apps open offline and then behave strangely. The hard part is the data, and that difference separates a real offline tool from a convincing demo.

Canvasola is a progressive web app, which means the whole shell is cached on first load and the app reopens offline afterwards. There is no install beyond opening it once, and no separate desktop build to keep updated. The install guide covers adding it to your home screen or taskbar.

  • Cached after the first load, and it reopens with the network off
  • One code base for a laptop, a tablet and a phone
  • No separate desktop build to install or update
  • The editor, the canvas and the mockup tools all work offline

Local saves and project files

The saving model matters more than the offline claim. Canvasola writes the current document into local storage as you work and keeps the list of workspace tabs separately, so a closed tab reopens with your work and your tabs in place. A version history panel holds twenty snapshots, and undo and redo is shared across the canvas, the map and the mockup editor.

Cloud sync is opt-in rather than automatic, which is a deliberate choice for a local-first tool. If you switch it on, the allowance is five projects of two megabytes each, and sessions last thirty days. The durable form of a project is a file: a .canv project with a CANV1 header holding the canvas elements, style, mind map, app mockup project and camera, reopened with Open Project.

  • The current document autosaves into local storage as you work
  • Workspace tabs are stored separately and restored on reopen
  • Cloud sync is opt-in, with 5 projects of 2 MB each
  • A .canv project file with a CANV1 header holds the whole project

Exporting without a connection

The export is the last test, and it is the one most often overlooked. From the canvas you can produce PNG, JPG, vector SVG, or use the print action, which opens the browser's own print dialog. From a mind map you get Markdown, OPML 2.0, a plain-text outline, SVG, or PNG, with the raster capped at 4096 pixels on the longest side.

The App Builder adds PNG of all frames at twice the size, JPG, JSON that can be imported back later, and static HTML and CSS built from absolutely positioned divs with inline styles, a small embedded stylesheet, no JavaScript and no interaction. There is no direct PDF export, so a document that has to be a PDF file goes through the print dialog.

  • Canvas: PNG, JPG, vector SVG, or the browser print action
  • Mind map: Markdown, OPML, plain-text outline, SVG and PNG
  • App Builder: PNG at 2 times, JPG, JSON and static HTML and CSS
  • No direct PDF export, only the print dialog in the browser

Which category you are in

Work out which job the tool has before you compare features. If the session is a group activity, a shared board is the right category and offline support is secondary. If the job is one person's thinking that has to survive a bad connection, a local-first workspace is the right category.

Canvasola is in the second group, and it is honest about the cost. There is no shared editing of one document, no comment threads, no page for other people to open, and no PDF export. The optional cloud account holds five projects of two megabytes each. The Miro comparison covers the group case from the other side.

  • Group sessions: a shared board, where offline support is secondary
  • Solo thinking offline: a local-first workspace with local saves
  • Deliverable-driven work: a tool whose exports match the format
  • Canvasola is built for the second and third cases

How to verify a tool before you fly

Ten minutes of testing tells you more than any badge on a product page, and it is worth doing on the device you will actually use rather than the one on your desk. Do the checks in order, because a tool that fails the first one will not pass a later one by accident.

The result is a plain answer for the trip you are planning, plus a short list of what the tool cannot do once the network is gone. Write that list down before you travel, not after.

  1. Load it once, then cut the network. Open the tool with a good connection, wait for it to settle, then turn the network off and reload the page. If it does not open, stop there.
  2. Check the work is really stored. Draw or map something, close the tab completely, reopen it and look for your work. A tool that only holds the shell will show you an empty surface.
  3. Export and open the file. Run an export while still offline, then open the result in another program. An export that needs the network is not an export you can rely on.

A checklist you can reuse

  • The app opened with the network switched off, not just cached
  • Work was still there after closing the tab completely
  • An export ran offline and the file opened elsewhere
  • You know whether the tool saves locally, to a server, or both
  • The project file format is one you can open later
  • You checked how the work reaches a second device
  • You accepted the limits of the category you are in

Common mistakes to avoid

  • Trusting the offline badge. A cached interface proves very little. Test opening the app with the network off and then check that your work is still there.
  • Leaving without an export. Work that only exists inside a tool is not finished. Export before you travel, and open the file to confirm it is real.
  • Assuming sync is automatic. In a local-first app, cloud sync is something you switch on. Know whether the copy on your laptop is the only copy.
  • Testing on the wrong device. A laptop with a saved install behaves differently from a phone that was never installed. Test where the work will actually happen.
  • Forgetting the file limit. Cloud storage is small by design, and local storage is not a backup. Keep a .canv project file somewhere safe.

Frequently asked questions

What is the best offline whiteboard for one person?

For a single person, look for a tool that stores the work on the machine and produces files you can carry away, and Canvasola is built that way. It is a progressive web app that reopens after the first load, autosaves the current document and the workspace tabs into local storage, and exports to PNG, JPG, SVG, Markdown, OPML, JSON and static HTML and CSS.

Does Canvasola work offline without an account?

Yes. No account is needed to start, and the app keeps working with the network off once it has been loaded. Cloud sync is optional, and turning it on gives five projects of two megabytes each with sessions lasting thirty days. The local copy of your work does not depend on that account existing.

Is an offline whiteboard still good for a team?

It depends on the meeting. Canvasola has no shared editing of the same document, no comment threads, and nothing published for other people to open, so a group working through one board together is better served by a collaborative tool. What it does well is the preparation and the follow-up work that usually happens on one machine.

How do I keep my work safe if the browser storage is cleared?

Save a project file. A .canv file with a CANV1 header holds the canvas elements, style, mind map, app mockup project, camera and layout mode, and Open Project brings it back. The <a href="/blog/back-up-your-canv-project">backup guide</a> covers where to keep those files and how to name them.

Open it once, then turn the network off.

Load Canvasola in your browser, draw something, and reopen the page with the network off. If the work is still there, you have your answer.

This guide is part of the comparisons collection. For the wider product tour, read the complete Canvasola guide, and keep the keyboard shortcut cheat sheet open while you work.