An OVF export creates a portable copy of a virtual machine that can be imported into another VMware environment or other compatible hypervisors. In VMware, this can be done either through the vSphere Client or from the command line with VMware OVF Tool.

In most cases, exporting as OVA is easier because it produces one file. Exporting as OVF produces several files and is better if the package needs to be inspected or edited.

Before starting

Check the following first:

• The virtual machine should ideally be powered off before export.
• This gives the cleanest and most consistent result.
• A powered-on export may work, but it is not guaranteed to be application-consistent.
• Make sure there is enough free space on the computer performing the export.
• The export is downloaded to the local machine running the browser or the command.
• Remove or consolidate old snapshots if possible.
• Exports from VMs with snapshots can be slower or behave unexpectedly.
• Disconnect unneeded removable media such as mounted ISOs.
• Ensure the VMware account has permission to view and export the VM.
• Be aware of unsupported features that may block export, such as:
• encrypted virtual machines
• vTPM
• some pass-through devices
• linked clone or special disk configurations

OVF and OVA formats

VMware can export in two common formats:

• OVF
• Produces multiple files, typically:
• VMName.ovf
• one or more VMName-disk*.vmdk
• optionally VMName.mf
• OVA
• Produces a single VMName.ova file
• Usually easier to copy, upload and archive

Exporting from the vSphere Client

The exact menu wording varies slightly between VMware versions, but the process is broadly the same.

Using vCenter in the vSphere Client

   https://<vcenter-server>/ui

1. Open the vSphere Client in a browser:
2. Sign in.
3. Locate the virtual machine in:

• Hosts and Clusters, or
• VMs and Templates

1. Shut down the guest operating system cleanly, then wait until the VM is powered off.
2. Right-click the VM, or use the Actions menu.
3. Select the export option. Depending on version, this is usually one of:

• Export OVF Template
• Template > Export OVF Template
• All Actions > Export OVF Template

1. In the export dialogue:

• Enter a name for the export.
• Choose the format:
• OVF for multiple files
• OVA for a single file
• If there is a manifest option, enable it if integrity checking is required.

1. Choose a local destination on the computer running the browser.
2. Start the export and wait for all files to download.

Important browser behaviour

If exporting as OVF, the browser usually downloads multiple files. This can cause problems if the browser blocks repeated downloads.

If the browser prompts or blocks downloads:

• allow multiple downloads for the vSphere site
• disable any download restrictions temporarily
• consider exporting as OVA instead, to generate a single file

Using the ESXi Host Client directly

If connecting directly to an ESXi host rather than vCenter:

   https://<esxi-host>/ui

1. Open:
2. Sign in.
3. Locate the VM.
4. Power it off cleanly.
5. Use the VM action menu and select the export option.
6. Choose OVF or OVA, depending on the version and available options.
7. Save the exported file or files locally.

On some ESXi versions, the direct host client has fewer export options than vCenter. If the GUI option is missing or limited, use OVF Tool from the command line.

Exporting from the command line with VMware OVF Tool

OVF Tool is VMware’s command-line utility for exporting and importing OVF and OVA packages.

Install OVF Tool

Install VMware OVF Tool on the machine that will perform the export.

Typical installation locations:

  C:\Program Files\VMware\VMware OVF Tool\

  /usr/bin/ovftool

• Windows:
• Linux:

or

  /usr/local/bin/ovftool

  /Applications/VMware OVF Tool/

• macOS:

Confirm it is available.

On Linux or macOS:

ovftool --version

On Windows PowerShell:

& "C:\Program Files\VMware\VMware OVF Tool\ovftool.exe" --version

Basic command structure

The syntax is:

ovftool "<source>" "<destination>"

For VMware inventory sources, the source is normally a vi:// URI.

Export a VM from vCenter to OVF

Linux or macOS example:

ovftool \
  "vi://username@vcenter.example.com/Datacenter/vm/Folder/VMName" \
  "/exports/VMName/VMName.ovf"

Windows PowerShell example:

& "C:\Program Files\VMware\VMware OVF Tool\ovftool.exe" `
  "vi://username@vcenter.example.com/Datacenter/vm/Folder/VMName" `
  "D:\Exports\VMName\VMName.ovf"

Notes:

• The command prompts for the password if it is not embedded in the URI.
• The destination path is local to the system running ovftool.
• If the target ends with .ovf, the result is an OVF package with multiple files.

Export a VM from vCenter to OVA

Linux or macOS:

ovftool \
  "vi://username@vcenter.example.com/Datacenter/vm/Folder/VMName" \
  "/exports/VMName.ova"

Windows PowerShell:

& "C:\Program Files\VMware\VMware OVF Tool\ovftool.exe" `
  "vi://username@vcenter.example.com/Datacenter/vm/Folder/VMName" `
  "D:\Exports\VMName.ova"

If the target ends with .ova, ovftool creates a single OVA file.

Export directly from a standalone ESXi host

Linux or macOS:

ovftool \
  "vi://root@esxi01.example.com/VMName" \
  "/exports/VMName/VMName.ovf"

Windows PowerShell:

& "C:\Program Files\VMware\VMware OVF Tool\ovftool.exe" `
  "vi://root@esxi01.example.com/VMName" `
  "D:\Exports\VMName\VMName.ovf"

When SSL certificate warnings appear

Many VMware systems use self-signed certificates. If ovftool fails certificate validation, add --noSSLVerify.

Example:

ovftool --noSSLVerify \
  "vi://username@vcenter.example.com/Datacenter/vm/Folder/VMName" \
  "/exports/VMName/VMName.ovf"

Windows PowerShell:

& "C:\Program Files\VMware\VMware OVF Tool\ovftool.exe" `
  --noSSLVerify `
  "vi://username@vcenter.example.com/Datacenter/vm/Folder/VMName" `
  "D:\Exports\VMName\VMName.ovf"

Use this only where appropriate, because it skips certificate verification.

Useful logging for troubleshooting

If an export fails, enable verbose logging.

Linux or macOS:

ovftool --X:logFile=ovftool.log --X:logLevel=verbose \
  "vi://username@vcenter.example.com/Datacenter/vm/Folder/VMName" \
  "/exports/VMName/VMName.ovf"

Windows PowerShell:

& "C:\Program Files\VMware\VMware OVF Tool\ovftool.exe" `
  --X:logFile=ovftool.log `
  --X:logLevel=verbose `
  "vi://username@vcenter.example.com/Datacenter/vm/Folder/VMName" `
  "D:\Exports\VMName\VMName.ovf"

Understanding the source path

When exporting from vCenter, the VM path normally follows this pattern:

vi://<username>@<vcenter>/<datacenter>/vm/<folder>/<vm-name>

Examples:

vi://backupuser@vcsa01.example.com/LondonDC/vm/Production/App01

vi://backupuser@vcsa01.example.com/LondonDC/vm/App01

When exporting from a standalone ESXi host, the path is usually simpler:

vi://root@esxi01.example.com/App01

If the VM name or folder contains spaces, keep the whole source string in quotes.

What files to expect after export

For an OVF export, the output folder typically contains:

• VMName.ovf

The descriptor file that defines the VM hardware and settings.

• VMName-disk1.vmdk and possibly more

The virtual disk files.

• VMName.mf

Optional manifest file containing checksums.

For an OVA export, there is usually just:

• VMName.ova

Common issues

Export option missing in the GUI

Possible causes:

• insufficient permissions
• connected to a host or interface that does not expose the option
• VM configuration not supported for OVF export

Use OVF Tool if the GUI option is unavailable.

Browser starts only one download

This usually happens with OVF exports because several files are generated. Either:

• allow multiple downloads in the browser, or
• export as OVA instead

Export fails due to certificate errors

Use:

--noSSLVerify

only if the environment uses a trusted self-signed or otherwise expected certificate.

Export fails on VMs with special devices

Check for and remove or reconfigure:

• vTPM
• USB pass-through
• PCI pass-through
• mounted ISOs
• encryption

Export is very slow

Common reasons:

• large thin-provisioned disks with high used space
• slow link between the export machine and VMware host
• snapshots
• export being saved to slow local storage

Recommended approach

For most administrators:

• use the vSphere Client when performing a one-off export
• use OVF Tool when:
• exporting regularly
• scripting backups or migrations
• exporting from environments where the browser method is unreliable
• working around missing GUI options

A practical default is:

• power off the VM
• export as OVA for easiest handling
• use OVF only when separate descriptor and disk files are specifically required