Free online OVA to VMDK converter

A virtualization program may require a standalone .vmdk disk instead of a complete .ova appliance. In many cases, conversion means extracting the VMDK already stored inside the OVA; disk conversion is needed only when the target software requires a different VMDK layout.

What the OVA format is

An OVA (Open Virtual Appliance) is a single TAR archive that packages an OVF virtual-machine description, one or more virtual disks, and sometimes a manifest containing file checksums. VMware products, Oracle VirtualBox, and other hypervisors use OVA files to distribute or move preconfigured virtual machines.

An OVA commonly contains a .vmdk disk along with an .ovf configuration file and an optional .mf manifest. The OVF describes memory, processors, virtual hardware, network adapters, disk controllers, firmware, and boot settings; the VMDK contains the guest operating system and its data. An appliance can contain multiple disks, so use the OVF description to identify the correct one.

What the VMDK format is

VMDK (Virtual Machine Disk) is a virtual hard-disk format developed for VMware products and supported by many other virtualization tools. It can be a monolithic file or a small descriptor linked to one or more extent files, and it can use sparse, preallocated, split, or stream-optimized layouts.

A standalone VMDK is useful when a hypervisor, disk utility, backup system, or virtual machine definition needs the guest disk without the OVA’s machine configuration. Extracting an existing VMDK avoids an unnecessary conversion and normally leaves the guest filesystem and data unchanged.

How to convert OVA to VMDK

Extract the existing VMDK

1. Keep a backup of the original OVA and check that the destination has enough free space. The extracted or converted disk can occupy considerably more space than the archive.
2. On Linux or macOS, create a directory and extract the OVA as a TAR archive:

mkdir -p ova-extracted
tar -xf appliance.ova -C ova-extracted
find ova-extracted -type f -iname '*.vmdk'

On current Windows versions, the available tar command can perform the same extraction:

mkdir ova-extracted
tar -xf appliance.ova -C ova-extracted

Alternatively, open the OVA with 7-Zip and extract all files. Keep a VMDK descriptor together with every extent file in the same directory. A small descriptor is not a complete disk; copying it without its referenced extent files makes the virtual disk unusable.

If the archive already contains a usable VMDK, attach that file to the target virtual machine. Do not convert it merely because it was extracted from an OVA. If the OVA contains several disks, inspect the .ovf file before selecting one.

Convert the disk when required

QEMU’s qemu-img works on Windows, Linux, and macOS and can create a new VMDK with a different layout:

qemu-img info ova-extracted/disk.vmdk
qemu-img convert -p -f vmdk -O vmdk ova-extracted/disk.vmdk converted-disk.vmdk

The input path may refer to a VMDK descriptor, provided its extent files remain beside it. To request a VMware stream-optimized VMDK, use a subformat supported by the installed QEMU version:

qemu-img convert -p -f vmdk -O vmdk -o subformat=streamOptimized ova-extracted/disk.vmdk converted-disk.vmdk

VirtualBox can also clone a VMDK or another supported virtual-disk source:

VBoxManage clonemedium disk ova-extracted/disk.vmdk converted-disk.vmdk --format VMDK

When the complete virtual machine configuration is needed, import the original appliance through File → Import Appliance in VirtualBox or the equivalent import command in the target hypervisor. For a standalone disk, direct extraction is usually the shortest method. Users can also convert the file on 101convert.com for free without installing software.

Compatibility and limitations

Extracting or converting a disk does not transfer the OVA’s CPU, memory, network, controller, firmware, or boot configuration. Recreate those settings in the destination virtual machine.

Check the disk-controller and firmware settings before starting the guest. An operating system installed for IDE, SATA, SCSI, or NVMe may fail to boot when attached through a different controller, and a BIOS installation may not boot when the new machine uses UEFI, or the reverse.

An OVA manifest records checksums for the files in the original package. Extraction does not damage the original archive, but modifying files and repackaging them without updating the manifest makes the package checksum-invalid. This normally does not prevent use of the extracted disk.

Virtual disks may be sparse inside the OVA and expand during conversion. Check the result with qemu-img info, retain all descriptor and extent files, and test a copy before running filesystem repair or making operating-system changes. A successful container conversion does not repair a corrupted guest filesystem or guarantee compatibility with every hypervisor version.