Workspace Storage Insights
See where disk space goes in your VS Code workspace. A Storage Explorer Usage sidebar shows folders and files by size, with your own file icon theme, and a theme-native dashboard adds a WinDirStat-style storage map, search, filters, and scan comparisons. Everything runs locally.

Features
- A tree of folders and files, sorted by size, with a proportion bar on every row.
- Icons and colors follow your active File Icon Theme (Material Icon Theme, Seti, vscode-icons, and others), including light and high-contrast variants.
- Sticky scroll: expanded parent folders stay pinned at the top while you scroll.
- A floating card at the bottom shows the total size, file and folder counts, and when the workspace was scanned.
- Refresh and Open Dashboard buttons in the view title bar.
- Click a file to open it, or use the hover action to reveal an item in the Explorer. Keyboard navigation works too (↑ ↓ → ← Home End Enter).
- Reuses the most recent scan, and shows a "Files changed — Refresh" hint instead of rescanning automatically.
Storage dashboard
- A nested, WinDirStat-style squarified storage map with folder drill-down and breadcrumbs.
- Path search plus size (≥1 MB / ≥10 MB / ≥100 MB), file-type, and modification-date filters.
- A sortable, virtualized file table with compact relative dates.
- A file-extension breakdown grouped by category (code, docs, config, media, binary).
- Comparison with the previous completed scan: total change and the largest file changes.
- Explicit diagnostics for unreadable or skipped items.
- Export of the current scan as Markdown or JSON.
- Follows VS Code light, dark, and high-contrast themes.
The extension never deletes files or runs cleanup commands.
Usage
- Open a folder or workspace.
- Select the Storage Explorer Usage icon in the Activity Bar to browse sizes in the sidebar.
- Select Open Dashboard in the view title bar, click the storage item in the status bar, or run Workspace Disk Usage: Open Storage Dashboard from the Command Palette.
- In the dashboard, click folders in the storage map to drill in, use the breadcrumbs to go back up, or search and filter the file table.
- Rescan later to compare against the locally stored previous scan.
Commands
| Command |
Description |
Workspace Disk Usage: Open Storage Dashboard |
Opens the dashboard (or reveals it if it's already open). |
Workspace Disk Usage: Refresh Storage Status |
Rescans and updates the status bar item. |
Workspace Disk Usage: Refresh |
Forces a rescan in the Storage Explorer Usage sidebar. |
Workspace Disk Usage: Open Dashboard |
Opens the dashboard from the sidebar. |
Configuration
Configure these settings under Workspace Disk Usage:
| Setting |
Default |
Purpose |
workspaceDiskUsage.excludes |
Common build and IDE folders |
Exact folder or file names skipped during scanning |
workspaceDiskUsage.excludePatterns |
[] |
Glob patterns such as **/*.log or **/temp/** |
workspaceDiskUsage.useProjectConfig |
true |
Merge exclusions from a workspace-root .diskusage JSON file |
workspaceDiskUsage.topFilesLimit |
50 |
Number of largest files included in exports and summary data |
workspaceDiskUsage.maxFileSizeMB |
0 |
Skip indexing files larger than this many MB (their size still counts in totals); 0 means no limit |
workspaceDiskUsage.scanConcurrency |
16 |
Maximum concurrent directory reads and file stats during a scan (1–32) |
workspaceDiskUsage.largeFileThresholdMB |
50 |
Highlight files at or above this size in the dashboard |
workspaceDiskUsage.dominantExtensionThresholdPercent |
40 |
Highlight extensions that take at least this share of the workspace |
workspaceDiskUsage.autoScanOnStartup |
true |
Scan after startup and show the total in the status bar |
Example .diskusage file:
{
"excludes": ["vendor"],
"excludePatterns": ["**/*.map", "**/fixtures/generated/**"]
}
Scan and comparison behavior
Unreadable items are skipped and reported as diagnostics; accessible items are still shown as a partial result. A cancelled or failed scan never replaces the comparison baseline. The first completed scan creates the baseline, and the next completed scan shows the changes.
Only one compact baseline is kept, in VS Code's extension-managed local storage. File metadata is never sent to an external service.
npm test compiles the extension and runs the unit and contract tests. npm run package builds a .vsix.
License
MIT — see LICENSE. File-type glyphs in the webviews use Codicons (CC BY 4.0).