Parallels Taking Up Space on Mac: Shrink or Delete VMs (2026)

For developers who run Windows, Linux, or older macOS versions alongside their daily workflow, virtual machines are indispensable. But if Parallels is taking up space on your Mac, you may have already discovered the uncomfortable truth: a single VM disk image can silently balloon to 50, 80, even 150 GB over time — often becoming the single largest file on the entire machine. Parallels Desktop and VMware Fusion both store VMs as self-contained bundles on your Mac's SSD, and neither product makes it obvious how to reclaim that space.

Why VM Disk Images Grow So Large

Both Parallels (.pvm bundles) and VMware Fusion (.vmwarevm bundles) store their virtual machines as package directories on your Mac. Inside each bundle lives one or more virtual disk files:

• Parallels: *.hdd directories, typically inside ~/Parallels/<VM Name>.pvm/
• VMware Fusion: *.vmdk files, inside ~/Virtual Machines/<VM Name>.vmwarevm/ (or wherever you chose to save the VM)

These virtual disks use a technique called expanding (thin-provisioned) allocation: the file starts small and grows as the guest OS writes data. The problem is that when you delete files inside the virtual machine, the guest OS marks those blocks as free — but the host file on your Mac does not automatically shrink. Over months of Windows updates, package installs, and build artifacts inside the VM, the disk image grows steadily and almost never gives space back on its own.

Snapshots compound the problem further. Every snapshot you take creates an additional differencing disk file that records changes from that point forward. A VM with ten old snapshots can easily be twice the size of the base image alone.

Find Your VM Bundles Right Now

Before doing anything else, figure out exactly how much space your VMs are consuming. Open Terminal and run:

du -sh ~/Parallels/*.pvm 2>/dev/null
du -sh ~/Virtual\ Machines/*.vmwarevm 2>/dev/null

If you moved your VMs to an external or non-default location, use Finder's search (Command-F, kind: Folder) or check the path shown in each app's settings. You can also sort by size in Finder: open the folder, press Command-2 for list view, then click the Size column header.

If you want a visual overview across your entire Mac, Crumb's disk treemap (Visualize tab) surfaces .pvm and .vmwarevm bundles as large colored blocks alongside everything else on your SSD. Hovering a bundle triggers the "Is this safe to delete?" AI explanation, which tells you what the bundle contains and what removing it means — useful context before you commit to anything permanent.

Option 1 — Shrink a VM You Want to Keep

If the VM is still useful, shrink its virtual disk rather than deleting it. The process differs between Parallels and VMware Fusion.

Shrink a Parallels Desktop VM

1. Delete old snapshots first. In Parallels, go to Actions → Manage Snapshots. Delete any snapshots you no longer need. Each deleted snapshot can recover several gigabytes immediately. This step is required before you can compact the disk.
2. Free space inside the VM. Boot Windows or Linux inside Parallels and delete unneeded files — old installers, browser caches, Windows Update caches in C:\Windows\SoftwareDistribution\Download\. Empty the Recycle Bin. The more free space the guest OS has, the more the compaction step can recover.
3. Run Disk Cleanup inside Windows. Search for "Disk Cleanup" in the Start menu, run it on the C: drive, and check all categories including "Windows Update Cleanup."
4. Compact the virtual disk from Parallels. Shut down the VM (not suspend — a full shutdown). Then go to Parallels Desktop → Configure → Hardware → Hard Disk → Advanced → Compress (Reclaim disk space). Click Compress and wait. On large disks this can take 20–30 minutes.

Note: Parallels also offers a Clean Up Virtual Machine button in the VM configuration. This is different from compacting — it removes Parallels-generated temporary files and helper snapshots, and can recover a few extra gigabytes on its own.

Shrink a VMware Fusion VM

1. Delete snapshots. Open VMware Fusion, select the VM, then go to Snapshots (View menu → Snapshots). Delete any you no longer need. Snapshot disk chains can be very large.
2. Free space inside the guest. Boot the VM. On Windows, run Disk Cleanup. On Linux, run apt autoremove && apt clean or the equivalent for your distribution.
3. Use VMware Tools to clean and compact. With VMware Tools installed in the guest (it ships with Fusion), open a Terminal in Linux or a Command Prompt (as Administrator) in Windows and run:

   vmware-toolsd --cmd "disk shrink /path/or/C:"

   On Linux the path is typically /. On Windows it is usually C:.
4. Compact from VMware Fusion's menu. Shut down the VM completely. In VMware Fusion go to Virtual Machine → Settings → Hard Disk → Compact Disk. This triggers the host-side compaction that actually shrinks the .vmdk file on your SSD.

After compacting, recheck the size of the bundle with du — a well-maintained 60 GB VM can sometimes drop to 25–30 GB after cleaning internal space and compacting.

Option 2 — Delete a VM You No Longer Need

If you have VMs for testing a project that is finished, an old OS version you no longer support, or a Windows install you have not booted in a year, deleting them outright is the most effective way to reclaim space. A single deletion can free 50–100 GB instantly.

Warning: this is permanent. There is no undo. Before deleting any VM, make sure you do not need any data stored inside it. If the VM has files you want to keep, copy them out to your Mac or a backup drive first.

Delete a Parallels VM correctly

1. Open Parallels Desktop. The VM must not be running.
2. Right-click the VM in the Parallels Control Center.
3. Choose Remove → Move to Trash. Using this option ensures Parallels cleans up its own registry entries alongside the bundle.
4. Empty the Trash. The bundle can be large so the empty may take a moment.

Alternatively, locate the .pvm bundle in Finder (~/Parallels/ by default), drag it to the Trash, and empty. This leaves no functional data behind — the entire VM is self-contained in the bundle.

Delete a VMware Fusion VM correctly

1. Open VMware Fusion. The VM must be powered off.
2. Right-click the VM in the library and choose Delete. VMware will offer to move the bundle to Trash.
3. Alternatively, locate the .vmwarevm bundle in Finder (~/Virtual Machines/ by default), drag to Trash, and empty.

Other VM-Related Files Worth Checking

How to Stop VMs from Ballooning Again

• Set a fixed disk size at creation time. Both Parallels and VMware let you choose between an expanding disk (grows over time) and a fixed-size disk (allocated upfront, never grows). Fixed disks do not shrink on their own either, but they make the total footprint predictable from day one.
• Limit snapshot depth. Keep at most two or three snapshots per VM. Delete old ones after you have confirmed the VM works as expected.
• Suspend, do not leave VMs running. A running VM keeps its memory state written to disk (a .mem file or similar) in addition to the disk image. Suspend only when you need to resume quickly; shut down fully when you are done for the day.
• Compact after major cleanup sessions. After any large Windows Update cycle or build artifact purge inside a VM, run the compaction step described above to return those freed blocks to macOS immediately rather than letting them accumulate.
• Schedule periodic audits. Download Crumb and run a whole-Mac scan every few months. The treemap makes it immediately obvious when a VM bundle has grown out of proportion relative to the rest of your disk — before it becomes a storage emergency.

Parallels vs VMware Fusion: Storage Footprint at a Glance

Conclusion

Virtual machine disk images are routinely the single largest file on a developer's Mac — and because they live inside self-contained bundles, standard disk-cleaning tools and macOS's own storage management view overlook them entirely. If Parallels is taking up space on your Mac (or VMware Fusion is doing the same), the path forward is clear: delete old snapshots first, free space inside the guest OS, then compact the virtual disk using the app's built-in tool. If you no longer need the VM at all, deleting the bundle outright is safe and recovers the most space. Just copy any files you want to keep out of the VM before you pull the trigger — that deletion is permanent.