Reports and portability

From diCleaner to NullDisk

Keep useful reports, check the current files, and rebuild only the cleanup selections you still need.

What you can keep from diCleaner

The cited pages do not establish scan-report export. Keep any important history or paths before rescanning; retain the original files until decisions are verified.

Saved scans describe files at a point in time. They do not contain the original file contents, and they do not replace a backup.

Switch in four steps

STEP 1

Keep useful records

The cited pages do not establish scan-report export. Keep any important history or paths before rescanning; retain the original files until decisions are verified.

STEP 2

Match the location and scope

Scan the same folder or volume in NullDisk. Match permissions, exclusions, and measurement mode where possible. A current scan will differ from a historical one if files or access changed.

STEP 3

Review the files, not just the total

Confirm full paths and previews. Logical size, allocated size, cloud object size, hard links, APFS shared blocks, and snapshots can explain differences between tools.

STEP 4

Choose an explicit cleanup action

In the Mac app, review collector items and the selected source before choosing Trash, permanent removal, or backup before deletion. Keep historical exports separately. Trash and snapshots can delay recovery of space.

Save a structured NullDisk report

Install the standalone CLI, then scan a location you control. The following commands inspect data and write reports; they do not remove files.

nulldisk scan ~/Downloads --json > disk-report.json
nulldisk dev ~/src --json > development-report.json

Reports may contain private paths. Review them before sharing and check the command’s exit status for incomplete results.

Common questions

Can I export a scan from diCleaner?

The cited pages do not establish scan-report export. Keep any important history or paths before rescanning; retain the original files until decisions are verified.

Can NullDisk import another analyzer’s scan or cleanup queue?

No direct import is documented. Scan the same filesystem again, preserve old reports as historical evidence, and rebuild only selections you have verified against the current files.

Can I export from NullDisk?

The separate nulldisk CLI produces JSON and NDJSON disk/development reports. These reports describe the measured scope; they are not backups or a GUI session import format.

About diCleaner → · Compare with NullDisk →