docs/wiki/2.01-Downloads and Install.md
| Platform | x64 | arm64 | x86 |
|---|---|---|---|
| Windows | |||
| Linux / Android | |||
| — | |||
| macOS | — |
<!-- prettier-ignore -->[!CAUTION]
The suggested commands and hyperlinked repos below are provided as a convenience.
Never run commands or open links you are not familiar with!
| Repo/Install Link | Suggested Install Command |
|---|---|
flatpak install flathub com.super_productivity.SuperProductivity | |
snap install superproductivity | |
Various Methods (eg. yay/paru, makepkg -si, or Chaotic AUR) | |
| N/A | |
| N/A | |
brew install --cask superproductivity | |
| N/A | |
| N/A | |
winget install -e --id JohannesMillan.superProductivity | |
choco install super-productivity --pre | |
scoop bucket add extras; scoop install extras/super-productivity |
If you encounter problems with the AppImage on Ubuntu, see this issue comment.
To use local file sync, you need to manually connect the home interface: snap connect superproductivity:home
Data Persistence Warning
When uninstalling the snap package, all user data (tasks, projects, settings) stored in ~/snap/superproductivity/common/ may be removed. Always export your data before uninstalling. Consider the AppImage or .deb package if you prefer data in the standard ~/.config/ location, or Flatpak, which keeps data in ~/.var/app/ and leaves it in place on uninstall unless you pass --delete-data.
For more details, see issue #6031.
Flatpak is a fully supported package, equal to the others listed above — install it from Flathub.
To sync to or back up into a folder outside the sandbox, grant filesystem access with Flatseal or flatpak override. Without it the app reports a permission error. Paths inside ~/.var/app/com.super_productivity.SuperProductivity/ need no extra permission.
Data lives in the sandbox rather than ~/.config/, so another install of a different package format will not see it — see [[3.06-User-Data]]. Update with flatpak update com.super_productivity.SuperProductivity (no sudo).
The Snap build automatically uses Electron's X11 rendering backend in Wayland sessions to avoid known Mesa/EGL startup failures. For another Linux package, if the window is blank or the GPU process repeatedly fails to start, try:
superproductivity --ozone-platform=x11
This changes the Chromium rendering backend; it does not enable any additional idle-detection feature and may give up Wayland-native behavior such as fractional scaling or native input-method support.
A DMG containing both the x86_64 and arm64 files is also available.
Due to certification issues, the Microsoft Store is recommended.
At the time of writing, the "chocolatey" build is failing and forcing the use of "pre-releases" is necessary.