Convert MDF to BIN
Convert Alcohol MDF/MDS disc images to tested BIN/CUE files with desktop tools.
How to convert mdf to bin file
- Disk images
- No ratings yet.
A disc-image application, virtual drive, or burning utility may require BIN/CUE instead of MDF/MDS for mounting, burning, or archival storage. The conversion is useful when the destination cannot open Alcohol's image format, but the original MDF/MDS files should be retained until the replacement image has been tested.
What the MDF format is
MDF is a proprietary optical-disc image format associated with Alcohol 120% and Alcohol 52%. The .mdf file normally contains the disc data, while the matching .mds file describes tracks, sessions, layer breaks, sector layout, and other information required to reproduce some discs accurately.
MDF/MDS images can represent CDs, DVDs, mixed-mode discs, audio tracks, and some copy-protected or multisession media. Keep both files together and open the .mds file when software asks for the image descriptor. A Microsoft SQL Server .mdf database file is unrelated and cannot be converted into an optical-disc image.
What the BIN format is
For optical media, BIN is usually a raw image accompanied by a small .cue cue sheet. The BIN stores sector data; the CUE records the filename, track boundaries, offsets, and track modes. A BIN without its CUE may contain the disc data but can lose usable track information, particularly for audio and mixed-mode discs.
BIN/CUE is accepted by many burning programs, virtual-drive applications, emulators, and archival tools. It is not a compression format and is not automatically smaller than MDF/MDS. BIN is a generic extension, so support varies: some programs handle only CD-style BIN/CUE images, while others also accept DVD or special raw-sector layouts.
How to convert the image
Direct conversion with UltraISO
- Copy the
.mdfand matching.mdsfiles to the same folder, then make a backup. - In UltraISO, open the descriptor through File → Open and select the
.mdsfile when possible. If the program accepts only the data file, open the.mdffile and verify that the tracks are displayed correctly. - Use Tools → Convert or the image-conversion command supplied by your UltraISO version.
- Select BIN/CUE as the destination, choose an output folder, and start the conversion.
- Confirm that both files were created. If the CUE references a different BIN filename, edit the first
FILEline in the CUE or rename the BIN to match it. - Mount or burn the CUE file, not just the BIN, and check the track count, audio playback, and accessible data.
UltraISO is a practical Windows option for direct MDF/MDS import and BIN/CUE export. Its trial restrictions and supported output formats can vary by version; a licensed copy may be required for large images or conversion features.
Conversion with AnyBurn or PowerISO
AnyBurn and PowerISO also provide image-conversion functions in versions that list MDF/MDS as an input and BIN/CUE as an output. Open the program's image converter, select the .mds descriptor as the source when offered, choose BIN/CUE, select a destination, and start the operation. Check the product's current format list before installation because format support differs between releases.
Read back a mounted image
Use this fallback when a direct converter cannot parse the MDF/MDS structure:
- Install a reputable virtual-drive application such as Virtual CloneDrive on Windows, then mount the
.mdsfile. The descriptor should select the associated MDF data automatically. - Open ImgBurn and choose Create image file from disc.
- Select the mounted virtual optical drive as the source and choose BIN as the output type if that ImgBurn release offers it. Enable creation of a CUE sheet when the option is available.
- Save the output, then open the generated CUE in a compatible mounting or burning program.
This method reads the virtual drive as if it were a physical disc. It can work around a parser incompatibility, but it cannot preserve subchannel data, intentional read errors, protection behavior, or other information that the virtual-drive software does not expose. Use the official ImgBurn download and inspect installer choices, because third-party download sites may bundle unwanted software.
Compatibility and quality limits
Converting MDF/MDS to BIN/CUE changes the container and track description; it does not repair bad sectors, decrypt protected content, or guarantee preservation of copy-protection metadata. An MDS-to-CUE conversion may also simplify layer-break, subchannel, or multisession information. For protected or unusual discs, keep the original MDF/MDS and use software that supports the original format instead of treating BIN/CUE as an exact replacement.
ISO is usually more portable for a single data disc, but it cannot accurately represent separate audio tracks, mixed-mode layouts, many multisession structures, or some raw-sector data. Use BIN/CUE when the target software requires it or when those track structures must remain available.
Online conversion is generally unsuitable: MDF/MDS images can be several gigabytes, many services do not parse the descriptor correctly, and uploading licensed or protected disc content creates privacy and rights concerns. A local desktop converter is the safer choice; no general online service should be assumed to produce a usable BIN/CUE pair unless it explicitly documents MDF/MDS input and cue-sheet output.