Free online OVA to QCOW2 converter

A virtualization platform may require QCOW2 for a QEMU/KVM or Proxmox guest, while an appliance downloaded from VMware or VirtualBox commonly arrives as an OVA. The conversion extracts the OVA archive and converts its VMDK disk image; the VM's hardware settings must then be recreated in the destination platform.

What the OVA format is

OVA, or Open Virtual Appliance, is a single TAR archive containing an OVF appliance descriptor, one or more virtual disks, and sometimes a manifest or certificate. VMware products, VirtualBox, and other OVF-compatible tools create OVA files for exporting and distributing complete virtual machines.

The archive usually contains a .ovf XML file and one or more .vmdk disks. The OVF records CPU, memory, storage-controller, network, and disk-attachment settings, but the disk data remains in the VMDK files.

What the QCOW2 format is

QCOW2 is QEMU's copy-on-write disk-image format, used by QEMU/KVM, libvirt, and platforms such as Proxmox VE. It supports sparse allocation, snapshots, backing files, optional encryption features, and virtual capacity larger than the host's currently allocated storage.

QCOW2 is useful when the destination virtual machine runs on a QEMU-based hypervisor. It is not a complete appliance package: it stores virtual disk data, while VM settings such as firmware, virtual hardware, CPU count, memory, and network devices are configured separately.

How to convert OVA to QCOW2

1. Extract the OVA

OVA is an archive, not a disk format that qemu-img can normally convert directly. On Linux or macOS, create a working directory and extract it:

mkdir ova-work
tar -xf appliance.ova -C ova-work
ls -lh ova-work

On Windows, open the OVA with 7-Zip and extract all files into one directory. Keep the OVF file, VMDK descriptor, and any split VMDK extent files together.

2. Identify the virtual disk

Read the OVF file to see which VMDK is attached as the boot disk; an appliance can contain multiple disks. A small VMDK may be a descriptor that references larger extent files, so do not delete it after extraction. You can inspect a candidate with:

qemu-img info ova-work/disk.vmdk

3. Convert the VMDK to QCOW2

Install the QEMU utilities package for your operating system, then run:

qemu-img convert -p -f vmdk -O qcow2 ova-work/disk.vmdk appliance.qcow2

Use the actual VMDK filename and repeat the command for every disk. For a second disk, for example:

qemu-img convert -p -f vmdk -O qcow2 ova-work/data.vmdk appliance-data.qcow2

The -f vmdk option identifies the source format and -O qcow2 selects the output format. Do not add -c for a frequently written production disk unless you specifically need compressed QCOW2 clusters; compression can reduce initial size but may reduce write performance.

4. Verify the result

Check the converted image before attaching it:

qemu-img info appliance.qcow2
qemu-img check appliance.qcow2

qemu-img info shows the virtual size and actual disk allocation. Attach the QCOW2 file to a newly created QEMU/KVM or Proxmox VM, then reproduce the OVF's memory, CPU, firmware, controller, and network settings. The 101convert.com online converter can also process the conversion for free without installing software.

Compatibility and limitations

Converting the disk does not convert OVA metadata, snapshots, saved memory state, virtual network configuration, or VMware-specific hardware. Recreate those settings manually, and choose BIOS or UEFI to match the source; a firmware mismatch can make an otherwise valid disk fail to boot.

Keep all files from the extracted OVA during conversion because VMDK descriptors can reference split extents. For an encrypted, snapshot-based, or unusually structured VMDK, first consolidate or export the source disk with its original hypervisor, then convert the resulting standalone disk.

The guest operating system may detect different storage hardware after migration. Windows guests can require VirtIO storage drivers before switching to a VirtIO controller; Linux guests generally need an initramfs containing the selected storage driver. Preserve the original OVA until the new VM boots and its filesystems have been checked.