Ultra-fast, user-mode disk analyzer built with Rust and Tauri. Visualize space hogs with dynamic age scatter plots.
ProductivityGitHub @barun-sahaOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Repository information has not been collected yet.
No updates detected yet. GitHub releases will appear here.
GitHub star growth between the latest completed 8-hour observations
DeepSeek Harness Remote can securely connect a phone or another computer to the computer where you run DeepSeek Harness, so you can continue your work anytime and anywhere, check progress anytime, and continue working.
AI translation
Open-source, local-first task manager that works offline, syncs every device, runs on a Raspberry Pi, and requires no subscription.
AI translation
Open-source, self-hosted webmail built on JMAP. Email, calendar, contacts, and files in one interface for Stalwart Mail Server.
Open Source Office suite for users used to MS Office - multi-platform, tuned for performance
Insights and actions on your disk space usage
Taken from the repository README
Loading the full README.
Read the full README ↗Drive Sonar is a fast, lightweight desktop disk usage explorer and analyzer built with Tauri v2, Rust, React, and TypeScript.
Drive Sonar is inspired by the simplicity of ncdu. Drive Sonar offers different visualizations to help you gain a better idea of your disk usage.
Drive Sonar runs entirely in user mode—no admin mode or elevated privilege is required to scan even the most protected corners of your disk. It's also fully open source, so you can see exactly what it's doing and build it yourself if you'd rather not trust a binary.
| Metric | Drive Sonar | WinDirStat | WizTree |
|---|---|---|---|
| Version tested | 0.6.0 | 2.8.0 | 4.3.1 |
| License | Apache 2.0 | GPL v2 | Proprietary |
| Runs in user mode (no admin required) | ✅ | ✅ | ❌1 |
| Installed size [MB] | 5.7 | 7.1 | 20.0 |
| Peak memory usage (median)2 [MB] | 108.7 | 239.6 | 635.2 |
| Warm scan time (median)3 [s] | 3.3 | 9.1 | 6.5 |
| Cold scan time (single run)4 [s] | 10.6 | 22.9 | 17.2 |
Primarily, this started as a hands-on project to learn Rust and Tauri. But it's also grown into something I actually reach for: Windows' native storage view is fairly high-level, and I wanted something like ncdu, but with a GUI—fast and minimal, insightful without visual clutter, and one that doesn't demand admin rights just to tell me where my disk space went.
Pre-built binaries are available on the Releases page. Download the installer for your platform, run it, and you're good to go—no build step required.
Note: The Windows installer isn't code-signed yet, so you'll likely see a Windows SmartScreen warning ("Windows protected your PC") on first run. This is just because the binary doesn't carry a paid publisher certificate—it's not a sign of malware. Click More info → Run anyway to proceed. Signing is on the radar for a future release.
On Windows, Drive Sonar requires Windows 10 version 1709 (October 2017 Update) or later. macOS and Linux have no additional version requirement.
Install dependencies:
npm install
Run the application in development mode:
npm run tauri dev
Build the optimized desktop binary:
npm run tauri build
First, ensure all project dependencies (including test libraries) are installed:
npm install
Run frontend unit tests with Vitest:
npm test
To generate frontend code coverage reports:
npm run test:coverage
Run backend Rust unit tests:
cargo test --manifest-path src-tauri/Cargo.toml
To generate code coverage reports, install cargo-tarpaulin (if not already installed) and run:
cargo tarpaulin --manifest-path src-tauri/Cargo.toml --ignore-tests
To create a new release:
0.4.0 -> 0.5.0) in:
package.json ("version")src-tauri/tauri.conf.json ("version")src-tauri/Cargo.toml (version under [package])
Update package-lock.json with npm install --package-lock-only after changing package.json.main: Commit changes, raise a PR, and merge into main. Release Drafter uses the version in src-tauri/tauri.conf.json for the draft's name, tag, and changelog link.main, confirm the version files and draft agree, and push v<version> matching src-tauri/tauri.conf.json:
git checkout main
git pull origin main
git tag v0.5.0
git push origin v0.5.0
v* tag triggers the GitHub Actions workflow, which checks that the tag matches the Tauri version before building binaries across platforms and attaching them to the same draft release. Review the notes and binaries, then publish the draft.Find out more about Drive Sonar:
Drive Sonar is open-source software, released under the Apache 2.0 license.
Admin requirement: WizTree requires administrator privileges to read the NTFS Master File Table directly for its full-speed mode; without elevation it falls back to a slower standard directory scan. WinDirStat can be optionally run with admin privileges as well. ↩
Memory usage: Median of 3 independent runs, same scan location. ↩
Warm scan: Median of 5 independent runs of the same folder, each app already opened once beforehand (warm file-system cache) — the scenario most users encounter when re-scanning (e.g., after deleting files). Because all three tools benefit equally from the OS file-system cache under this condition, disk I/O latency is minimized for each of them alike — this measurement isolates each application's own processing efficiency (directory traversal, tree construction, size aggregation) rather than raw disk speed. ↩
Cold scan: Median of 3 independent runs per app, each following a full system restart. Disk activity was confirmed quiet via Resource Monitor before every run (queue length ~0, active time 1–3%, throughput under a few hundred KB/sec) to rule out background OS contention (updates, indexing, sync clients) as a confound. WizTree was run with administrator elevation (its intended mode, enabling direct MFT reads); WinDirStat and Drive Sonar were both run in standard user mode. WinDirStat does not report scan duration natively and was timed manually with a stopwatch. Item count varied slightly across runs (~1.2M items). Note: if background OS activity (updates, indexing, antivirus scans) is active during a scan, cold-scan times can spike well above these figures — we observed up to ~50s in earlier unconstrained trials — so results are only comparable when disk activity is confirmed idle beforehand. ↩