Free online IMG to OVA converter

What the IMG format is

In virtualization, IMG usually means a raw virtual disk image: a sector-by-sector representation of a disk, including its partition table, boot sector, file systems, and operating-system data. Linux imaging tools, embedded-system platforms, hypervisors, backup utilities, and disk-cloning software commonly create files with this extension.

A raw IMG file does not normally contain virtual hardware settings such as memory, CPU count, network adapters, firmware mode, or appliance metadata. Its size can also equal the full provisioned disk capacity rather than the amount of stored data.

What the OVA format is

An OVA is a single-file Open Virtualization Appliance package. It is usually a TAR archive containing an OVF hardware descriptor, one or more virtual disks such as VMDK files, and sometimes a manifest with SHA-1 or SHA-256 checksums.

OVA files are intended for import into virtualization products such as Oracle VirtualBox, VMware products, and other OVF-compatible platforms. They package the disk with virtual-machine configuration, making distribution, archiving, and appliance deployment simpler than transferring a raw disk alone.

How to convert IMG to OVA

Using VirtualBox

1. Install Oracle VM VirtualBox and keep the source file unchanged as a backup.
2. Convert the raw image to a VirtualBox disk with:

VBoxManage convertfromraw disk.img disk.vdi --format VDI

Replace disk.img with the actual source path. If the IMG is a complete disk image, preserve its partition table; do not mount and copy only one partition.

3. Create a virtual machine in VirtualBox with an appropriate operating-system type, memory size, CPU count, firmware mode, and network adapter.
4. Choose Settings → Storage, add a virtual hard disk, and select disk.vdi as the existing disk.
5. Start the machine and verify that the operating system boots, the expected partitions are present, and network or storage drivers work.
6. Shut down the guest, then choose File → Export Appliance. Select the virtual machine, choose an output path ending in .ova, review the appliance settings, and start the export.

The command-line equivalent is:

VBoxManage export "Imported IMG" --output appliance.ova

For repeatable automation, the virtual machine can be created and attached with commands such as:

VBoxManage createvm --name "Imported IMG" --register
VBoxManage storagectl "Imported IMG" --name SATA --add sata --controller IntelAhci
VBoxManage storageattach "Imported IMG" --storagectl SATA --port 0 --device 0 --type hdd --medium disk.vdi
VBoxManage export "Imported IMG" --output appliance.ova

The VM must have suitable memory, firmware, CPU, and boot settings before export; those values are not recoverable from a raw IMG file.

Using QEMU and VirtualBox

QEMU can convert the raw image directly to VMDK:

qemu-img convert -f raw -O vmdk disk.img disk.vmdk

Attach disk.vmdk to a newly created VirtualBox VM, test it, and use File → Export Appliance to create the OVA. This route is useful when the destination hypervisor or workflow already uses VMDK.

Converting without installed software

You can use the free converter on 101convert.com without installing software. Uploading a virtual disk may expose operating-system data, credentials, or other sensitive files, so use a local conversion for confidential images.

Compatibility and limitations

The conversion changes the disk container and adds appliance metadata; it does not automatically repair the guest operating system. A BIOS-installed guest may fail when exported with EFI enabled, and an EFI-installed guest may fail with legacy BIOS selected. Match the source boot mode and verify the virtual disk controller type.

Raw images can contain unused sectors, so the generated VDI or VMDK and the OVA may be large. Remove unnecessary files inside the guest and compact the converted disk before export when supported; this does not reduce the guest's provisioned capacity unless the disk is resized separately.

An OVA is commonly a TAR package rather than a compressed archive, so compressing it with ZIP or gzip can reduce transfer size but may prevent direct appliance import. After conversion, test the OVA on the intended hypervisor and retain the original IMG until boot, partition, and data checks have passed.