Back to StorageRadar
Support

Get help with setup, permissions, and review-first cleanup workflows.

This page covers the most common StorageRadar support paths: how to start from the right workflow, how to interpret blocked coverage, when Reports differs from Large Files, and when to email support.

Quick start

Most support cases get resolved faster when the workflow is narrowed down first: current scan, permissions, historical diff, app leftovers, or MCP setup.

1

Run or reopen the right scan

Start from Home, Developer, System, or a custom folder and let the scan finish before judging the result. Wrong scope or incomplete coverage is the fastest way to get a confusing outcome.

2

Review the evidence before any apply action

Use Disk Map, Large Files, App Uninstaller, Dev Cleanup, or Reports to inspect what StorageRadar actually found. Preview-first workflows exist so you can confirm paths, size, and risk before acting.

3

Check Permissions when coverage looks incomplete

If you see blocked paths, missing app leftovers, or limited scan coverage, open Permissions and re-check access. StorageRadar shows blocked areas explicitly instead of pretending they are empty.

4

Contact support with context

If the result still does not make sense, email [email protected] with your macOS version, the StorageRadar area you were using, what you expected, and what you actually saw.

FAQ

Does StorageRadar work without internet?

Yes for core workflows. Scanning, analysis, preview, dry-run, permissions diagnostics, snapshots, reports, and local MCP access all work on-device. Network is only relevant for optional analytics or diagnostics if enabled, and for future Mac App Store purchase or restore flows.

Why do I see blocked paths or incomplete scan results?

macOS privacy controls and sandbox limits can restrict what the app can inspect until the right permissions are granted. StorageRadar is designed to show blocked coverage clearly. Open Permissions, review what is missing, grant access if appropriate, then rerun or re-check the workflow.

What is the difference between preview and apply?

Preview mode lets you inspect scan results, uninstall traces, developer cleanup candidates, dry-run output, and snapshot history without changing files. Apply actions are for real cleanup work such as Move to Trash, Delete Permanently, App Uninstaller apply, or Dev Cleanup apply when those actions are unlocked.

How are Reports different from Large Files?

Large Files answers what is big in one current scan. Reports compares saved snapshots across time and answers what grew, shrank, appeared, or disappeared. Diff requires two compatible snapshots from the same root scope.

What does the MCP integration expose?

StorageRadar MCP is local and read-only. It can expose scan metadata, largest-item analysis, snapshots, diffs, and developer cleanup summaries through a token-authenticated local endpoint on 127.0.0.1. It does not expose file contents and it cannot delete or move files.

System requirements and support scope

StorageRadar support is centered on the current macOS app workflows and the public beta era product model described on this site.

  • macOS 15 or later.
  • Core workflows are local-first and do not require a StorageRadar account or cloud sync.
  • Full scan and cleanup coverage may depend on macOS permissions for protected folders and app-owned locations.
  • Reports comparison requires two compatible snapshots from the same root scope.
  • MCP requires enabling Integrations inside the app and using a local client that supports MCP.

Troubleshooting

Blocked paths and permissions

  • Open Permissions if StorageRadar shows blocked items, warnings, or gaps in expected coverage.
  • Grant only the access you are comfortable with, then re-check coverage instead of assuming the scan silently updated.
  • For app leftovers and protected Library paths, macOS permissions may change what can be reviewed or applied.

Results look empty, partial, or smaller than expected

  • Confirm you scanned the right source and waited for the scan to finish before comparing totals.
  • Review whether blocked areas are affecting the folders or apps you expected to inspect.
  • Use the workflow that matches the question: Disk Map or Large Files for current size, Reports for historical change, App Uninstaller for leftovers, and Dev Cleanup for known developer profiles.

Reports and snapshot diff limitations

  • Diff only works when you have two saved snapshots that belong to the same root scope.
  • Snapshot history is stored locally, so comparison depends on what was captured on this Mac.
  • If a diff will not build, check that both snapshots are compatible before assuming the report is broken.

MCP connection basics

  • Enable MCP in Integrations first, then confirm the local server is running before troubleshooting the client.
  • Use the local endpoint and bearer token shown by StorageRadar, then test a simple call such as get_server_info.
  • Remember that MCP is intentionally read-only: it can answer questions about scans and snapshots, but it cannot inspect file contents or perform cleanup actions.

Contact support

If you email support, the fastest path to a useful answer is to include the workflow you were using and the exact point where the result stopped making sense.

Email: [email protected]

Helpful details to include:

  • macOS version and StorageRadar build or version if visible
  • Which area you were using: Disk Analysis, App Uninstaller, Dev Cleanup, Reports, Permissions, or MCP
  • What you expected to happen, what happened instead, and whether blocked paths were involved
  • Any exact error text, screenshot, or MCP client message you can share

Need the product overview first? Go back to the StorageRadar home page.