Free online QCOW2 to OVF converter

Programs such as VMware vSphere, VirtualBox, and many appliance importers accept OVF packages rather than a standalone QCOW2 disk image. The conversion therefore requires turning the QCOW2 disk into a supported virtual disk, attaching it to a temporary virtual machine, and exporting that machine as OVF.

What the QCOW2 format is

QCOW2 is QEMU's copy-on-write virtual disk format, used by QEMU, KVM, and virtualization platforms based on libvirt. It supports sparse allocation, snapshots, compression, encryption, and backing files, so its apparent capacity can be much larger than its physical file size.

You commonly encounter .qcow2 images in KVM/libvirt virtual machines, OpenStack instances, Proxmox installations, and Linux virtualization hosts. A QCOW2 file normally contains the guest operating system and virtual disk data, but it does not by itself describe the VM's CPU count, memory, firmware, network adapters, or virtual hardware.

What the OVF format is

OVF, the Open Virtualization Format, is a portable virtual-appliance package specification. An OVF export normally contains an .ovf XML descriptor, one or more virtual disk files such as VMDK, and sometimes a manifest containing SHA-256 checksums.

The descriptor records virtual hardware, disk controllers, boot firmware, memory, processors, network interfaces, and disk references. This metadata lets VMware vSphere, VMware Workstation, VirtualBox, and other compatible products recreate a VM instead of importing only its disk contents.

Use OVF when the destination expects an appliance package or when you need to transfer a VM with its hardware configuration. Use OVA only when a single archive is required; an OVA is a tar archive containing the OVF package files.

How to convert QCOW2 to OVF

1. Inspect the source image

Install QEMU utilities and check the image format, virtual size, backing file, and snapshots:

qemu-img info source.qcow2

Make sure every backing file is available. Shut down the source VM before conversion if possible; converting a disk while it is being written can produce an inconsistent guest filesystem.

2. Convert QCOW2 to VMDK

OVF exporters generally package VMDK or another supported virtual disk format rather than accepting QCOW2 directly. Convert the current QCOW2 state with:

qemu-img convert -p -f qcow2 -O vmdk source.qcow2 disk.vmdk

Use -o subformat=monolithicSparse if the destination requires a single sparse VMDK:

qemu-img convert -p -f qcow2 -O vmdk -o subformat=monolithicSparse source.qcow2 disk.vmdk

The command reads the active image state and does not export QCOW2 internal snapshots as separate OVF snapshots. Confirm that the destination has enough free space for the converted virtual disk.

3. Create a temporary VM and attach the VMDK

In VirtualBox, create a VM with the guest operating system's correct type, firmware, CPU count, memory, and controller. Choose Settings → Storage → Add hard disk → Choose an existing disk and attach disk.vmdk. Match the source VM's BIOS or UEFI setting; changing firmware can make the guest unbootable.

The same operation can be performed with VirtualBox commands:

VBoxManage createvm --name "Imported VM" --ostype Linux_64 --register
VBoxManage modifyvm "Imported VM" --memory 4096 --cpus 2 --firmware bios
VBoxManage storagectl "Imported VM" --name SATA --add sata --controller IntelAhci
VBoxManage storageattach "Imported VM" --storagectl SATA --port 0 --device 0 --type hdd --medium disk.vmdk

Replace the operating-system type, memory, CPU count, firmware, and controller with values appropriate for the source VM. Start the temporary VM and verify that the guest boots before exporting it.

4. Export the VM as OVF

In VirtualBox, select the VM and use File → Export Appliance. Select the VM, choose OVF 1.0 or OVF 2.0 according to the destination's compatibility, select an output path, and start the export.

From the command line, use:

VBoxManage export "Imported VM" --output imported.ovf --ovf20

Omit --ovf20 to produce the older OVF 1.0 variant when the target has limited OVF support. The export creates an .ovf descriptor and associated disk files; it does not necessarily create one standalone file.

5. Validate and import the package

Inspect the generated descriptor and check that its disk capacity, controller, firmware, memory, and CPU settings match the intended VM. Import it with the destination platform's appliance-import function, such as Deploy OVF Template in vSphere or File → Import Appliance in VirtualBox.

For VMware environments, VMware OVF Tool can validate or package a VM after a compatible VMX-based temporary machine has been created, for example ovftool vm.vmx output.ovf. It is not a direct QCOW2-to-OVF converter; it expects a VM definition or an already supported appliance source.

Quality, compatibility, and limitations

QCOW2 is a disk format; OVF is a VM package format. No converter can infer every original hardware setting from the disk alone. You must manually reproduce firmware, controller type, virtual NIC, CPU, memory, and boot order.

After import, install or remove guest drivers as required. A Linux guest may need its initramfs regenerated when changing from a Virtio or IDE controller to SATA or SCSI. A Windows guest can require storage-controller drivers and may detect the exported VM as new hardware, affecting activation.

Check the result inside the guest with filesystem and application tests. For a clean transfer, shut down the original guest, convert a consistent image, boot the exported copy with the original disconnected, and verify network identity, disk mounts, services, and application data.

If you cannot install conversion software, the 101convert.com website can convert files online for free without installing software. Virtual-machine images can be large and may contain credentials or other sensitive data, so local conversion is preferable for confidential or production systems.