You open the app on a train, on a flight, in a client's basement meeting room with one bar of signal, and the board that was there this morning is a spinner, or a blank page, or a login screen asking you to reconnect. Nothing about your images changed. What changed is that the thing you were looking at was never actually on the device in your hand — it was a window onto a server, and the window just lost its view.
That is worth saying plainly before anything else, because it reframes the question. "Why doesn't my moodboard app work offline" sounds like a bug report. It is closer to a design decision you agreed to the day you made an account, and the honest fix depends on which half of that decision is actually the problem for you.
The symptom, stated the way you'd search it
A board that opened fine an hour ago now shows a spinner that never resolves, or a message asking you to sign back in, or — on some hosted tools — nothing at all, just a blank rectangle where the images used to be. Turning wifi back on fixes it instantly and completely, which is itself a clue: nothing was corrupted, nothing was lost, the board was simply somewhere else the whole time and the connection was the only road to it.
The cause: a board that lives on someone else's server
Milanote's own help center is direct about this for its mobile apps. Asked whether the Milanote mobile apps work offline, the answer is: "Not yet. You'll need an internet connection to view and edit boards." That single sentence explains most of the frustration in one line — the board was never stored on your phone in a form the app could read without asking the server first.
Notion's own documentation on working offline is more generous but still bounded. Offline mode exists on the desktop and mobile apps — "this feature isn't available on web browsers" — and it works by you marking a specific page "Available offline" before you lose the connection. Even then, a database only takes the first 50 rows of its first view with it automatically; anything past that needs downloading one row at a time, in advance, on purpose. A moodboard built as a gallery view over a growing database of reference images is exactly the shape that outgrows that limit first, usually without anyone noticing until the day it matters.
Neither of these is a flaw exactly. A board that several people edit at once, with comments and live cursors and a version history, has to live somewhere all of those people can reach it, and that somewhere is a server. The convenience you get in exchange — open the same board from your phone, your laptop, and a teammate's desk, all seeing the same thing — is real, and it is also the reason offline access is the part that gets built second, if it gets built at all. Hosted tools generally treat a connection as the default state and offline as the exception they patch in afterward. That is a reasonable order of operations for a product built around real-time collaboration. It is a bad fit for a reference board nobody else has ever opened.
The fix that costs nothing: use the setting you already have
Before reaching for a different app, it is worth checking whether the one you
have already solves this, because sometimes it does. If a moodboard lives on a
Notion page, open it, tap the ••• menu, and toggle "Available offline" while
you still have a connection. That single page — images, gallery cards, and
whatever is inside the first fifty rows of its underlying database — comes
along the next time you lose signal. It is not automatic and it does not cover
everything past that row count, so a database that has grown past fifty
reference images needs the extras downloaded individually ahead of time, which
in practice means doing it the day before the flight, not at the gate.
Milanote's help center documents no equivalent toggle for its mobile apps, so there is no setting to flip there — the honest answer for a Milanote board on a phone is that the "Not yet" in its own FAQ is current, checked the day this page was written, and worth testing against your own account rather than assumed to have quietly changed. If you specifically need Milanote's desktop app to keep working through a dropped connection mid-session, that is worth testing on your own machine before a trip depends on it — the mobile answer is explicit; the desktop one, absent a documented answer, is something to verify yourself rather than take on faith either way.
For the Notion route specifically, the order of operations matters more than it looks. Toggling "Available offline" on a page after the connection is already gone does nothing — the download has to finish while you still have signal, which in practice means doing it the night before a flight rather than at the gate once you notice the spinner. And because only the first fifty rows of a database's first view come along automatically, a moodboard built as a gallery over a database that has grown past that count needs the overflow rows opened and downloaded individually, one at a time, while you still have a connection to do it with. That is tedious enough that most people only discover the fifty-row ceiling exists the first time they hit it in the field, which is exactly the wrong moment to learn about it.
When the fix is actually a different tool
The setting above helps for the boards you remember to prepare. It does nothing for the ones you forgot, and it does nothing at all if what you actually want is to stop thinking about connectivity before every trip. That is a different problem from the one Notion's toggle solves, and it is worth being honest about which one you actually have before switching anything.
If a board is genuinely collaborative — other people are editing it, commenting on it, opening it from their own accounts — moving it off a hosted service gives up the reason it was hosted in the first place, and no local app, including ours, replaces that. Best free alternatives to subscription moodboard tools covers the wider field if collaboration is still the point and price is the only complaint.
If a board is a private, personal reference collection — the kind of thing one
person builds and nobody else opens — the calculation is different. Coii Ref
indexes the folders of images already on your Mac and reads a saved canvas as a
plain .coii-canvas file, the same way it reads any other file: no request
goes anywhere to check whether the file is allowed to open. That is what
local-first software means as a category,
not a marketing word — the file is the thing, not a reference to a thing kept
somewhere else. The full comparison against Milanote
goes through what you would give up making that trade, and it is a real list:
no sharing link, no comments, no editing from a phone, no real-time anything.
Coii Ref vs Notion's gallery views is the
equivalent comparison if your board today is a Notion database wearing card
covers rather than a Milanote canvas.
What actually changes once the images are local
The honest version of "switching fixes this" is narrower than it sounds. What moves is where the pixels and the metadata live: on your drive, inside a folder Finder already shows you, rather than behind an account on a server somewhere. A saved search — the same query you'd run to pull up a shoot, a client's folder, or everything rated four stars and not yet flagged — reads an index that lives beside the files, so there is nothing to sync and nothing to mark "available offline" in advance, because it never was anywhere else.
What does not change is the rest of the job a hosted board was doing. If part of why you liked having a board in Notion or Milanote was that a client could open the same link from their own laptop, that stops working the day the board becomes a file only your Mac can open. This is not a reason to avoid the switch, but it is a reason to be specific about which boards actually need moving. A personal shot-reference collection and a client-facing pitch deck are not the same object, even when they look almost identical inside the same app, and treating them differently is usually the right call rather than an all-or-nothing migration.
How to tell which kind of board you actually have
Ask who has opened it in the last month besides you. If the answer is nobody, the hosting was buying you nothing you were using, and the connection requirement was pure cost. If the answer is a client, a collaborator, or a teammate, the board is doing real collaborative work, and the fix here is the free one — Notion's per-page toggle, tested and refreshed before every trip — rather than a switch that would quietly break the sharing that was the whole point.
It is also worth checking whether the frustration is really about connectivity at all, or about something adjacent to it. A reference app that starts struggling once a library gets large can look like a connection problem — slow loads, spinners that never resolve — when the actual cause is scale rather than signal. And a board that references files on an external drive that isn't plugged in will show the same kind of broken-looking gap as a lost connection, for a completely different reason. Both are worth ruling out before deciding the fix is switching tools at all.
A quick way to tell the two apart: turn on airplane mode deliberately, at your desk, with the drive that holds your images still connected, and open the board on purpose. If it fails the same way it did on the train, connectivity really was the cause. If it fails differently, or not at all, the earlier incident was something else — a slow disk, a library that had quietly grown past what the app was tested against, a drive that unmounted itself — and switching to an offline-first tool would not have fixed that version of the problem anyway. Diagnosing which one you actually have costs five minutes and saves you from solving the wrong thing twice.
The version of this that actually holds up over years is boring: keep the boards other people need to open where those people can reach them, and keep the boards that are really just yours somewhere that does not ask permission to open. The 30-day trial is the cheapest way to find out which category most of what you have actually falls into — no card, no account, and nothing to toggle before you leave the house.