Convert BIN to VDI

A VDI file is needed when a raw hard-disk image must run as a virtual disk in Oracle VirtualBox. A BIN file that contains a CD/DVD image normally needs a different workflow: convert its data track to ISO and attach it as a virtual optical disc rather than turning it into a VDI.

What BIN means

In the disk-image context, .bin is a raw binary image, not one single standardized format. It commonly stores sector data from a CD, DVD, or hard disk; an optical BIN usually has a matching .cue file that describes tracks, offsets, sector modes, and audio tracks.

The extension alone does not identify the source. Inspect the image with a disk-image utility and keep the CUE file with its BIN. A BIN/CUE pair can contain multiple tracks, while a raw hard-disk BIN normally contains a partition table and filesystem data.

What VDI means

.vdi is Oracle VirtualBox's Virtual Disk Image format. It represents a virtual hard disk that a virtual machine can boot from or use as secondary storage.

• A dynamically allocated VDI initially occupies little host storage and grows as sectors are written.
• A fixed-size VDI allocates its declared virtual capacity immediately and can provide more predictable storage performance.
• VirtualBox supports VDI snapshots and differencing disks, and can attach the image to a VM as a virtual hard drive.

VDI does not make an optical disc image more compatible. A CD image with audio tracks, copy protection, or raw subchannel data generally must remain a BIN/CUE image or use an optical-disc emulator.

Convert a raw hard-disk BIN to VDI

Use this method only when the BIN is a sector-by-sector hard-disk image. Back up the source because a mistaken write operation can destroy the original.

1. Install Oracle VirtualBox and open a terminal or command prompt.
2. Run VBoxManage convertfromraw "input.bin" "output.vdi" --format VDI. On some systems the executable is named VBoxManage.exe.
3. Check the reported source size and the resulting virtual size before attaching the VDI.
4. In VirtualBox, choose Machine → Settings → Storage, add a virtual hard disk, and select output.vdi.

VBoxManage convertfromraw copies the raw sectors; it does not convert the filesystem, repair partitions, or reduce the data inside the image. A dynamic VDI can save host space, but its maximum virtual capacity remains based on the source image.

QEMU can perform the same raw-to-VDI conversion: qemu-img convert -f raw -O vdi "input.bin" "output.vdi". Use qemu-img info "output.vdi" to inspect the result. Do not use a generic file-renaming operation; changing .bin to .vdi does not change the format.

Handle a CD or DVD BIN/CUE image

Do not normally convert an optical BIN directly to VDI. VirtualBox expects an ISO or another supported optical-image format for a virtual CD/DVD drive, while a VDI is treated as a hard disk.

1. Keep the .bin and .cue files together and verify that the paths in the CUE file match the actual filenames.
2. For a data disc, convert the data track with a tool such as bchunk: bchunk input.bin input.cue output. This produces an ISO for a suitable data track and may produce separate files for audio tracks.
3. Attach the resulting .iso in VirtualBox under Machine → Settings → Storage → Optical Drive.

On Windows, AnyBurn and PowerISO can extract or convert many BIN/CUE data discs; on Linux and macOS, bchunk and compatible optical-image tools are common choices. Check the CUE file before conversion when it references multiple BIN files or audio tracks.

Converting a mixed-mode or audio CD to ISO can discard audio tracks, subchannel information, pregaps, or copy-protection behavior. If those features matter, use a CUE-aware optical emulator or preserve the original BIN/CUE pair instead of producing a VDI.

Online conversion and compatibility

Most general online converters do not reliably accept raw BIN images and produce valid VDI files. A service that explicitly lists BIN as a raw disk input and VDI as an output may work for a non-sensitive hard-disk image, but upload limits, unsupported partition layouts, and privacy risks make VBoxManage or qemu-img preferable. Never upload a disk containing credentials, personal data, licensed software, or proprietary files.

After conversion, compare source and destination sizes, inspect the partition table inside the VM, and boot a copy first. If the guest operating system does not boot, the source may be an optical image, may require a different virtual storage controller, or may depend on physical hardware and copy-protection data that VDI cannot reproduce.