Which note apps on a Boox keep writing after you turn Wi-Fi off?
Caleb Whitmore
October 7, 2026
Boox Notes and NeoReader keep writing after you turn Wi-Fi off. So does KOReader, and so does Obsidian when the vault is a folder already on the tablet. Notion, Evernote, Google Keep, and a OneNote notebook you never marked for offline use do not. They open a cache, fail the new page, or sit on a spinner. The split is whether the note is a file on the device or a record that lives on someone else’s server.
Turning Wi-Fi off is the test, not a setting inside the app. Force-stop the app, reopen it, make a new page, reboot the Boox, and see if the page is still there. An app that only looked fine because it still had a session is not an offline note app.
Which apps are actually local?
Notes, the one Onyx ships, stores notebooks on the tablet. Handwriting, layers, and the on-device recognition I use all run with the radio off. I have filled a meeting notebook on a Go 10.3 and a Note Air in airplane mode, rebooted, and the pages were there. That is the app to trust if the Boox is your notebook.
NeoReader is the same kind of local for PDFs and EPUBs already copied on. Margin notes and highlights stick to the file. It will not download a new book, and it should not. If the file was opened from a cloud folder that is only a placeholder, NeoReader will fail the same way any app fails a missing file. Copy the PDF into storage first. Then Wi-Fi can go off.
KOReader keeps highlights and notes on sideloaded files because it treats the folder as the library. It does not need an Onyx account or a store. It is the right second reader if NeoReader is fighting you, and it does not become more online just because the Boox is Android.

What does Obsidian do when the radio is gone?
It keeps editing the markdown that is already in the vault on the tablet. A new note in that folder is a new file. It survives reboot. What stops is sync: Obsidian Sync, Remotely Save, a Git plugin, Syncthing. The phone and the laptop will not see the note until the radio returns, and if you also typed in the same file on the laptop, you get a conflict, not a merge you can do with a pen.
Plugins are the trap. A lot of them fetch on open. With Wi-Fi off they error, delay the note, or blank a pane. The core editor does not need them. If you use Obsidian on a Boox as a capture surface, disable the plugins that phone home before you depend on the offline case. A vault that will not open until a plugin reaches a server is not a local vault. It is a website with a markdown costume.
Handwriting into Obsidian on a Boox is a separate disappointment. The Android client is a text editor on a slow screen. It keeps your typing without Wi-Fi. It is a bad place for the pen. Put the pen in Notes. Put the text in the vault when you are back, or accept that you are typing.
Which famous note apps only pretend?
Notion needs the network for the database you think of as your notebook. A page you recently opened may still paint. Creating the note you actually need, in a database, with the properties you use, usually spins. Do not take a Boox to a meeting planning to capture in Notion unless you have already proven that exact page works in airplane mode. Most people have not. They proved it on office Wi-Fi.
Evernote only writes inside notebooks you explicitly downloaded for offline, and only after that download finished. The default is not that. Google Keep will sometimes queue a sticky and sometimes lose the one you thought you saved. I do not trust either for the only copy of a meeting.
OneNote on Android is the messy middle. A notebook you opened recently can take ink offline, and it can also refuse a new section, duplicate a page when sync returns, or show you yesterday. If OneNote is the system of record, the Boox is a bad only-device for a Wi-Fi-off day. If you insist, open the exact notebook on Wi-Fi, confirm it is available offline in the app’s own setting, then test with the radio off before the day matters.
Kindle, Drive, and Dropbox are not note apps, and people still write in them. A Kindle book that finished downloading can be read and lightly annotated for a while without Wi-Fi. A Doc you started in Drive may be a cloud pointer. Annotations you care about belong in Notes or in a PDF that is a real file, then exported. The cloud app can be the transport later.

What still breaks inside the apps that work?
Handwriting search and recognition in Notes are on-device on the Boox models I use, so they keep working. A feature that shows a sign-in wall is not. Close it. Do not turn Wi-Fi back on to dismiss a badge and then forget the radio up. That is how a writing app becomes a sync client again.
Storage location matters more than the icon. A notebook saved on the device works. The same app pointed at a WebDAV or a Drive folder that is not fully downloaded does not. “Works with cloud” in the app’s feature list is a warning, not a comfort, for this test. Local folder, then off.
A Boox will also kill background apps to save the panel. An offline queue inside Evernote or Keep dies if the process is killed before it can flush, and with Wi-Fi off it cannot flush later. Notes does not need that queue. Prefer the app that has already written the file over the app that promises to sync when it can.
What about handwriting apps from the Play Store?
Squid, Noteshelf, and the other pen notebooks people install from Play keep writing only when their notebook file is on the device and the app does not demand a login to open it. That is true of some of them and false of the ones that “sync your whole library” as the primary save. Install Play only if you already decided you need that app. Then run the same airplane test before you uninstall Notes in a fit of optimism. A store app that writes locally is a fine second notebook. A store app that writes to an account is another Notion.
Play itself does not have to stay signed in for Notes to work. Enabling Play to try one app, then leaving Play services awake, is how the radio-off test passes and the battery test fails. Freeze Play after you know which apps you kept. The writing does not need the store process.
A keyboard case does not change which app is local. Bluetooth can stay off while you write with the EMR pen. If you are typing into Obsidian you may want the keyboard, and that radio is unrelated to Wi-Fi. Turn Bluetooth on for the hour you type, then off. Do not leave both radios up because the keyboard was useful once.
Who should stop hunting for a cloud app that works offline?
Stop if the meeting is today. The cloud app will not become local because you toggled a switch in a hallway. Write in Notes. Export the page to PDF when you are back on a network, and put that PDF where the cloud notebook expected a capture. That is clumsier than a native Notion page and it is a page you actually have.
Keep hunting only if offline is a rare edge and the system of record is the cloud for good reasons, a team that already lives there. Then the Boox is a bad primary capture device for the days the network is gone, and you should carry the pen app anyway as the fallback you have tested. Two apps is honest. One untested cloud app is how the meeting becomes a blank spinner.
A reboot test, not a vibe
- Turn Wi-Fi off in the shade. Forget the network if the tablet rejoins on its own.
- Open Notes. Make a page with a mark you will recognize. Force-stop Notes. Reopen. The mark should be there.
- Reboot. Open the same notebook before you turn Wi-Fi on. If it asks you to sign in before the pen works, that notebook was not local.
- Do the same for Obsidian only if the vault folder is on the tablet. Make a markdown note, reboot, find the file in the folder with a laptop over USB if you want to be sure.
- Anything that spun, logged you out, or showed a cached page you could not add to has failed. Do not bring that app.
The note apps on a Boox that keep writing with Wi-Fi off are Notes, NeoReader for files already stored, KOReader, and Obsidian against a local vault. The famous cloud notebooks keep a cache and a promise. Use them when the radio is on. When it is off, write in the app that already put the page on the device.