The easiest open source app you will ever use to detect huge files. Built with Rust + React (Tauri).
Squirreldisk is an open source alternative to softwares like: WinDirStat, WizTree, TreeSize and DaisyDisk.
Some features:
- Fast scan and deep directory scanning
- Disk scanning or pick a directory
- External disks real-time detection
- A sunburst chart to quickly visualize the disk usage
- Drag and drop: collect all items to be deleted
- Right click on a folder/file to open the file explorer
- Cross-Platform MacOS, Windows, Linux
- No telemetry, no analytics, no network connections — fully offline
SquirrelDisk is currently built from source. The steps below cover the requirements and build commands for each supported OS.
Clone the repository first:
git clone https://github.com/adileo/squirreldisk.git
cd squirreldiskNative support for both Apple Silicon and Intel Macs.
npm install
# Start the app in development mode
npm run tauri dev
# Build for the current architecture
npm run tauri build
# Build for a specific architecture
npm run tauri build -- --target aarch64-apple-darwin # Apple Silicon
npm run tauri build -- --target x86_64-apple-darwin # Intelsudo apt-get install -y libgtk-3-dev libwebkit2gtk-4.0-dev libayatana-appindicator3-dev librsvg2-dev
npm install
npm run tauri dev
npm run tauri buildInstall Visual Studio Build Tools with the Desktop development with C++ workload before building.
npm install
npm run tauri dev
npm run tauri build- App: 0.3.4
- Tauri: 1.2
- PDU (macOS): 0.21.1 — native ARM64 + x86_64 builds
- PDU (Windows/Linux): 0.8.4
This app was a project from 2 years ago built in Electron in 2 days, I decided to port it to Tauri to achieve better performances and to make it Open Source. Yay.
The code is still spaghetti and needs a lot of refactoring.
If you find any bugs, please report it by submitting an issue on our issue page with a detailed explanation. Giving some screenshots would also be very helpful.
You can also submit a feature request on our issue page or discussions and we will try to implement it as soon as possible.
