Convert IMG to BIN

A program, emulator, burning application, or hardware tool may require a .bin image when the source is a raw .img file. In many cases the data can be copied without alteration; optical-disc images may also need a .cue file that describes their tracks.

What the IMG format is

.img is a generic filename extension for a disk image containing sector-level data from media such as floppy disks, hard drives, USB drives, memory cards, or optical discs. It does not identify one mandatory internal format: an IMG may be a raw byte-for-byte image, a CloneCD image accompanied by .ccd and .sub files, or a proprietary image created by a vendor utility.

Tools including Win32 Disk Imager, Rufus, dd, CloneCD, and backup software create or use IMG files for writing bootable media, preserving removable disks, mounting software discs, and running emulators.

What the BIN format is

.bin is also a generic extension, not one universal specification. In disk-imaging workflows, it commonly identifies a raw sector image. For CDs and some other optical discs, BIN usually contains the binary track data and is paired with a .cue sheet describing tracks, indexes, pregaps, and sector modes.

BIN is appropriate when the destination application specifically expects a BIN/CUE set or a raw BIN image. It can preserve sector data, but renaming an extension cannot create missing track metadata or translate a proprietary image format.

How to convert an IMG file

First identify the source. Check the documentation for the program that created the file and look for companion files such as .ccd, .sub, or .cue. On Linux or macOS, file input.img can provide a preliminary identification; a generic result such as “data” is not proof of a particular image type. On Windows, a disk-imaging or hex-inspection utility can help, but the source application's documentation is usually more reliable.

For a raw image accepted by the destination: make a byte-for-byte copy and change the copy's extension. On Linux or macOS:

cp -- input.img output.bin

On Windows Command Prompt:

copy /b input.img output.bin

For a large file on Linux, dd if=input.img of=output.bin bs=4M status=progress also performs a byte-preserving copy. Do not substitute a physical disk path for either filename unless you have verified the device; an incorrect dd or copy target can overwrite a disk.

This method is an extension change, not a format conversion. Use it only when the receiving program accepts the same raw sector layout under the BIN extension.

For an optical image requiring BIN/CUE: use a desktop converter that recognizes the source format. In AnyBurn for Windows, open Tools → Convert image file format, select the IMG source, choose BIN/CUE if offered, specify the output folder, and start the conversion. Keep the generated .bin and .cue together, then open the CUE file in the burning, mounting, or emulation software.

UltraISO can perform the same task when it recognizes the source: open the image, choose Tools → Convert, select BIN as the destination, and retain any generated cue sheet. Menu names and supported source formats vary by version, so confirm that the input is recognized and that the output is BIN/CUE rather than ISO.

For command-line optical-disc work, cdrdao can read and write supported disc layouts, but it is not a universal IMG-to-BIN converter; use it only after identifying the source format and required TOC or cue-sheet structure.

An online service such as Convertio or CloudConvert is suitable only when its current format list explicitly accepts the particular IMG and produces BIN, preferably with CUE. Uploading a disk image can expose all data on the media, and large images may exceed service limits or lose optical-disc metadata. Do not upload sensitive images; download and retain every generated companion file.

Quality and compatibility limitations

For a byte-for-byte copy, compare hashes with sha256sum input.img and sha256sum output.bin. Matching hashes confirm that the data is identical; they do not confirm that the target application supports the image's layout. A real format conversion may legitimately produce a different hash.

A raw floppy, hard-drive, or USB IMG renamed to BIN remains a raw disk image and may not work in software expecting an optical BIN/CUE set. A CloneCD image can depend on its .ccd and .sub files for track layout, copy-protection information, or subchannel data; converting only the IMG can discard information required for accurate emulation or reproduction.

Keep the original IMG and all companion files until the BIN has been tested in the intended emulator, mounting tool, burning application, or device. Check the output size and test the image on equivalent media or a verified copy rather than overwriting the source.