Convert QCOW2 to VDI

Turn QCOW2 archives into VDI. The whole disk, partitions and file systems included, block for block as a dynamically allocated VDI for VirtualBox.

Converted in an isolated sandbox on our serversDeleted after 24 hours

Drop QCOW2 files on the dialor turn it to pick what to do

A VirtualBox disk from a QEMU disk.The whole disk is copied block for block into one VDI file.

  1. What you get

    A single VDI file made for VirtualBox. It is a dynamically allocated VDI.

    The whole disk comes across, partitions and file systems included, block for block.

  2. What it leaves behind

    Internal snapshots are left out. Only the disk as it stands is written to the VDI.

    Some QCOW2 images are not supported. These are images that sit on a backing file, images that keep their data in a separate file, and encrypted images.

  3. Going the other way

    To turn a VDI back into a QCOW2 disk, use VDI to QCOW2.

QCOW2 and VDI.What each format is.

The formats

From · QCOW2

QEMU Disk

QEMU and KVM copy-on-write disk images.

Extensions
.qcow2 .qcow
MIME type
application/x-qemu-disk
Kind
Archives
To · VDI

VirtualBox Disk

VirtualBox virtual disk images.

Extensions
.vdi
MIME type
application/x-virtualbox-vdi
Kind
Archives

In your code.The same QCOW2 to VDI conversion through the API, for your app or your agent.

terminal
$ cv convert archive.qcow2 archive.vdi
$ cv convert archive.qcow2 archive.vdi

Questions.What people ask about QCOW2 to VDI.

01OF 04

Yes. The whole disk is copied block for block, so the partitions and file systems come across with it.

No. Internal snapshots are left out of the VDI.

No. Encrypted images are not supported. Images that sit on a backing file or keep their data in a separate file are not supported either.

It is a dynamically allocated VDI.

More conversions.Other ways in and out of QCOW2 and VDI.