Is Neodisk Safe to Use on Your Files?
Updated
Yes, within the scope of what it does. Neodisk is described as read-only by design: it scans your disks and cloud drives to show where space went, and it never deletes your files. That makes it safe to point at any drive you want to analyze. The important caveat is that "safe" here means safe to scan — Neodisk is an analyzer, not a cleaner, so any actual deletion or modification happens in some other tool, under your control.
What "read-only by design" actually covers
The safety claim rests on a single design decision: the app reads file metadata and sizes, and does not write, move, or delete anything. According to the site, this is not a setting you toggle — it is how the tool is built.
That distinction matters because most disk-cleanup anxiety comes from tools that combine analysis with deletion. Neodisk separates those steps entirely:
| Concern | Neodisk's behavior |
|---|---|
| Deleting files during a scan | Does not happen — read-only by design |
| Modifying file contents | Not part of scanning |
| Cleaning up space for you | Not offered; you clean up elsewhere |
| Access needed | Read access to the disks and cloud drives you scan |
So the risk profile is closer to opening a folder in Finder than to running a cleanup utility. If you are comfortable letting a program enumerate your files, you are comfortable with Neodisk's core operation.
Why open source and privacy claims are checkable
Neodisk is described as private, free, and open source. For a tool that indexes your entire disk, that combination is the part worth weighing:
- Open source means the code can be inspected rather than taken on trust. If you or someone you rely on wants to verify that no write or delete calls exist, that is possible in principle.
- Private in this context means the analysis stays local — the app shows you a treemap and sunburst view of your own storage rather than shipping a file listing somewhere.
- Free removes the usual trade-off where a "free" analyzer monetizes by nudging you toward paid deletion features.
None of these are guarantees on their own. Open source only helps if someone actually reviews the code, and "private" is a claim you can partly test by watching network activity. But together they make the safety question answerable instead of a matter of faith.
Where the real risk sits — and it isn't Neodisk
The failure mode people worry about is a tool deleting the wrong thing. With Neodisk, that risk moves to whatever you use after the scan. The workflow looks like this:
- Run Neodisk and read the treemap or sunburst view to find what is eating space.
- Decide what you actually want to remove — caches, old downloads, duplicate media, large unused apps.
- Do the deletion in Finder or another tool, where you can see and confirm each item.
Step 3 is where mistakes happen, and it is entirely outside Neodisk. A large block in a treemap might be a system file, a sparse disk image, or a folder you still need. The scan tells you where space went; it does not tell you what is safe to delete. Treat the visualization as a map, not a recommendation.
Practical conditions for using it safely
- Point it at drives you own or administer. Scanning a shared or work-managed volume may be fine technically but could conflict with local policy.
- Expect read access, not write access. If a drive is mounted read-only, analysis should still work; cleanup obviously would not.
- Verify the download source. Since it is open source, prefer the official site or a package manager listing rather than a mirror. The site lists a Homebrew cask install (
brew install --cask neodisk) alongside direct downloads for Mac (Apple silicon and Intel) and Linux, plus a web demo. - Keep the two phases separate in your head. Scan in Neodisk, delete elsewhere. If you ever find yourself expecting Neodisk to free space for you, you have crossed into a job it does not do.
Bottom line
Neodisk is safe to run against your files because it does not touch them — it reads and visualizes, nothing more. The residual risk is not in the scan but in what you do with the information afterward, and that risk exists with or without Neodisk. If you want a disk analyzer that cannot delete anything by construction, and you value being able to inspect the code, the read-only, open-source design is the reason to trust it. If you want a tool that also cleans up, you will need a second tool — and that is where you should apply your caution.