Convert OVA to OVF

A hypervisor or appliance editor may require an OVF package instead of a single OVA file. Converting or extracting it separates the descriptor and virtual disks, making them easier to inspect, edit, verify, or import into software that does not accept OVA directly.

What the OVA format is

OVA, or Open Virtual Appliance, is a single tar archive containing an OVF descriptor, one or more virtual disks such as VMDK files, and optionally a manifest or certificate. VMware vSphere, VMware Workstation, Oracle VirtualBox, and other virtualization platforms create and import OVA appliances. OVA files are commonly used to distribute prebuilt Linux appliances, export virtual machines, and transfer a VM as one file.

What the OVF format is

OVF, or Open Virtualization Format, describes an appliance with an XML descriptor and associated files. An OVF package normally contains the .ovf descriptor, virtual disks, and optional manifest or certificate files. The descriptor records virtual hardware, disk controllers, CPU and memory settings, network devices, firmware requirements, and other deployment metadata.

Separate files make an OVF package easier to inspect, edit, verify, replace, or process with software that expects OVF. It is not normally smaller than OVA: removing the outer TAR archive preserves almost all of the virtual disk data and can increase the apparent size because the files are no longer stored as one archive.

Using VMware OVF Tool

VMware OVF Tool is the most direct desktop option for VMware-compatible appliances. Broadcom distributes it for Windows, Linux, and macOS through its VMware download portal.

1. Install VMware OVF Tool and open Command Prompt, PowerShell, or a terminal.
2. Change to the directory containing the OVA, or use full paths.
3. Run:

ovftool appliance.ova appliance.ovf

The command writes the OVF descriptor and associated disk files beside the destination. Depending on the source and tool version, it may also write a manifest. To use a separate output directory, create it first and specify a destination path such as:

ovftool appliance.ova converted/appliance.ovf

Keep every generated file together and check the command output for warnings. If a manifest is present, its hashes must match the descriptor and disk files before deployment; use an OVF-aware validation or import operation after any manual edit.

Using Oracle VirtualBox

VirtualBox imports the OVA as a VM and then exports that VM as an OVF package. In the interface, choose File → Import Appliance, select the OVA, and complete the import. Then choose File → Export Appliance, select the imported VM, set the output filename to an .ovf path, and export it.

The equivalent commands are:

VBoxManage import appliance.ova --vsys 0 --vmname ConvertedVM
VBoxManage export ConvertedVM --output appliance.ovf

VirtualBox can rewrite hardware settings, disk-controller definitions, network adapters, and appliance metadata during import and export. Use OVF Tool when preserving VMware-oriented configuration is more important than editing the VM through VirtualBox.

Extracting without importing

For an exact file-level unpacking, extract the OVA as a TAR archive instead of importing it:

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

On Windows, 7-Zip can open the OVA as a TAR archive; extract its contents and use the existing .ovf file. This preserves the original descriptor, disks, and manifest, but it does not repair invalid metadata, convert disk formats, or adapt the appliance for another hypervisor. Extraction is therefore unpacking, not a re-export.

Online converters

Online conversion is generally unsuitable for OVA files. They are often several gigabytes, exceed browser upload limits, and can contain credentials, certificates, licensed software, or private data. There is no universally reliable web service for preserving hypervisor-specific OVF metadata; use local VMware OVF Tool, VirtualBox, or a TAR utility instead. If an organization-approved service explicitly supports OVA-to-OVF, confirm its file-size limit, retention policy, encryption, and whether it preserves manifests before uploading an appliance.

Compatibility checks

• Keep referenced names unchanged. The .ovf descriptor refers to disk filenames by relative path. Renaming or separating the disks can make the package fail to import.
• Handle manifests after editing. Changing the descriptor or disks invalidates the corresponding SHA-1 or SHA-256 entries in an .mf file. Remove the manifest only when the target importer permits it, or regenerate it with an OVF-aware tool.
• Expect hardware differences. Firmware mode, CPU compatibility, SCSI or IDE controllers, network adapters, secure boot, VMware Tools, and VirtualBox Guest Additions may need adjustment on the target hypervisor.
• Snapshots may not be preserved. An appliance normally contains a consolidated disk or a disk chain; exporting can omit snapshots or merge their changes into a new disk.
• Check disk format support. The descriptor may reference VMDK, VHD, or another disk format. The destination hypervisor must support that format, or the disk must be converted separately with a compatible utility.