Where Does Akiflow Store Local Data?
Akiflow caches tasks and calendars in an Electron data folder per OS, with an IndexedDB leveldb holding the offline copy.
Last updated
Akiflow is an Electron app, so its local state follows the per-OS app-data convention: an Akiflow folder with Cache, IndexedDB, Local Storage, and settings. The IndexedDB leveldb file holds the offline copy of tasks that third-party exporters read.
Real data lives in your connected calendars and task tools. The local folder is a cache, which makes it safe to delete for troubleshooting but useless as a migration path. Sign in on the new machine and let sync refill it.
Where Akiflow stores this, by platform
%APPDATA%\Akiflow
Electron cache plus IndexedDB leveldb with the offline task copy. A Local sibling folder also exists; remove both for a full reset. Tasks resync from connected accounts.
~/Library/Application Support/Akiflow
Same IndexedDB cache layout. Also clear ~/Library/Preferences/Akiflow and %LOCALAPPDATA%-style Local folder equivalents for a truly clean reinstall.
~/.config/Akiflow
Same interior as the other platforms. Export tools read the IndexedDB leveldb here when the UI offers no export of its own.
Frequently asked questions
How do I cleanly reinstall Akiflow?
Quit Akiflow fully, then delete the data folder for your OS (plus Preferences entry on Mac). Reinstall and sign in; calendars and tasks resync from connected accounts.
How do I export Akiflow tasks without an export button?
Point the exporter at the IndexedDB leveldb path for your OS. It reads the local cache directly, which covers tasks when no native export exists.
Notice an outdated path? Let us know.