Scan. Choose a supported tool and location. Read any missing-access or skipped-location notice.
Review. Inspect the file paths and categories. A result is a candidate, not an instruction to delete it.
Understand sizes. Compare measured sizes; APFS sharing and snapshots can affect what deletion actually frees.
Select. Keep anything you still need. In-use caches are not preselected; that does not make every other item disposable.
Confirm. Read whether the action moves files to Trash or permanently removes them. Local model removal and simulator erasure need particular care.
Recover where supported. Put Back restores supported Trash moves without overwriting replacements. Review the Trash before emptying it: it still uses storage until then, and permanent removal cannot be undone.
MacBook Pro M4 Pro, 48 GB RAM; macOS 26.6.2; MacMonitor debug 1.0.0; November 4, 2026. Read-only Junk scan: 10.62 GB found and 8.79 GB selected in this capture. Nothing was cleaned or deleted. These are candidate sizes, not measured reclaimed storage or a typical result.
Privacy and purchase requirements
Scans run locally. The app has no analytics; the direct license makes activation and periodic verification requests, and Check for Updates makes a request when you choose it. Read the privacy details. The app requires macOS 14 or later.
One license covers one Mac. The current introductory offer is US$4.99 for the first 50 purchases, followed by a stated regular one-time price of US$19. Checkout confirms availability, taxes and the final total. Buy MacMonitor for Mac.
What it finds
MacMonitor's Cleaner starts with Smart Scan, which runs the tools below together and cleans only what is safe in one step, and adds Clean System Data in Storage Lens. Every tool shows what it found, how big it is, and what will happen, before it does anything.
Clean System Data
Storage Lens → System Data measures supported storage contributors it can read. Apple calculates its System Data total separately. Review eligible caches and old browser update copies for Trash cleanup with Put Back. The direct edition also lists supported simulator removals with their own permanent-action confirmations. Docker disk images are shown for review. See what MacMonitor handles.
Smart Scan
New in 1.2. One scan for junk, build caches, AI models and idle apps, then one Clean for the parts that are safe to remove without looking. Models, idle apps, backups and archives are listed for review and never removed by Smart Scan.
Junk cleaner
App caches, logs, crash and diagnostic reports, saved application state, old installers in Downloads, iOS device backups, and what is in your Trash. Caches are labelled with the app they belong to, and caches an open app is using are never pre-selected. iOS backups and the Trash are never pre-selected either.
Duplicate finder
Compares file contents, not just names or sizes, in a folder you choose. It always keeps one copy and moves the rest to the Trash, where you can recover them. Hard links are not counted as copies, because removing one frees nothing.
Large & old files
Lists big files, 100 MB and up by default, sorted by the space they really take on disk, so a sparse disk image that claims 400 GB but holds 3 GB is not offered as 400 GB. Sort by size, age or name.
Idle apps
Shows apps unused for 90 days or more, with their leftover files found automatically. Only clearly regenerable leftovers, such as caches and logs, are pre-selected. An app that is still open is asked to quit first.
For developers there is more: local AI model weights (Ollama, LM Studio, Hugging Face), Xcode DerivedData and archives, stopped simulators, package manager caches, and node_modules folders, each with its own review.
How a cleanup works
1 · ScanSee it first
Sizes and categories appear before you choose anything.
2 · ReviewPick what goes
Every item is listed. Things like iOS backups and the Trash are never pre-selected.
3 · ConfirmThen it moves
Most items go to the Trash. Put Back can restore supported recorded moves; check any reported failures.
Safe by design
Trash first. Most cleanup moves items to the Trash. Permanent actions include erasing Trash items, removing local models and erasing simulator data. Read the action-specific warning before confirming.
Honest numbers. Moving something to the Trash is not counted as freed disk space, because the space is only free once the Trash is emptied.
Checked again before removal. The list on screen can be minutes old, so each item is compared with the file on disk immediately before it is removed, and anything that changed or moved is left alone and reported.
Protected locations. Cleanup refuses protected system locations rather than just hiding them.
Put Back for supported moves. After a supported cleanup, a banner offers to restore recorded Trash moves without overwriting replacement files. Review failures; permanent actions are not recoverable through Put Back.
Never inside packages. Your Photos library and app bundles are treated as single items, so a scan never offers a file from inside them. Scans of your home folder also stay out of app data in ~/Library.
iCloud-safe. Files kept only in iCloud are skipped and never downloaded to compare them, since removing one would delete it on every device and free nothing here.
Apps in use are respected. Caches of apps that are open, and of system services with work in progress, are listed as in use and never selected for you.
Nothing automatic. MacMonitor never deletes on a schedule or in the background.
It is not an antivirus and does not promise a faster Mac. Allocated size is not guaranteed free space, because APFS clones and snapshots can share disk blocks; the app says so where it matters. It works with the folders you point it at and, if you grant Full Disk Access, the whole disk.
A Mac storage cleaner should help you understand a removal before it happens. Start with the task that brought you here: making room for an installer, reviewing duplicate downloads, clearing supported development output, or removing an application you no longer use. Different tools address different parts of that work.
The most useful result is a file or category you can explain. Read the path, its owner and the action’s consequence. A large selection total does not establish that the selected files are unneeded, and it does not guarantee an identical increase in available storage. Treat the scan as the beginning of a decision.
Match each category to a different decision
App caches and logs are different from an old project, a downloaded model or a device backup. A cache may be replaceable but useful for offline work. A project may contain the only editable version of your work. A model removal may mean downloading a large file again. Review those costs before deciding what to clean.
For duplicate files, establish which copy remains and where it lives. For large files, identify whether a result is an original, export, package or virtual disk. For applications, preserve documents and use the vendor’s uninstaller when one is required. A single “remove everything” habit ignores these differences.
A documented Cleaner example
The native Junk screenshot on this page came from a read-only capture on November 4, 2026. The machine was a MacBook Pro M4 Pro with 48 GB RAM and macOS 26.6.2; the installed debug app reported version 1.0.0. It showed 10.62 GB found and 8.79 GB selected, with some in-use caches excluded from automatic selection.
No cleanup was applied during that capture. These figures are useful for seeing the interface’s found-versus-selected distinction, not for predicting a customer’s result. They are not measured reclaimed storage, a typical saving or proof of faster performance. The caption keeps the context visible beside the image.
Use a small first cleanup
Pick a category whose purpose you understand and save work in the affected applications.
Inspect the candidates and leave uncertain files unselected.
Read whether the operation moves items to Trash or removes them permanently.
Confirm the action and review any itemized failures or skipped items.
Test the task you wanted to improve before permanently emptying reviewed Trash items.
A small first operation makes recovery easier to reason about. If an application needs to rebuild a cache or download something again, you can connect the effect to a specific choice. A large mixed cleanup makes that connection harder.
Understand permissions and skipped locations
macOS protects some locations, and a scan can be incomplete when access is unavailable. Read the app’s missing-access or skipped-location notice. A folder that was not measured should not be interpreted as empty, and a partial scan should not be represented as a complete account of the disk.
Grant permissions only when they fit the inspection you intend to perform. You can often review an understood folder before considering wider access. No permission makes every file in a measured location disposable; the retention decision remains yours.
Recovery is a convenience alongside a backup
Put Back is for supported recorded Trash moves and avoids overwriting a replacement at the original path. It cannot make an emptied Trash or a permanent removal reversible. If something changed after scanning or after a move, read the resulting report instead of assuming a blanket restore succeeded.
Keep an independent backup of important work. Before clearing a development environment or removing large app data, establish what you would need to recreate it. A source repository may not include local databases, simulator test records, offline downloads or release artifacts.
Decide when the cleanup is complete
Recheck the task that required room. If the installer can proceed and you have preserved the files you need, more deletion is not automatically beneficial. Keep a short record of the categories reviewed and any recovery action available, then investigate recurring growth separately if the disk fills again.
MacMonitor combines this reviewed cleanup workflow with its file organizer and Activity view. Organizing folders and monitoring resources answer related questions, but neither should be described as measured storage recovery or automatic optimization.
Questions
Is it safe to use a Mac cleaner?
It depends on the cleaner. MacMonitor shows every item before removing it, moves most items to the Trash so they can be restored, refuses protected system locations, and re-checks each item right before it acts.
Will it free up as much space as it says?
It reports what it can measure honestly. Items moved to the Trash still use disk space until the Trash is emptied, and APFS clones and snapshots can share blocks, so allocated size is not a guarantee of freed space.
How does the duplicate finder decide which copy to keep?
It compares file contents in a folder you choose, groups exact duplicates, and always keeps one copy. The rest go to the Trash, where you can recover them.
Can it remove local AI models and build caches?
Yes. It finds model weights for Ollama, LM Studio and Hugging Face, and developer caches such as Xcode DerivedData, simulators, package manager caches and node_modules, and lets you review each before removing.
Does the Cleaner run automatically?
No. It only acts when you review and confirm a cleanup.
Ready when you are
MacMonitor is available now for macOS 14 or later.