VMware vSphere does not support shrinking a virtual disk (VMDK) in-place. Once a disk is expanded via the vSphere Client or CLI, the provisioned size is updated in the VM configuration (.vmx) and descriptor files. This action cannot be reverted directly. This guide provides supported workarounds to reclaim space or correct the provisioned size of a VMDK.
This is a design limitation. The ESXi hypervisor is not aware of the Guest OS filesystem layout and cannot safely truncate a disk without risking data corruption
Before proceeding, ensure a full backup of the virtual machine is available.
Method 1: Using VMware vCenter Converter Standalone
Method 2: Manual Data Migration
rsync (Linux) or Robocopy (Windows).Note: If the virtual disk is thin-provisioned and the additional capacity was never initialized or partitioned within the Guest OS, the expansion has no impact on physical datastore consumption.
Growing, thinning, and shrinking virtual disks in ESXi
VMware vCenter Converter Standalone 9.0 Release Notes
Product Interoperability Matrix- VMware standalone converter