In this article
Identify the three things on your Mac
A downloaded .dmg file, the volume it mounts, and an app copied out of that volume are different objects. Opening the download gives you access to its contents; that alone does not establish that a separate installed copy exists.
| Object | Where you might see it | What removing it changes |
|---|---|---|
| Downloaded disk-image file | Downloads, with a .dmg extension | Removes that container when deleted |
| Mounted volume | Finder sidebar under Locations | Ejecting detaches the volume; the download remains |
| Copied application | Applications, or the developer's specified destination | Removing this copy removes the application at that location |
Apple's installation guide distinguishes opening a disk image or package from completing the supplied installation steps. Follow those steps before cleaning up the download. Some images contain an app to copy; others contain an installer that must run.
The Applications folder shown inside an installer window is often a shortcut to the destination. It is not evidence that copying has finished. If the distinction between a reference and its target is unclear, our Mac alias guide explains what an alias does and what deleting one actually removes.
Prove that the installed copy works
Use a short check with the image unavailable. This is more informative than seeing the app's icon in the Dock, because a convenient launch shortcut does not tell you which copy you previously opened.
- Finish the developer's installation instructions. For a drag-to-install app, wait until the copy to Applications completes.
- Save your work and quit the app normally. Closing its window may leave the application running.
- In Finder, eject the mounted volume associated with that download. Check the volume's name before choosing Eject.
- Open a fresh Finder window, go to Applications, and open the actual application there. Avoid reopening the download during this check.
- Confirm the app opens and performs a small ordinary task you need. Only then move the downloaded installer to the Trash if you no longer need it.
For example, with a text editor, opening a disposable document and saving it is a more useful check than stopping at a splash screen. It still cannot prove that every optional feature, plug-in, or offline dependency works. Choose a check appropriate to the application rather than treating a successful launch as a complete acceptance test.
Watch the copy-and-eject sequence
MacMost’s May 8, 2024 tutorial demonstrates the drag-to-install workflow. The section at 4:11 covers disposing of the disk image after installation. This is an older demonstration of the file-copy mechanism; follow the current developer instructions for your particular app.
What our copy experiment showed
On October 8, 2026, we ran a controlled test on macOS 15.7.5. We compiled a tiny executable that prints a fixed message, put it inside an app-shaped bundle, and created a compressed disk image containing that bundle.
We mounted the image, copied the bundle to a separate temporary folder, and compared the executable bytes. Then we ejected the image normally and removed our disposable DMG. The copied executable continued to run.
| Test stage | Mounted source | Separate copy |
|---|---|---|
| Image mounted, copy complete | Executable present on the mounted volume | Identical executable bytes on a different filesystem device |
| Image ejected | Mounted executable path no longer available | Executable still returned the expected message |
| Temporary DMG removed | Image file no longer present | Executable still worked; SHA-256 stayed unchanged |
This tests the independence of copied files, not the installation behavior of every Mac app. We used a temporary destination instead of the system Applications folder and invoked our own executable directly. We did not test Finder drag-and-drop, a package installer, licensing, updates, or a third-party app's first launch.
The distinction matters: the experiment explains why deleting a delivery container does not erase a completed copy. Your own application still needs the practical check above, especially when its installation instructions include additional components.
If the image will not eject
An “in use” message is a reason to identify the user of the volume, not to force the cleanup. Save and quit an app running from the image, and close documents opened from it. Apple's disk-ejection troubleshooting guide starts with quitting the application using the disk.
If the app you meant to install still depends on the mounted source, return to its installation instructions. Do not delete random helper files, terminate unfamiliar processes, or bypass a security warning to make the installer disappear. Those actions answer different questions.
A .pkg inside a DMG also needs its own installation to finish. Copying the package somewhere else is not the same as installing its contents. If you later need to investigate what a package installed, use our package-receipt file inventory guide; deleting the downloaded package does not undo its completed installation.
Keep images whose contents still matter
The .dmg extension is not a disposable-file label. Apple's Disk Utility guide explains how people can create images for files and folders, including encrypted images. Such an image may contain someone's only copy of important documents.
For an installer, consider whether you need that exact release again. An older compatible version, an offline setup requirement, or a developer that no longer distributes the same file can justify keeping it in a clearly named archive. Record the app and version so the reason for retaining it remains understandable later.
Before deleting, verify the object, the completed copy, and your reason for keeping it. Ejecting removes the mounted volume from view; deleting the download removes the container; uninstalling the app is a separate decision. If your goal is disk-space accounting, Finder and macOS Storage totals also need to be interpreted separately.
