VMware → Proxmox
VMDKQCOW2
VMDK is VMware’s disk. QCOW2 is what Proxmox and qemu expect. Search results still tell you to install qemu-img and wrestle with a descriptor plus a -flat file. This page is the product path: upload the VMDK, convert in isolation, download a QCOW2 you can import.
No account on the public uploader. Guest jobs stay within five conversions and 250 MB per day. Business rates start at €0.80/GB for OST → PST.
Describe what you want, then continue to convert.
A virtual disk is not a JPEG. It can be sparse, split, tens of gigabytes, or a tiny descriptor that points at a sibling -flat.vmdk. Proxmox importdisk wants a disk image it can attach — usually QCOW2 or RAW — not a VMware chain.
This conversion is that hand-off: one VMDK in, one QCOW2 out. It does not rebuild NICs, cloud-init or the VMID. After download you still import the disk in Proxmox.
The worker identifies the file as a VMware disk, converts it with the hypervisor toolchain in an isolated environment, then validates that the result is a readable QCOW2 rather than a truncated blob.
Encrypted, empty or unreadable VMDKs fail with a diagnostic. A failed validation does not produce a silent half-disk.
Guest conversion is one file and follows the published Free limits. Datastore exports, folders of VMs, or disks that exceed those limits belong in a Business workspace.
Upload the data disk when it is a single self-contained VMDK. Split descriptor-plus-flat sets often fail as a guest upload because the descriptor is not the payload. Bundle them or use Business for messy VMware exports.
Yes. This page exists when you want isolation, a validation check, and no hypervisor toolkit on the laptop that holds the disk.
No. We convert the disk format. You still import and attach it in Proxmox.
