Heptabase uses local storage for app data and offline access. This warning appears when the storage estimate reported by the app or browser shows less than 1 GiB (1,024 MiB) remaining in its storage quota.
It is not triggered by your computer’s drive having less than 10% free space. The app’s storage quota and your drive’s total free space are different measurements.
Check what's using the space
Open the Heptabase data folder and look at the size of the hepta-files subfolder, which holds your imported PDFs, images, and other attachments:
Windows: paste this path into File Explorer’s address bar:
%USERPROFILE%\AppData\Roaming\project-meta
macOS: in Finder, press Cmd+Shift+G and paste this path:
~/Library/Application Support/project-meta
The size of hepta-files shows how much space your desktop attachments use, but it does not tell you what triggered this warning. A folder larger than 1 GB is not, by itself, evidence of the cause. Check your drive’s available space as well; Heptabase’s database and the app or browser storage quota are separate from this attachment folder.
Free up space
Move attachments to another drive
If hepta-files is large, contact support. We can enable Change File Storage Location so you can move hepta-files to another local drive.
After it is enabled, restart the desktop app and go to Settings > Advanced.
This only moves imported PDFs, images, and other attachments; the Heptabase app installation and other local data stay on the original system drive. Do not choose a folder inside Google Drive, iCloud, Dropbox, or another cloud-synced location, because that can cause sync problems.
Free disk space safely
If your drive is low on free space, remove files you no longer need outside Heptabase. Do not manually delete Heptabase’s data folder or clear browser site data to dismiss the warning, as this can remove local or unsynced data. Contact support if the warning persists despite having free disk space.
Use the web app
The web app can reduce the need to keep desktop attachment copies, but it still uses browser storage for local data and caching. It is not a zero-storage workaround, and browser storage limits can still apply.
