Free online VHD to OVF converter

A VHD usually needs conversion when a Hyper-V or Virtual PC machine must be imported into software or an appliance workflow that accepts OVF. The process creates a virtual-machine descriptor and usually converts the disk to VMDK; changing the filename extension does not perform the conversion.

What the VHD format is

VHD, or Virtual Hard Disk, is a sector-level virtual disk format used by Microsoft Hyper-V, older Virtual PC installations, Windows disk tools, and some backup or migration products. The file can contain partitions and a guest file system, but it does not contain the VM's CPU, memory, firmware, network, or other virtual-hardware settings.

VHD files may be fixed-size, dynamically expanding, or differencing. A differencing disk depends on its parent, so merge the chain into a standalone disk or provide every required parent before conversion. Hyper-V checkpoint disks are often .avhdx rather than VHD and require a different workflow.

What the OVF format is

OVF, the Open Virtualization Format, describes a virtual appliance in an XML .ovf descriptor. An export normally includes that descriptor, one or more virtual disks such as .vmdk, and optionally a manifest such as .mf containing file hashes. The descriptor records virtual hardware, disk controllers, disk attachments, firmware, network adapters, and deployment settings.

OVF can be imported by compatible versions of VMware products, VirtualBox, and some appliance or cloud platforms, but compatibility is not universal: vendors can support different OVF versions, virtual hardware, disk controllers, and guest operating systems. OVA is a single TAR archive containing the OVF descriptor, disks, and optional manifest; choose it when the recipient requires one file.

Convert with VirtualBox

VirtualBox is the simplest general-purpose desktop method because it can attach a VHD to a new VM and export that VM as OVF. Install a current version from Oracle, and work on a copy of the source disk.

1. Shut down the source VM completely. Do not convert a disk belonging to a running VM or a saved state. Merge any differencing disks first.
2. In VirtualBox, select New, choose the guest operating-system type and version, and assign memory and processors suitable for the source VM.
3. Under the virtual hard-disk step, choose Use an existing virtual hard disk file and select the .vhd. If the wizard does not offer that option, create the VM without a disk and attach it under Settings → Storage.
4. Under Settings → System and Settings → Storage, match the source's BIOS or UEFI mode, boot-disk order, controller type, and approximate chipset configuration. Enable EFI only when the original guest used UEFI.
5. Start the VM and verify that the guest boots and its applications work. Shut it down again before exporting; do not treat a failed first boot as evidence that changing the file extension will help.
6. Select File → Export Appliance, select the VM, choose an available OVF format, set an output path ending in .ovf, and start the export. VirtualBox normally writes an OVF descriptor and a converted .vmdk, with a manifest in some configurations.

The equivalent command-line sequence is:

VBoxManage createvm --name "Converted VM" --register
VBoxManage modifyvm "Converted VM" --memory 4096 --cpus 2 --firmware bios
VBoxManage storagectl "Converted VM" --name SATA --add sata --controller IntelAhci
VBoxManage storageattach "Converted VM" --storagectl SATA --port 0 --device 0 --type hdd --medium "/path/source.vhd"
VBoxManage export "Converted VM" --output "/path/converted.ovf"

Use --firmware efi when the source guest requires UEFI, and adjust the controller, memory, processors, and disk path to the source VM. The command exports the VM definition as well as the attached disk; it does not preserve every vendor-specific setting from Hyper-V.

Other desktop workflows

For a disk-only conversion, QEMU's qemu-img can convert VHD to VMDK:

qemu-img convert -f vpc -O vmdk source.vhd converted.vmdk

Afterward, create a VM in the destination hypervisor, attach the VMDK, configure its firmware and hardware, and export that VM as OVF. qemu-img alone does not create an OVF descriptor and cannot preserve the original VM configuration.

VMware OVF Tool exports an existing VMware VM, for example from a .vmx file, but it is not a VHD-to-OVF converter. A VMware-specific workflow therefore requires a supported VHD import or disk conversion first, followed by an export with OVF Tool or the VMware product's appliance-export command.

Online services are not suitable for a complete conversion because they generally convert only the disk and cannot reliably reconstruct firmware, controllers, boot order, or network configuration. Some services advertise VHD-to-VMDK conversion, but uploading a disk can disclose credentials and personal data; use one only for a non-sensitive disk when the destination needs a disk image rather than a complete OVF appliance.

Compatibility checks

Conversion does not guarantee a successful boot. Windows or Linux may detect a different storage controller, virtual network adapter, BIOS or UEFI implementation, disk identifier, or machine identity. Windows may also require reactivation. Match BIOS versus UEFI, GPT versus MBR, controller type, boot order, and disk capacity before export; install destination-specific guest tools only after the guest is running.

Validate the exported appliance by importing it into the target hypervisor and testing boot, networking, storage, time synchronization, applications, and licensing. Keep the original VHD until those tests pass.

A dynamically expanding VHD may become a differently allocated VMDK, so the exported files can consume more space. OVF does not compress its disks. Compress the complete OVF set only after confirming that the recipient supports the chosen archive, or export as OVA when a single file is required. Preserve the manifest when present; modifying an OVF or disk afterward can invalidate its hashes.