Switching guide

From JDiskReport to NullDisk

Leaving JDiskReport? Good news: disk scans are reproducible. Here's how to carry your workflow over to NullDisk in four steps — without losing track of a single gigabyte.

What you can take with you

JDiskReport

JDiskReport's tables don't migrate anywhere — note the top-50 paths and oldest trees, then verify and clean them in NullDisk.

Step by step

STEP 01

Inventory what matters

JDiskReport's tables don't migrate anywhere — note the top-50 paths and oldest trees, then verify and clean them in NullDisk.

STEP 02

Run a fresh NullDisk scan

Open NullDisk, pick the same volume or folder, and let it measure everything — allocated size, hard links included. What you see now is ground truth.

STEP 03

Rebuild your cleanup queue

Drag each flagged item into the Ready-to-Remove collector. Review sizes, previews, and paths at leisure — nothing is deleted yet.

STEP 04

Trash once, verify twice

Move the collector to the Trash in one step, then rescan to confirm the reclaimed space. Uninstall the old tool only after the numbers check out.

Frequently asked questions

Can I export reports from JDiskReport?

JDiskReport's tables don't migrate anywhere — note the top-50 paths and oldest trees, then verify and clean them in NullDisk.

Will I lose anything by switching?

No — scans are reproducible. A fresh NullDisk scan of the same volume shows the same files with allocated-size accuracy, usually within minutes.

Is NullDisk hard to learn after JDiskReport?

Most switchers are productive in minutes: the radial map reads instantly, and the collector mirrors the 'gather then delete' habit you already have.

See alternatives → · Read the review →

Also consider