Super Productivity
Super Productivity is an open-source task and time-management workspace for desktop, web and mobile with projects, subtasks, time boxing, work logs, planning views, Pomodoro cycles and service integrations.
What Super Productivity provides
Super Productivity keeps projects, subtasks, estimates, time boxes, work logs, planning views and reminders in a local-first workspace. Calendar, issue-tracker and synchronization features are optional and have their own permissions, data flows and conflict behavior.
Build the workflow in layers
Start offline with a test project, export a backup and measure how tasks and work logs are recorded. Add only one synchronization backend, then one external integration with a minimal token. Local editing should not be assumed to write back to every connected service.
Maintenance note
This page reviews Super Productivity for task planning, work-log conventions, sync backends and integration boundaries. Content review date: 2026-08-23.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave Super Productivity to this cloud drive
Baidu Netdisk
Save Super Productivity to this cloud drive
Super Productivity project and sync guide
Build a small offline project first, test tasks, time boxes and logs, export a backup and then connect one sync backend or service at a time with a test account.
Before you start
- Confirm the desktop, web or mobile build and their feature differences.
- Prepare a test project without sensitive client data and define the work-log convention.
- If connecting services, prepare minimal-permission tokens and an independent backup location.
Installation steps
- 01
Install the matching platform build
Install Super Productivity for the platform, confirm the version and local data location and keep the first project offline while learning the workflow.
- 02
Create projects and time boxes
Add a few projects and subtasks with estimates, tags, planned times and due dates, then test pause, idle and cross-day work-log behavior.
- 03
Configure reminders and planning views
Set work and break reminders, arrange time blocks and distinguish imported calendar items from local tasks to avoid counting repeated events twice.
Quick start
- 01
Export a complete local backup
Export application data before connecting any external service, record the version and timestamp and confirm that the backup can be read from an independent location.
- 02
Connect one sync backend
Choose one supported sync method, test create, edit and delete on two devices and inspect snapshots, encryption keys and conflict recovery before using primary data.
- 03
Add a minimal-permission integration
Connect one issue tracker or calendar with a test project, verify which fields are imported, written back or used only for time tracking and keep the token scope narrow.
Usage tips
- Work logs are user-entered records and should not be treated as automatic billing, attendance or performance evidence.
- Multiple sync backends should not control the same dataset until their conflict behavior has been demonstrated.
- Keep recovery keys and exports separate from the live workspace and service credentials.
Troubleshooting and uninstall
Why are old tasks or duplicate time blocks appearing after sync?
Pause other devices, preserve the export and service snapshot, confirm the single backend, clock and encryption key and compare versions in a copy before merging.
Why did an imported issue not update the remote service?
Check the integration's direction, supported fields and token permissions; some integrations pull titles or schedules only and do not write local edits back.
- Export data and recovery materialsExport projects, logs and settings, record connected services and preserve encryption keys or sync recovery data in a separate location.
- Disconnect and remove the appRevoke unused integration tokens, stop synchronization, sign out where applicable and uninstall through the platform after confirming the export is usable.
Frequently asked questions
Does Super Productivity require an account?
Local use can work without an account; synchronization, calendar and service integrations are optional and have separate data and permission implications.
Should two sync backends be enabled together?
Usually start with one. Multiple writers make conflict ownership harder to understand, so test one backend and a recoverable backup before adding another.
Are work logs automatic activity tracking?
No. They reflect the user's configured start, pause and classification actions and do not automatically prove billable, approved or productive time.
Does the download require an extraction code?
The Quark entry does not require one; the four-character code for the Baidu entry is shown beside its download entry.