Why Mac Disks Keep Filling Up at Work, and How IT Can Get Ahead of It

Every IT team that supports Macs knows the ticket. A designer cannot export a project, a developer’s build fails halfway, or a macOS upgrade refuses to install because there is not enough room. Someone frees a few gigabytes, the ticket is closed, and a few weeks later the same Mac is back in the queue.

The pattern is familiar because the cause is rarely a single large file. Storage on a work Mac fills up gradually, from many sources at once, and most of them are invisible to the person using the machine. Treating each incident as a one-off cleanup keeps the queue busy without changing the trend. A small amount of policy and visibility does far more.

Where the Space Actually Goes

A Mac used for real work accumulates data in places that Finder does not put in front of anyone. The usual suspects:

• Caches. Browsers, collaboration apps, design tools and media apps all keep caches to stay fast. Most rebuild themselves if removed, but they also grow back, and some apps are generous about how much they keep.
• Developer files. Xcode build data and simulators, node_modules folders in every project, package manager caches and Docker images can easily reach tens of gigabytes on a single engineering laptop.
• Duplicates and forgotten downloads. Installers, exported videos, zipped deliverables and copies of the same asset saved in three project folders.
• Cloud sync folders. OneDrive, Google Drive, Dropbox and iCloud Drive can keep files online only, but anything opened once is often stored locally afterwards. A second account, or a folder left behind by a disconnected one, doubles the effect.
• Local snapshots and purgeable space. Time Machine keeps local snapshots on the startup disk, and macOS counts some of that space as purgeable. It can be reclaimed on demand, but not always at the moment an installer or an app needs it.
• Chat, mail and phone backups. Attachments in messaging and mail apps, plus old iPhone or iPad backups, sit deep in the user Library.

None of this is misuse. The problem is that Storage settings summarizes much of it under broad labels such as “System Data”, which tells the user very little about what can go.

Why Users Cannot Clean Up Safely on Their Own

Asking employees to “free up some space” puts them in an awkward position. They can see that the disk is full, but not which of the large folders in their Library are caches that rebuild and which hold the only copy of something important. Some respond by deleting nothing. Others delete the wrong thing, or run a cleaning utility that promises big numbers without explaining what it removes.

Two details make this harder than it looks:

1. File size is not the same as space on disk. APFS supports clones, copies that share storage with the original. Deleting a cloned file can free far less than its listed size suggests, so a cleanup that looks impressive in Finder may change little on the disk.
2. Deleting is not freeing. Files moved to the Trash still occupy space until the Trash is emptied, and cloud files removed locally may download again the next time someone opens them.

The Hidden Cost of a Full Disk

A full disk is easy to dismiss as an inconvenience. Across a fleet, the costs add up in ways that rarely show up in one report.

Failed or delayed macOS updates

Major macOS upgrades need a large amount of working room to download, unpack and install. A Mac without it simply does not upgrade, which leaves security patches waiting and stretches the rollout window for the whole fleet. The dux guide on preparing a Mac for a macOS update when space is tight explains why the safe margin is much larger than people expect.

Slow machines and lost time

macOS uses free space for swap and temporary files. A Mac that runs close to full tends to feel sluggish, and the person using it often blames the hardware rather than the disk.

Support tickets that repeat

Every manual cleanup costs a technician’s time and the employee’s time. When the underlying growth is not addressed, the same Mac returns, and the cost is paid again.

Buying storage that cannot be added later

On most current Macs the internal storage cannot be upgraded after purchase. When a model runs out of room, the remaining options are external drives, a replacement machine, or ordering larger configurations next time. Larger SSDs are an expensive way to compensate for space that could have been recovered, and that decision is locked in for the life of the hardware.

What a Sensible Fleet Storage Policy Looks Like

A workable policy does not need to be elaborate. It needs a few clear decisions and the data to back them up.

Set a free space threshold. Pick a minimum that leaves comfortable room for updates and daily work, and treat Macs below it as needing attention before they generate a ticket.

Measure it continuously. Free space should be a reported attribute in the device management system, not something discovered when a user calls. Both Intune and Jamf can collect it with a small script.

Know why, not just how much. A low free space value says which Macs are at risk. It does not say whether the culprit is a cache, a forgotten Docker image or an old phone backup. The answer determines whether the fix is a quick cleanup or a conversation about the workload.

Decide what users may do themselves. Some organizations are happy for employees to clear their own caches. Others prefer that people can see what fills their disk but leave any removal to IT. Either choice is valid, as long as it is enforced consistently.

Plan purchases with data. Storage reports over time show whether a team genuinely needs larger drives or simply needs regular maintenance.

Keep cleanups reversible. Any tool used on company machines should make it hard to lose data by accident and easy to put things back.

How dux Fits Into That Policy

The macOS app dux (Disk Usage eXtended) shows where disk space goes and suggests cleanups ranked by how much space they actually free. The core app is free, and there is a Business edition aimed at exactly the fleet scenario described above.

Deployment through the existing MDM

The Business edition uses the direct download build, shipped as a signed and notarized installer package that can be distributed with Microsoft Intune, Jamf Pro, Kandji, Mosyle or Addigy. It is not offered through the Mac App Store, because Apple’s volume purchasing does not cover in-app purchases. The license key is delivered as a managed setting and activated silently, without user accounts or sign in. Sample profiles cover Full Disk Access approval and the login item, so employees do not face permission prompts, and a documented script removes everything again if needed. The app supports macOS 15, 26 and 27.

Managed settings

A configuration profile controls how the app behaves. A report only mode lets people see what fills their disk while removing every cleanup action, which suits organizations that want visibility without self-service deletion. Administrators can also stop the app from removing local cloud downloads, switch off categories of suggestions, hide upgrade notes and route updates through the MDM instead of the app. These restrictions apply in every plan, even if a license lapses. With Business, IT can additionally set default scan folders, folders that are never scanned and a scheduled scan interval for the whole organization. Employees see a short note that a setting is managed by their organization.

Fleet disk reporting

This is where the Business edition addresses the “why” question. A helper inside the app reports free space, purgeable space, the estimated reclaimable space and a breakdown by category, such as developer files or caches, as an Intune custom attribute or a Jamf extension attribute. A Power BI template included with the license turns the Intune data into a fleet dashboard through Microsoft Graph. There is no hosted console: reports stay on the Macs and in the organization’s own management tools. The step by step guides for Intune disk reporting and Jamf extension attributes are useful even before any purchase, since they start with scripts that use only built-in macOS tools.

Per Mac pricing

Business is priced per Mac per year: €15 per Mac, with Macs from the 50th onward at €10 each, excluding VAT. Larger fleets are invited to discuss volume terms. Current details are on the dux Business page.

A safety model built for shared responsibility

For IT, the most important part may be how cautious the app is by design. Space figures reflect what a cleanup truly frees on disk, accounting for clones, rather than headline file sizes. Every suggestion carries a safety level of Safe, Review or Risky, and only safe items can be preselected. Before anything moves, a review sheet lists exactly what each action will do, and items go to the Trash or become APFS clones rather than being deleted outright. Activity keeps a log of every cleanup, and undo restores items as long as they are still in the Trash. The few actions that cannot be undone, such as certain developer tool commands or removing local cloud downloads, are named before they run. The app sends no telemetry about files or folders; the privacy and safety page sets out the details for a security review.

Practical Takeaways

• Treat storage as a fleet metric, not a ticket category. Report free space for every Mac in the MDM and review it before each major macOS rollout.
• Look for the cause before buying hardware. Caches, developer files, cloud downloads and backups often explain most of the growth, and they can be managed.
• Decide on self-service deliberately. Choose between letting people clean up with guardrails and giving them visibility only, then enforce that choice with a configuration profile.
• Insist on reversible cleanups. A tool that reviews every action and offers undo protects both the employee and IT.

The “disk full” ticket will never disappear entirely. With a clear threshold, regular reporting and a safe way to act on it, it can at least stop being the same ticket over and over again.