WinBin2Iso is a free Windows tool by Nenad Hrg and SoftwareOK, latest v6.79 from 19 October 2026, distributed as ZIP files only with no installer. You can get it from the WinBin2Iso download page. This guide explains what MDF and MDS each do, how conversion works, and how to decide whether to convert, keep, or do both.

What the MDF file holds

The MDF file is the bulk of the image. It holds the disc data in a raw-ish form, similar in spirit to a BIN file, though in its own layout. If you only have the MDF file, you have the data, but you may be missing the organisational information that tells a tool how the disc was structured. That is why MDF files are normally distributed with MDS files, and why you should treat a lone MDF with a little caution until you know what disc it came from.

For a data disc, the contents of the MDF are what you ultimately care about: the files and folders that were on the disc. Conversion to ISO extracts that data into a single-file image that Windows 10 and 11 can mount natively. The conversion does not need to invent data. It repackages the data you already have into a more convenient form. If the MDF is incomplete or damaged, however, the ISO will reflect that, so checking the result matters.

What the MDS file holds

The MDS file is the small companion file, in the style associated with Alcohol 120%. It holds track and session information: how tracks are laid out, where sessions begin and end, and other structural details that the raw data alone does not spell out. Think of the MDS as the disc’s table of contents and structural notes, while the MDF is the disc’s contents.

How conversion to ISO works

WinBin2Iso converts MDF to ISO by reading the MDF data and writing it as a single-file ISO image. For a data disc, the result is an ISO you can mount in Windows, copy as one file, and store more easily than a pair of files. Our tutorial on how to convert MDF to ISO walks through the steps, and the general comparison in BIN vs ISO vs CUE vs IMG vs MDF puts MDF in context with the other formats.

Conversion is not the same as preservation of every detail. A plain ISO is a simpler structure than an MDF plus MDS pair. It is designed to hold disc contents in a standard, widely supported form, not to record every nuance of the original disc’s sessions and structure. For a single-session data disc, that simplification costs you nothing you were likely to use. For a multi-session or otherwise unusual disc, it can cost you structural information that only the original pair preserves.

What can be lost in conversion

The honest answer is: session and protection-related information, and other details that live in the MDS rather than in the user data, may not survive a conversion to a plain ISO. That does not mean files will disappear from a normal data disc. It means that if the original disc relied on session structure, or on details recorded in the MDS, to behave in a particular way, the ISO may not reproduce that behaviour exactly.

This is a reason to test, not a reason to panic. Convert, mount the ISO, and check that the files and folders you expect are present and readable. If they are, and the disc was a data disc, the conversion has done its job. If something looks missing or wrong, go back to the original pair rather than trying to repair the ISO. The original is your fallback, and it is far easier to reconvert than to reconstruct lost structure.

When to keep the original pair

Keep the original MDF and MDS pair when the disc is complex, when you are unsure what the disc contains, when you may need the original structure later, or when the disc is the only copy you have. Disk space is cheap compared with the cost of losing the only faithful copy of a disc. A sensible workflow is to convert to ISO for everyday use, verify the ISO, and then archive the original pair rather than deleting it immediately.

Keep the pair as your primary copy when the disc is an audio disc or a mixed disc with audio tracks, because track structure matters there in the same way it does for BIN and CUE audio discs. Converting a multi-track audio image to a single ISO can lose track boundaries, so the original pair is the safer master copy. For audio, see audio CD BIN to ISO and missing tracks, which explains the same caution in the BIN context.

Frequently asked questions

Do I need the MDS file to convert MDF to ISO?

WinBin2Iso converts the MDF data. The MDS is valuable for preserving the original structure and for tools that read the pair, so keep it even when the converter does not ask for it.

Will my files disappear if I convert MDF to ISO?

For a normal data disc, no. The files in the image should appear in the ISO. What may not survive is session and structural detail recorded in the MDS, which matters more for complex discs than for simple data discs.

This distinction matters because the wrong assumption can waste time at best and damage a device at worst. A disc-image BIN belongs in a converter such as WinBin2Iso, or in a mounting or burning tool. A firmware BIN belongs in the update process for the specific device it was made for, and nowhere else. Mixing those up is the one mistake this guide exists to prevent. WinBin2Iso itself is a free Windows tool by Nenad Hrg and SoftwareOK, latest v6.79 from 19 October 2026, available from the WinBin2Iso download page.

Disc image BIN: the raw copy of a disc

A disc image BIN is a raw, sector-by-sector copy of a disc. It does not just hold the files you could see in File Explorer when the disc was inserted. It holds the raw sectors, including bytes that are not user files. SoftwareOK describes a 74-minute CD as having 333,000 sectors, with raw sectors at 2,352 bytes, MODE1 data sectors carrying 2,048 bytes of data, and Mode2 sectors carrying 2,336 bytes of data or 2,352 bytes for audio. That raw structure is why a BIN file is often larger than the ISO made from it, and why the size difference alone is not a sign of a problem.

Disc image BIN files are usually distributed with a CUE file, a small text file that describes track layout. The pair works together for mounting and burning, even though WinBin2Iso does not need the CUE to convert a data BIN to ISO. If you want the full background, see what is a CUE file and the hub post BIN vs ISO vs CUE vs IMG vs MDF. A data BIN converts cleanly to a mountable ISO. An audio BIN needs more care, because converting a multi-track audio BIN to a single ISO can lose track structure, so the original pair should be kept for audio.

Firmware BIN: a different kind of file entirely

A firmware BIN is a binary file intended to be written to a specific piece of hardware, such as a router, a drive, a microcontroller board, or another embedded device. It is not a disc image, it does not contain a filesystem you can mount, and it is not meant to be converted to ISO. Firmware files are usually distributed by the hardware maker, with instructions for that exact model, and often with a checksum or version note tied to that model.

The file extension is the same, but the purpose could not be more different. A firmware BIN is written to hardware through a flashing or update tool provided for that device. A disc image BIN is converted or mounted as a disc. Treating one like the other will not produce a useful result, and flashing the wrong file to a device can leave it unusable. That is why the source of the file matters more than its extension.

How to tell them apart

Start with the source. A disc image BIN usually comes from a disc-imaging context: a disc backup, an archive of disc contents, or a page about disc images. It often arrives with a CUE file, or the page mentions a CUE file, tracks, or a disc. A firmware BIN usually comes from a hardware maker’s support page, a device forum, or an update package, and the page mentions a device model, a flashing tool, or a firmware version.

Next, look at companions. A CUE file alongside the BIN strongly suggests a disc image. A readme, a flashing utility, or instructions naming a specific device model strongly suggests firmware. Size alone is not decisive, but it can be a clue: a disc image BIN is typically at least tens of megabytes and often hundreds of megabytes, because it holds a whole disc, while many firmware files are much smaller, though there are exceptions in both directions, so size should never be your only test.

Never flash a firmware BIN as a disc image

This warning deserves its own section because the consequences are asymmetric. Converting a firmware file to ISO by mistake will usually just produce a useless ISO. Flashing a disc image, or the wrong firmware file, to a device can brick that device, meaning it no longer starts or functions normally. Do not use a disc-burning tool to write a firmware BIN to a device, and do not use a firmware flashing tool on a disc image BIN.

If you are unsure which kind of BIN you have, do not flash anything. Keep the file, note where you got it, and look for the original instructions. If the file came from a device maker’s site, the maker’s instructions for that model are authoritative. If it came as a disc image with a CUE, treat it as a disc image and use disc tools. When the two stories conflict, trust the source that actually distributed the file, not a forum guess.

Frequently asked questions

Is every .bin file a disc image?

No. The extension is generic. Disc image BIN files are one common use, but firmware files and program data files also use .bin. Check the source and companions before deciding.

What if my BIN came without a CUE file?

That alone does not prove it is not a disc image. Some data BIN files are distributed without a CUE. Check the source, and for a data disc you can still convert with WinBin2Iso.

This matters for WinBin2Iso users because the role of the CUE file is often misunderstood. For a data disc, WinBin2Iso does not need the CUE file to convert BIN to ISO. For mounting or burning the original BIN, the CUE is essential. Knowing which situation you are in saves time and prevents the common mistake of deleting a file you still need. You can get the converter from the WinBin2Iso download page.

What a CUE file actually contains

A CUE file is plain text. You can open it in Notepad or any text editor and read it. It does not contain audio, video, or program data. It contains lines that name a data file, declare track types, and give index positions. The data file named in the CUE, usually a BIN file, holds the actual disc contents. The CUE is the map; the BIN is the territory. Without the map, some tools cannot navigate the territory correctly, even though all the data is still present in the BIN.

Anatomy: FILE, TRACK, and INDEX

Three kinds of lines do most of the work in a CUE file. The FILE line names the data file and its type. The TRACK line declares a track and its mode. The INDEX line gives a position within that track, expressed in minutes, seconds, and frames. Together, they let a tool reconstruct the disc layout from the raw data.

Below is a generic example for a single data track. It is labelled as an example only, and it is not taken from any particular disc. Your own CUE file will name your own BIN file and may have different track details.

FILE “example.bin” BINARY

TRACK 1 MODE1/2352

INDEX 01 00:00:00

In this example, the FILE line points to a file called example.bin and says it is binary data. The TRACK line says track 1 is a MODE1 track with 2,352-byte raw sectors, which matches the raw sector size SoftwareOK describes for CDs. The INDEX line says the track starts at zero minutes, zero seconds, zero frames. A real disc with several tracks would have additional TRACK and INDEX lines, one set per track, in order.

Pairing rules: how BIN and CUE belong together

The pairing rules are simple, but they are worth stating plainly. First, the filename in the FILE line must match the actual BIN filename exactly, including spelling and, on systems that care about case, capitalisation. Second, the CUE and BIN should stay in the same folder, because many tools look for the data file relative to the CUE file. Third, do not rename one without updating the other. If you rename the BIN, open the CUE in a text editor and change the FILE line to match, then save it as plain text.

Fourth, a CUE file does not make a BIN file valid on its own. If the BIN is incomplete, truncated, or from a different disc, a correct-looking CUE will not fix it. The CUE describes layout; it cannot repair missing data. If a tool reports a CUE error, check the filename match and folder first, then consider whether the BIN itself is complete. Our guide to a missing or wrong CUE file walks through the common error messages and fixes.

When WinBin2Iso needs a CUE file, and when it does not

For a data disc, WinBin2Iso does not need the CUE file. You select the BIN file, choose an output ISO, and convert. The data is in the BIN, and for a data disc that is enough. This is good news if your CUE file is missing but your BIN is a data disc, because conversion can still proceed. Our tutorial on how to convert BIN to ISO without a CUE file covers that situation step by step.

For mounting or burning the original BIN, the CUE is a different story. Mounting tools and burning tools use the CUE to understand track boundaries and layout. Without it, they may refuse to mount the image, mount only part of it, or misread the track structure. The same applies to audio discs in general: even if a conversion tool does not ask for a CUE, the track information the CUE carries is what makes an audio disc behave like separate tracks rather than one long recording.

The practical rule is therefore: keep the CUE file whenever you have one, even when WinBin2Iso does not ask for it. It costs almost no disk space, and it preserves your options. If you later decide to mount or burn the original instead of using the ISO, you will be glad the CUE is still there.

Frequently asked questions

Can I open a CUE file to check it?

Yes. Open it in Notepad or another plain-text editor. You should see FILE, TRACK, and INDEX lines. If you see garbled characters instead, the file may have been saved in the wrong encoding or may not be a CUE file at all.

Do I need to keep the CUE after converting to ISO?

Keep it until you are sure you no longer need the original. It is tiny, and it lets you mount or burn the original BIN later. For audio discs, keep the BIN and CUE pair as the primary copy.

WinBin2Iso, the free Windows tool by Nenad Hrg and SoftwareOK, converts BIN to ISO and MDF to ISO. The latest version is v6.79, released on 19 October 2026, and it is distributed as ZIP files only, with no installer. You can get it from the WinBin2Iso download page. This guide explains each format so you can decide whether to convert, mount, or leave a file exactly as it is.

Quick comparison table

ISO: the convenient single file

ISO is a single-file disc image. That simplicity is its main advantage. You can copy one file, store one file, and, on Windows 10 and 11, double-click it to mount it as a virtual drive without extra software. For a data disc, such as a disc containing documents, photos, or program files, an ISO is easy to work with and easy to explain to someone else.

BIN and CUE: a pair, not a single file

BIN is a raw image of a disc. It holds the disc data in raw form, including the extra bytes that a simple file copy would not capture. That is why BIN files are often larger than the equivalent ISO. SoftwareOK notes that a 74-minute CD has 333,000 sectors, with each raw sector at 2,352 bytes, while MODE1 data sectors carry 2,048 bytes of data. The difference helps explain why a BIN can be larger than the ISO made from it, without anything being wrong.

CUE is the small text file that usually sits next to a BIN. It describes the track layout: which file holds the data, where tracks start, and how they are ordered. For a data disc, WinBin2Iso does not need the CUE file to convert BIN to ISO, because the data itself is in the BIN. For mounting or burning the original BIN, however, the CUE matters, because the mounting or burning tool uses it to understand the layout. See what is a CUE file and what is a BIN file for the full details.

IMG: check before you assume

IMG is a generic extension. It can be a raw disc image, a device image, or an image in another program’s own layout, depending on where it came from. Do not assume an IMG file will mount in Windows just because it looks like a disc image, and do not assume WinBin2Iso will convert it, because WinBin2Iso is built for BIN and MDF input. If you have an IMG file, first find out what created it and what it is supposed to contain. If it came with a CUE file or documentation, that documentation is your best guide. If it is a device image rather than a disc image, treating it as a disc image can lead to confusion or a failed mount.

MDF and MDS: keep the pair in mind

MDF is most often seen alongside MDS. The MDF file holds the image data in a raw-ish form, while the MDS file holds track and session information, in the style associated with Alcohol 120%. WinBin2Iso can convert MDF to ISO, which is useful for a data disc you want to mount easily. The trade-off is that a plain ISO may not preserve everything the MDS described, such as session details. For a straightforward data disc, that trade-off is usually acceptable. For a complex or unusual disc, keeping the original MDF and MDS pair is the safer choice. Our MDF and MDS explained guide and how to convert MDF to ISO tutorial cover both sides of that decision.

The audio warning you should not skip

Audio needs special care. A multi-track audio BIN and CUE converted to a single ISO can lose track structure. The music may still be there as one long stretch of audio, but the separate tracks, with their boundaries and ordering, may not survive in a usable form. If the disc is an audio CD, keep the BIN and CUE pair, or mount the original, rather than converting to ISO and deleting the source. ISO is right for data discs. For audio, preserving the original pair is the cautious and correct choice. The post on audio CD BIN to ISO and missing tracks explains this in more depth.

Frequently asked questions

Do I need a CUE file to convert a data BIN to ISO?

No. For a data disc, WinBin2Iso converts the BIN itself. The CUE is needed by mounting and burning tools that rely on it to read the original layout, not by WinBin2Iso for a data conversion.

Can Windows mount a BIN file directly?

No. Windows 10 and 11 mount ISO files natively, but not BIN files. Convert a data BIN to ISO first, or use a mounting tool that understands BIN and CUE.