Where Does Super Productivity Store Tasks and Backups?
Where the Super Productivity task app keeps its Electron database, backups folder, and attachments.
Last updated
Super Productivity keeps its state in the standard Electron userData folder: %APPDATA%\super-productivity on Windows, with automatic JSON backups in a backup subfolder. Tasks, projects, tags, and metrics all live there.
The auto backup folder is the quiet hero: versioned JSON snapshots accumulate without asking, and restores import cleanly. Sync providers mirror the same state rather than replacing backups. Copy the whole folder with the app closed and nothing is lost. Integrations cache offline issues.
Where Super Productivity stores this, by platform
%APPDATA%\super-productivity
Main state plus backup/ JSON snapshots and assets/ attachments here. Paste the path into Explorer. Sync settings point at external targets; the local folder stays authoritative.
~/Library/Application Support/super-productivity
Same Electron layout under Application Support. Finder hides Library; use Go > Go to Folder. macOS sandboxing does not apply since the app ships outside the store.
~/.config/super-productivity
Honors $XDG_CONFIG_HOME, defaulting to ~/.config. The automatic backups accumulate here too, so prune old JSON when disk runs low. Portable builds keep the same tree beside the binary.
Frequently asked questions
how do i back up super productivity
Copy the Super Productivity userData folder to the same path on the new machine with the app closed (%APPDATA%\super-productivity on Windows). Tasks, projects, and settings travel together. Attachments in the assets folder need the same copy treatment.
does super productivity auto back up
Yes through automatic JSON backups in the backup/ folder beside the data (configurable count and interval). Copy those files off device periodically; on disk copies die with the disk. Restores import through Settings > Import.
how does super productivity sync work
Through WebDAV, Dropbox, or local file sync configured in Settings, which mirrors the same JSON state. Sync conflicts resolve newest wins, so avoid editing on two machines simultaneously. The sync target holds backups, not live state.
Notice an outdated path? Let us know.