Knowing how to clean mac with multiple users is trickier than it sounds. A single Mac shared by a family, a household of roommates, or a small office can accumulate gigabytes of redundant caches, old downloads, and forgotten app data spread across every account — and a cleanup tool that only sees the currently logged-in user can leave most of that clutter untouched. This guide walks through exactly where junk hides per-account and in shared system folders, how to clean safely without touching another person's files, and what to look for in a Mac cleaner that actually understands the multi-user layout of macOS Sequoia and Tahoe.
How macOS Organises Storage Across User Accounts
macOS keeps a strict separation between user data and system-level data. Each account has its own home folder under /Users/username/, and most app-generated clutter lives inside that home folder. A few locations are shared, but they are read-only for ordinary users. Understanding this boundary is the first step to cleaning without accidentally crossing into someone else's space.
- Per-user caches:
~/Library/Caches/— Safari, Chrome, Xcode, and almost every app write here under the current account only. - Per-user logs:
~/Library/Logs/— crash reports and app logs are isolated per account. - Per-user app support:
~/Library/Application Support/— databases, thumbnails, and offline data stored by apps. - Per-user developer caches:
~/Library/Developer/Xcode/DerivedData/,~/.cargo/,~/.m2/repository/,~/.gradle/caches/— these can balloon to tens of gigabytes per developer account. - Shared system caches:
/Library/Caches/— writable only by admin processes; safe to inspect but requires elevated privileges to clean.
The practical implication: if you run a cleanup tool while logged in as one user, it typically only scans that user's home folder. The other accounts remain untouched until someone logs into them and runs a scan.
Where the Biggest Junk Accumulates on a Shared Mac
On a family or shared Mac, certain folders tend to grow especially large. The table below shows the most common culprits, where they live, and rough sizes you might expect after a year of typical use.
| Folder | Scope | Typical size range | Safe to delete? |
|---|---|---|---|
~/Library/Caches/ |
Per user | 2 – 20 GB | Yes — apps rebuild on next launch |
~/Downloads/ |
Per user | 1 – 50 GB | Review first — user files may be here |
~/Library/Developer/Xcode/DerivedData/ |
Per user (developer accounts) | 5 – 40 GB | Yes — Xcode rebuilds on next compile |
~/.cargo/registry/ |
Per user (Rust developers) | 1 – 10 GB | Yes — re-downloaded on next build |
~/.m2/repository/ |
Per user (Java/Maven developers) | 1 – 8 GB | Yes — re-downloaded by Maven |
~/Library/Application Support/ |
Per user | 2 – 15 GB | Selective — contains app data and databases |
/Library/Caches/ |
System-wide (shared) | 0.5 – 3 GB | Yes, with admin rights — macOS rebuilds |
| Trash across all users | Per user (~/.Trash/) |
Varies widely | Yes — empty each account's Trash |
How to Clean Each User Account Without Breaking Anything
The safest workflow on a shared Mac is to clean account-by-account. Here is a step-by-step approach using macOS built-in tools and manual commands, suitable for any account on macOS Sequoia or Tahoe (Apple Silicon or Intel).
- Log into each account in turn. Fast User Switching (available in Control Center) lets you move between accounts without fully logging out, though for a thorough cache clear it is better to log out completely and back in.
- Open a Terminal window and check cache size:
du -sh ~/Library/Caches - Clear the user cache folder:
rm -rf ~/Library/Caches/*
This is safe — macOS and apps recreate entries as needed. Do not delete theCachesfolder itself, only its contents. - Remove old Xcode derived data (developer accounts only):
rm -rf ~/Library/Developer/Xcode/DerivedData/* - Clear old logs:
rm -rf ~/Library/Logs/* - Empty that account's Trash: In Finder, choose Finder > Empty Trash, or right-click the Trash icon. Each user has their own
~/.Trash/folder that only empties when they do it themselves. - Review Downloads: Sort
~/Downloadsby date and size. Disk images (.dmg) and installer packages (.pkg) that have already been used are safe to remove.
Repeat these steps for every account on the Mac. If one family member is less technical, you can log into their account with their permission and run the same steps.
The System-Level Storage That Belongs to No Single User
Beyond per-user home folders, shared Macs accumulate storage in locations that no individual account fully owns. These include:
- System caches at
/Library/Caches/— written by system daemons and some apps that run as root. - Shared application support at
/Library/Application Support/— some apps store licence databases or shared resources here. - Old iOS device backups at
~/Library/Application Support/MobileSync/Backup/— created per-user when iTunes or Finder performs a phone backup. On a family Mac where multiple people sync their iPhones, this folder can easily exceed 30 GB across accounts. - Time Machine local snapshots managed by the system — viewable in System Settings > General > Storage. macOS purges these automatically under space pressure, but they can temporarily inflate reported usage.
For a deeper look at what is consuming space at the system level, the guide on what is System Data on Mac storage explains how macOS categorises these hidden volumes.
Choosing the Right Cleaner Tool for a Multi-User Mac
Most Mac cleaner apps only scan the account they are launched from. On a single-user machine this is fine, but on a family Mac it means a parent running a scan will not see the clutter in their child's account or vice versa. When evaluating tools, look for:
- Per-account scanning: The tool should make clear which account's data it is showing, and ideally let an admin account scan other accounts with permission.
- Transparency before deletion: Every file marked for removal should be visible and reviewable. On a shared Mac, an opaque "clean now" button carries real risk of deleting someone else's important files if paths are misidentified.
- Developer folder awareness: A family Mac used by a developer may have massive caches in
~/Library/Developer/,~/.cargo/, or~/.m2/. The tool should surface these specifically, not lump them into an unidentified category. - Safe system-cache handling: Cleaning
/Library/Caches/requires elevated privileges. A responsible tool will ask for permission explicitly and explain what it is deleting.
A tool like Crumb can audit all of these locations at once — user caches, developer build folders, old logs, and system caches — and shows exactly what it found and why it is safe to remove before anything is deleted. That review step is especially valuable on a shared Mac where one cleanup decision can affect everyone.
Managing iOS Device Backups on a Family Mac
iOS backups deserve special attention. On a family Mac where two or three people regularly sync iPhones or iPads, the backup folder can be the single largest consumer of storage. Each device backup lives at:
~/Library/Application Support/MobileSync/Backup/
Each backup is stored as a folder named by the device's UDID. To see what is there, open Finder, go to the menu bar and choose Go > Go to Folder, paste the path above, and browse the subfolders. The modification date tells you when the last backup occurred.
In macOS Sequoia and Tahoe, manage backups through Finder > [Device name] > Manage Backups when a device is connected. You can delete outdated or duplicate backups from this interface safely. Old backups for devices you no longer own are immediate wins — some families find 10–20 GB here that no one knew about.
Keeping a Shared Mac Clean Long-Term
A one-time purge helps, but a shared Mac benefits from lightweight recurring habits:
- Set a calendar reminder for each household member to empty their own Trash and Downloads folder monthly.
- Agree on a "no installers" rule: once a
.dmgor.pkghas been used, move it to Trash immediately. - If one account is used by younger children who install many games or streaming apps, periodically review
~/Library/Application Support/in their account for abandoned app data from games they no longer play. - Use System Settings > General > Storage as a quick overview — it shows total usage per category (Applications, Documents, iCloud Drive, etc.) for the current user without needing any third-party tool.
- For a fuller picture of what is taking space across the whole drive, the article on what is taking up space on my Mac covers the best ways to investigate hidden storage consumers.
A shared Mac cleaned consistently is genuinely faster and more responsive. Browser caches alone — multiplied by three or four family members all using different browsers — can add up to 15–30 GB within a year. Clearing them per-account is one of the simplest and safest disk wins available.