WidgetStore - Widgets, animated icons, dashboards and personal pages for Notion

Desktop disk usage: inspect WidgetStore storage

Check disk capacity and inspect WidgetStore widget pages, icon cache, app index and startup logs locally. Learn what is excluded and why sizes are estimates.

Capacity and app storage

Open System monitor from the desktop sidebar. Disks continues to show each volume's capacity, available space and read/write rates.

Under WidgetStore disk usage, click Analyze app storage to read file metadata on this computer. File contents are not read, results are not uploaded, and personal file lists are not displayed. Click Stop to cancel; interrupted results are clearly marked as incomplete. Use Scan again for a fresh snapshot.

The usage breakdown is read-only. A separate Regenerable cache panel requires a preview, individual file selections and a native confirmation. The former recursive HOME/volume scan is disabled because it lacked per-folder consent and protected-data exclusions; volume capacity remains available. Development did not clean any real user data.

Included categories

On macOS and Linux, only specified regular files in these app-owned locations are measured. Subfolders, symbolic links and hard links are excluded:

  • Offline widget pages: local HTML copies, replaced after a successful fetch and retained for offline access.
  • App icon cache: extracted installed-app icons and failed-extraction markers, regenerated when missing.
  • App index: the local installed-app index, refreshed by app discovery.
  • Startup logs (including previous): startup and crash logs, with a previous copy retained during rotation. Agent terminal replay and conversation logs are excluded.

Folder not present and Not measured are distinct. Permission failures never become a zero-byte measurement. Category analysis is not yet supported on Windows; volume capacity still works.

Reading the numbers

Measured scope is the sum of readable included files. It is neither the total app footprint nor reclaimable space. Filesystem blocks, compression, shared blocks and active writes affect estimates. Removing a file would not necessarily free its displayed size.

The scan has a budget of 50,000 directory entries and 10 seconds, with stop checks between entries. A blocked filesystem call can delay stopping. Budget limits or cancellation produce an explicit incomplete result. Results remain in app memory until restart; old persisted scan results are no longer loaded.

Exclusions and limits

Model data, workspaces and Git worktrees, Agent conversations/run records/attachments/review evidence, mail, reader, notes, credentials, browser data, downloads, personal files, other apps and system files are not scanned. This version cannot identify every source of WidgetStore disk usage. A small measured subtotal says nothing about excluded data.

Selected-folder large-file scanning, duplicate detection and app uninstall are not provided. Cleanup covers only the regenerable caches listed below, rather than the entire disk or all app data.

See the desktop guide and Agent workspace and attachment guide. Existing storage actions in Settings are a separate feature from this read-only analysis.

Regenerable cache: preview, hold, restore and remove

Under Regenerable cache, choose categories and click Preview candidate files. Categories and files start unselected. Candidates are app-generated offline widget HTML, app icons and the app index: regular single-link files, unchanged for at least 7 days and not currently participating in app cache I/O. Startup logs are not regenerable and are excluded. Unknown names, links, special files, files owned by other users and oversized files are excluded.

The preview shows file names, logical lengths, allocated-block estimates and modification times. Usage rows separately count excluded hard links. Each list is limited to 200 entries and 128 MiB of logical lengths, and expires after five minutes. Changed or expired entries require a fresh preview.

Select files individually and choose Request confirmation to move to holding. A native dialog explains regeneration costs. After consent, the backend checks each file and its containing directory again. Active, changed or unverifiable files are kept and failures are reported. Offline widget pages need a network connection to fetch again; icons and the app index rebuild on demand.

Holding storage still uses disk space. Moving files there does not free capacity. It is a dedicated directory inside the app cache, with no automatic expiry deletion. Use Refresh held files, select entries and choose Restore selected files. Restore also requires native confirmation, never overwrites a new cache file and keeps conflicting held files. Interrupted or conflicting entries are restore-only. At most 16 nonempty batches appear at once; a partial-list notice tells you to handle these and refresh for more.

Only verified held entries can be selected for Request confirmation to remove permanently, followed by a separate native confirmation. Permanent removal cannot be undone and does not use the system Trash. It checks file identity and state again, removes only exact held files and never recursively deletes directories. Estimated blocks removed may differ from the actual increase in available space; consult the volume reading above.

Stop stops subsequent entries after the current filesystem call returns. Completed moves remain recoverable; permanently removed files cannot be restored. Counts and expandable item results distinguish success, failure and stopping.

Windows category analysis and cleanup are not yet available. There is no website, MCP or Agent automatic-cleanup interface. Actual deletion tests used newly created isolated fixtures, never real app data.

Last updated: Nov 18, 2026