Convert DSK to VHD
Convert compatible raw DSK disk images to VHD with QEMU or VirtualBox.
Make VHD files online
We can't read DSK files yet, so this conversion isn't available. If you can export your work to one of these formats - or others - we'll turn it into VHD:
Want to convert DSK to VHD?
Let us know. We pick the conversions to add next by how many people ask for them.
How to convert dsk to vhd file
- Disk images
- No ratings yet.
Convert a DSK image when a virtual machine or legacy virtualization tool accepts VHD but not the original disk-image file. The conversion can preserve raw sectors, but a floppy image may still need repartitioning or attachment as a floppy device before it will boot as a virtual hard disk.
What the DSK format is
.dsk is an ambiguous extension used for several disk-image formats. It commonly identifies raw floppy images and emulator-specific images for systems such as Amstrad CPC, ZX Spectrum, Apple II, and other vintage computers. A raw DSK contains sectors copied from a disk; platform-specific variants can also contain track layouts, sector geometry, weak sectors, or copy-protection metadata.
DSK files are used by retro-computing emulators, archival software, firmware tools, and collections of bootable floppy disks. The extension does not identify the internal format, so determine the source system and whether the image is raw before converting it.
What the VHD format is
VHD, or Virtual Hard Disk, is Microsoft’s virtual disk-container format. Hyper-V, Virtual PC, VirtualBox, QEMU, and other virtualization tools can use VHD files as virtual hard disks.
A VHD can contain a partition table, filesystem, boot sectors, and ordinary file data, or it can expose the sectors of a converted source image. Classic VHD supports fixed-size and dynamically expanding variants and has a maximum capacity of approximately 2 TB. VHDX is preferable for new large virtual disks when the host supports it, but it is a different format.
How to convert a raw DSK with QEMU
QEMU’s qemu-img is the most direct option when the DSK is a raw sector image. Install QEMU for Windows, macOS, or Linux, keep an untouched backup of the source, and inspect the file:
qemu-img info disk.dsk
If the source is confirmed to be raw, create a dynamically expanding VHD:
qemu-img convert -f raw -O vpc -o subformat=dynamic disk.dsk disk.vhd
Use a fixed-size VHD when the target software requires all sectors to be allocated immediately:
qemu-img convert -f raw -O vpc -o subformat=fixed disk.dsk disk.vhd
The vpc output driver means Microsoft VHD in QEMU. Specify -f raw only after confirming that the file contains ordinary sector data; QEMU cannot decode an emulator-specific DSK merely because its filename ends in .dsk.
Convert a raw DSK with VirtualBox
VirtualBox can write raw disk data to a VHD with VBoxManage:
VBoxManage convertfromraw disk.dsk disk.vhd --format VHD
On Windows, run the command from VirtualBox’s installation directory if VBoxManage is not in PATH. This command treats the input as raw sectors; it does not interpret Amstrad CPC extended DSK structures, copy-protection metadata, or other emulator-specific layouts.
Convert a non-raw DSK first
If the image comes from an emulator with track-level metadata, open it with the matching emulator or a utility designed for that system. Export or write its readable disk contents to a raw image, then convert that raw file with QEMU or VirtualBox. A program may provide a menu such as Disk → Export or Save disk image; the correct operation depends on the source format.
For an original physical floppy, use an imaging tool that understands the disk controller and protection scheme. A normal file copy or generic sector dump can omit weak sectors, deliberately duplicated sectors, and nonstandard layouts required by the original software.
Check the converted image
Inspect the result before attaching it to a guest:
qemu-img info disk.vhd
Test the VHD in the intended virtualization software, preferably with write access disabled during the first test. Do not mount the same writable image simultaneously on the host and in a guest.
Compatibility limits
- The conversion changes the container format, not the filesystem. FAT, CP/M, DOS, and proprietary filesystem data remain unchanged when the source is a compatible raw image.
- A floppy-sized DSK produces a floppy-sized VHD unless you deliberately create or resize a larger virtual disk. The result may have no MBR or GPT partition table and may therefore be rejected as a hard disk.
- A disk designed to boot through floppy firmware may not boot through a virtual hard-disk controller. Attach it as a virtual floppy when supported, or copy its files into a newly partitioned and formatted VHD.
- Extended DSK files, copy-protected images, and nonstandard sector layouts can lose essential information during export to raw sectors. Preserve the original and test the converted file in the source emulator.
- VHD capacity and geometry rules can prevent some oversized or unusual source images from opening in older virtualization software. Use VHDX instead only when the target platform supports it.
Online conversion services
There is no dependable universal online DSK-to-VHD service because .dsk identifies incompatible image structures, while many files contain bootable software or private data. General file-conversion sites may accept a DSK filename but interpret it incorrectly or produce a raw file without preserving track metadata. Local conversion with QEMU or VirtualBox lets you select the source type, choose fixed or dynamic VHD, and retain the original file. Microsoft’s Disk2vhd is not a DSK converter; it captures running physical or logical Windows volumes into VHD files.
Information about file extensions and file types is provided by File-Extensions.org