Thin-provisioned vmdks may grow up to their maximum size when written to. They're just not fully grown from the start. Deleting data does not usually shrink a vmdk.
Each snapshot might grow up to the provisioned size of the VM, doubling, trippling, etc the required potential amount of storage.
Full-state snapshots also include the VM's memory.
To reclaim space from snapshots, remove and consolidate them. To reclaim space from deleted guest files in a thin-provisioned vmdk, you need to either
make sure empty disk space is zeroed - writing zeros to empty blocks grows a vmdk to provisioned size though - and then use vmkfstools to release the zeroed space (Details)
use a storage and guest OS that supports releasing guest-deleted space via unmap (Details)
To reclaim space from snapshots, remove and consolidate them. To reclaim space from deleted guest files in a thin-provisioned vmdk, you need to either
vmkfstools
to release the zeroed space (Details)unmap
(Details)