Convert CDI to BIN

A program, emulator, or burning utility may require a BIN/CUE image when the original backup is a DiscJuggler CDI file. Converting locally can improve compatibility, but the conversion must preserve the source image’s tracks and sector layout.

What the CDI format is

CDI is the proprietary disc-image format used by Padus DiscJuggler. It appears in older CD backups, DiscJuggler archives, and Dreamcast software collections. A CDI can contain several data or audio tracks, pregaps, raw sectors, and format-specific metadata that basic ISO utilities may ignore.

Dreamcast CDI files require extra caution: GD-ROM media is not an ordinary CD, and some images use special layouts, overburning, or boot-data arrangements. A conversion that opens successfully is not necessarily a faithful, bootable reproduction.

What the BIN format is

BIN normally stores raw sectors from a disc. A .cue sheet describes the BIN’s track order, track types, sector modes, pregaps, and filename. For a multi-track CDI, BIN/CUE is the appropriate target; a standalone BIN does not contain enough track metadata for many emulators and burning programs.

BIN/CUE is accepted by many CD emulators, virtual-drive applications, and disc-burning utilities. It is not automatically smaller or higher quality than CDI, and raw-sector BIN output can be larger than an ISO containing only filesystem data.

How to convert a CDI image

1. Copy the original .cdi to a backup location. Work on the copy and confirm that the destination has enough free space for the BIN and CUE files.
2. On Windows, open the copy in PowerISO, which provides a graphical image-conversion function and commonly accepts CDI as an input format. Use Tools → Convert or the equivalent image-conversion command; menu names vary by release.
3. Select the CDI as the source, choose BIN or BIN/CUE as the output, and enable CUE-sheet creation when offered. Keep separate output files for separate tracks if the program presents that option.
4. Start the conversion and keep the generated .bin and .cue files in the same directory. If you rename the BIN, edit the filename referenced by the first FILE line in the CUE sheet.
5. Load the .cue, not just the BIN, in the target emulator or virtual-drive program. For burning, select the application’s BIN/CUE or cue-sheet image mode rather than treating the BIN as a data file.

PowerISO’s CDI support and sector handling can vary by version. If it rejects the file or produces an image that does not boot, use a CDI-specific utility such as cdi4dc or cdirip for Dreamcast and other legacy CDI images, following that utility’s output instructions. These tools may extract tracks or produce an intermediate image rather than a ready-made BIN/CUE pair, so inspect the generated files and CUE sheet before use.

DiscJuggler can read its native CDI format and is useful for testing or recreating a source image, but it is not a universal CDI-to-BIN exporter. ImgBurn is useful for writing supported BIN/CUE images but should not be treated as a general CDI conversion tool.

Compatibility and quality limits

Conversion changes the image container; it does not restore missing sectors or improve source quality. A normal BIN/CUE conversion may not preserve copy-protection data, subchannel information, unusual DiscJuggler metadata, GD-ROM structure, or proprietary boot arrangements. Preserve the CDI until the converted image has been mounted or booted and its important files or tracks have been checked.

For a single conventional data CD, ISO may be a simpler destination, but ISO cannot represent every audio track, pregap, raw-sector, or mixed-mode feature that BIN/CUE can retain. Use raw-sector output, commonly 2352-byte sectors, when the source utility offers a sector-size choice and the target requires it; do not change the setting merely to reduce file size.

There is no consistently reliable online CDI converter for large, multi-track, or Dreamcast images. General services such as CloudConvert or Zamzar should be used only if their current format list explicitly includes CDI input and BIN/CUE output; uploading proprietary software or copyrighted backups may also expose content or breach usage rights. A local CDI-aware converter is safer and avoids upload limits, failed track detection, and privacy problems.