Installer files are unusual among the things cluttering a Mac: they have a single, well-defined job, and once that job is done, the file has no further purpose. Unlike a document or a photo, you're never going to open an old .dmg "just to look at it." That makes installer cleanup one of the lowest-risk categories of cleanup on the whole system — and yet most Macs accumulate years of them in ~/Downloads, because there's rarely a moment that feels like the right time to delete one.
What each installer format actually does
Three formats make up nearly all Mac installers, and understanding what each one does explains why none of them need to survive past first use:
.dmg (disk image) mounts as a virtual disk when you double-click it, usually showing a window with the app icon and an Applications folder shortcut for you to drag into. Once you've dragged the app across, the mounted image can be ejected and the original .dmg file deleted — the app now lives independently in /Applications, with no ongoing dependency on the disk image it arrived in.
.pkg (installer package) runs a guided installation script that places files across the system — sometimes in /Applications, sometimes in /Library, sometimes in several places for a complex piece of software. Like a .dmg, its job finishes the moment the installer completes; the .pkg file itself is not referenced again afterward.
.zip is a general-purpose compressed archive and is the one format on this list that isn't necessarily disposable — it might contain an app, but it might also contain a font, a document, or a project. Treat zip files individually rather than assuming they follow the same "delete after use" rule as .dmg and .pkg.
The quarantine flag, and why it's not a safety indicator for deletion
Every file downloaded through a browser gets a com.apple.quarantine extended attribute, which is what triggers the "are you sure you want to open this?" dialog the first time you launch a downloaded app. This is worth understanding because it's easy to mistake for a signal about whether a file is safe to keep or delete — it isn't. Quarantine is purely a first-run security gate for Gatekeeper; it has nothing to do with a file's usefulness after that first run. An installer you've already run once, quarantine flag and all, is exactly as disposable as one you never opened.
Recognising a notarized installer versus one that isn't
Apple's notarization process checks a developer's software for known malware signatures before Gatekeeper will let it run without a manual override. You can check whether an app you've installed was notarized (though this doesn't apply to the installer file itself, since the installer is a container, not the executable):
spctl -a -vv /Applications/SomeApp.app
A result mentioning source=Notarized Developer ID confirms it passed Apple's check. This is useful context when deciding whether to trust an installer enough to run it in the first place, but it has no bearing on whether the leftover .dmg or .pkg file is worth keeping afterward — notarization status doesn't change once the app is installed, so there's no reason to hold onto the installer as some kind of ongoing proof.
A practical sort-and-clear method
Open ~/Downloads, switch to list view, and use Finder's search with Kind: Disk Image and Kind: Installer Package to isolate exactly the file types this article covers, separate from documents and photos mixed into the same folder.
| Signal | What it means |
|---|---|
App already appears in /Applications |
Installer's job is done, safe to delete |
| File is more than a few months old | You would re-download a fresher version anyway if needed |
Filename has (1), (2) suffixes |
Duplicate downloads of the same installer |
| You don't recognise the app name at all | Likely from a tool you tried once and abandoned |
Work through the list and delete anything matching two or more of these signals without hesitation — this is close to the safest category of file to remove on the whole system.
When to actually keep one
There are a few legitimate reasons to keep an installer around rather than relying on a future re-download:
- The developer's site has since removed the version you need, and you rely on that specific version for compatibility with an older workflow
- You're on a slow or limited connection and want to reinstall the same app on another Mac without downloading it twice
- It's an installer for hardware-specific drivers or firmware tools that aren't trivially discoverable again
If any of these apply, move the specific installer to an archive folder rather than leaving it mixed into Downloads — that way it's a deliberate keep, not clutter you forgot to sort.
Building the habit so this doesn't recur
The reason installers pile up isn't carelessness — it's that deleting one right after use rarely occurs to anyone, since the moment of installing an app doesn't naturally prompt a cleanup thought. Tying installer cleanup to a regular Downloads review (weekly or monthly) closes that gap far more reliably than trying to remember to delete each one individually right after use.
Mounted disk images left behind
A related, less obvious source of clutter: a .dmg you've opened but not ejected stays mounted as a virtual volume, appearing in Finder's sidebar and consuming a small amount of memory even though the underlying file itself isn't duplicated on disk. Check Finder's sidebar under Locations for any mounted volumes with installer-sounding names, and eject them once you've finished with the installer — right-click the volume and choose Eject, rather than leaving it mounted indefinitely because the install already finished.
Installers bundled inside other archives
Occasionally an installer arrives nested inside a .zip alongside a readme file or licence document, rather than as a standalone .dmg or .pkg. In this case, deleting just the extracted installer without also removing the original .zip leaves half the clutter behind — check whether the archive itself is still present after extraction, since both the compressed original and the expanded installer serve the same one-time purpose and neither needs to persist afterward.
Where VolumeLens comes in
Installers are exactly the kind of low-risk, high-volume clutter a storage map surfaces quickly — dozens of files, individually unremarkable, collectively significant. VolumeLens sorts everything in Downloads by actual size, so a folder full of old .dmg and .pkg files shows up clearly rather than requiring a manual Kind-based search, and nothing leaves the disk until you've reviewed and confirmed it in the review sheet.