Free online OVA to VHDX converter

Hyper-V uses VHDX for virtual hard disks, while many appliances and exported virtual machines arrive as OVA packages. Converting the disk inside the OVA lets you attach it to a Hyper-V virtual machine without reinstalling the guest operating system.

What the OVA format is

OVA is a single TAR archive containing an OVF virtual-machine descriptor, one or more virtual disks, and sometimes manifest or certificate files. VMware Workstation, VMware vSphere, VirtualBox, and appliance vendors commonly create OVA exports.

The virtual disk is usually a VMDK file. The OVF descriptor stores the original VM's CPU, memory, firmware, controller, network, and disk-attachment settings, but converting the disk does not automatically recreate those settings.

What the VHDX format is

VHDX is Microsoft's virtual hard-disk format used by Hyper-V and supported by current Windows virtualization tools. It supports virtual disks up to 64 TB, larger block-sector options, resiliency against power failures, and metadata useful for modern virtual machines.

Use VHDX when the destination is Hyper-V, Windows Server virtualization, or software that specifically requires Microsoft's format. A dynamically expanding VHDX saves host storage initially; a fixed VHDX allocates its full capacity and can provide more predictable I/O.

How to actually convert OVA to VHDX

Using qemu-img

QEMU's qemu-img is the most direct method because it converts the VMDK contained in the package without booting the guest.

1. Make a working directory and extract the OVA with a TAR utility. On Linux or macOS, run mkdir ova-work && tar -xf appliance.ova -C ova-work. On Windows, open the OVA with 7-Zip and extract its contents.
2. Identify the virtual disk referenced by the OVF file. Do not convert the OVF descriptor, manifest, or certificate. An appliance can contain multiple VMDK files, and each disk requires a separate conversion.
3. Check the source disk with qemu-img info source-disk.vmdk.
4. Convert it to a dynamically expanding VHDX with qemu-img convert -p -f vmdk -O vhdx -o subformat=dynamic source-disk.vmdk destination-disk.vhdx. Use subformat=fixed instead if the destination requires a fixed-size disk.
5. Validate the result with qemu-img check destination-disk.vhdx and qemu-img info destination-disk.vhdx.

Install QEMU from a trusted desktop package or distribution repository, then run the command from the directory containing the extracted files. Preserve the original OVA until the converted VM has booted and its data has been checked.

Attach the disk in Hyper-V

1. Open Hyper-V Manager and select New → Virtual Machine.
2. Choose the same generation expected by the guest. Generation 1 uses legacy BIOS and IDE compatibility; Generation 2 uses UEFI and SCSI. A UEFI-based Linux or Windows guest generally requires Generation 2.
3. At the virtual-hard-disk step, select Attach a virtual hard disk later, finish creation, then open Settings → SCSI Controller → Hard Drive → Add and select the VHDX. For a Generation 1 VM, attach it through the appropriate IDE controller.
4. Recreate the OVA's CPU, memory, firmware, boot order, network adapter, and additional disk settings from the OVF descriptor. Enable Secure Boot only when the guest and its bootloader support it.

Using an online converter

For a browser-based conversion without installing software, 101convert.com provides a free online conversion option. Uploading a complete OVA can expose embedded operating-system data, credentials, licenses, or proprietary files; use local conversion for confidential or production images.

Quality, compatibility, and limitations

The conversion changes the disk container, not the guest's virtual hardware drivers or boot configuration. VMware Tools, VirtualBox Guest Additions, static network naming, and storage-controller drivers may need removal or adjustment after migration.

Power off the source VM before exporting or converting. A disk copied while the guest is running can contain inconsistent filesystem or application state.

After the first boot, install Hyper-V integration components supplied by the guest operating system, confirm the correct boot mode, renew or reconfigure network settings, and check activation. If the OVA has several disks, keep their original attachment order; changing it can alter drive letters or mount points.