What is a .BIN file?
“BIN” is not an exact format either but a simple label for the binary information saved with nothing better. It happens when software does not have anything exact to give a particular name while saving the byte-streams to file. BIN/Cue format was the popular choice at 90s for raw CD images usually paired with a CUE text sheet that tells burning and mounting softwares about the organization of the tracks within it. It was made popular at 90s by "CDRWin" by Golden hawk technology.
Also hardware suppliers use bin format for delivering the firmware, boot loader, bios image, FPGA and calibration purposes for their particular device. Gaming preservation circles also use “bin” format as cartridge dumps. Bin files for sega genesis megadrive roms and atari 2600 roms appear the same way as well. These open inside emulators rather than burning discs software. There used to be another usage as "MacBinary". It means Macintosh binary file wrapper including data fork, finder metadata, creator type codes etc. The fastest way to discern between these usages is from context. A matching CUE sheet usually means you deal with a CD disc image, there will be hardware manufacturer’s website in case of a firmware, certain size gives idea for certain console if you are in gaming circles and old mac download hints MacBinary, but if the file is not giving any hint at its header, use hexadecimal editor, or program you think you might have used it.
How to open a .BIN file
Open a .BIN file on Windows
- 1 Go to the folder with your file in File Explorer. Usually, downloaded files end up in Downloads.
- 2 Double-click your .BIN file if you have an app for .bin files on your computer. In case it does not open, move on to step three.
- 3 Right-click your .BIN file -> select .
- 4 Choose PowerISO in the list (Windows 11: choose Always). For Windows 10 -> put a check on "Always use this app to open .bin files" and click OK.
Still not opening? See common problems and fixes, or view it in your browser.
Open a .BIN file on macOS
- 1 In the Finder app, locate your .BIN file.
- 2 Just double-click your .BIN file in order to automatically launch the program which is connected with it.
- 3 Need another app on your Mac? Control-click the file (or right-click with a mouse). In the pop-up menu select .
- 4 If it isn't in the list, choose and find the application manually.
Still not opening? See common problems and fixes, or view it in your browser.
Programs for macOS
- cdrdao open-source
- VLC media player open-source
- bchunk open-source
- ImHex open-source
- Binwalk open-source
- Ghidra open-source
- Kega Fusion free
- Genesis Plus GX open-source
Open a .BIN file on Linux
- 1 Launch your file manager. Depending on the desktop it may be named Files (GNOME), Dolphin (KDE Plasma), Nemo (Cinnamon) or Thunar (Xfce).
- 2 Double-click the file.
- 3 Or choose another program by right-clicking the file -> .
- 4 Install cdrdao (if it is not installed on your computer) from the software centre, repository or Flathub.
Still not opening? See common problems and fixes, or view it in your browser.
Programs for Linux
- cdrdao open-source
- VLC media player open-source
- bchunk open-source
- ImHex open-source
- Binwalk open-source
- Ghidra open-source
- Kega Fusion free
- Genesis Plus GX open-source
Open a .BIN file on Android
- 1 Launch Files or another file management app.
- 2 In Downloads, find the .BIN file and open it by tapping.
- 3 A list of apps capable of opening the file will be shown. Tap VLC media player and press Always to permanently connect the file type with this app.
- 4 No apps able to open this file? Download VLC media player from the Google Play Store.
Still not opening? See common problems and fixes, or view it in your browser.
Programs for Android
- VLC media player open-source
Open a .BIN file on iPhone / iPad
- 1 Use the Files app and go to On My iPhone, iCloud Drive or Downloads.
- 2 Tap the .BIN file you want to open.
- 3 If the file can be opened by a built-in iOS app (supported format), it opens automatically.
- 4 Touch and hold the file to get the context menu -> choose -> select VLC media player from the list of apps.
- 5 If there is no such option, download the app first from the App Store and then tap the document again.
Still not opening? See common problems and fixes, or view it in your browser.
Programs for iPhone / iPad
- VLC media player open-source
Open a .BIN file online
- 1 Move to the online viewer at the top of this page.
- 2 Drag the file there or select it, and its contents will appear in your browser tab. The file is not uploaded.
Still not opening? See common problems and fixes, or view it in your browser.
More details about opening .BIN files
Practical BIN/CUE utilities available for Windows are such popular applications as PowerISO, IsoBuster, ImgBurn, and WinCDEmu, where WinCDEmu has the open-source nature with emphasis on mounting a disc image into the virtual drive, and PowerISO offers conversion features to it. Also, ImgBurn might be good for analysis and burning the disk image whenever the cue sheet works properly. Meanwhile, for Windows, the recommended tool for data recovery out of damaged and multisession images is IsoBuster. On macOS platform there might work The Unarchiver and StuffIt Expander in order to unpack the MacBinary .BIN. Besides, such CLI utilities can do the trick of working with disc-images through terminal such as bchunk, cdrdao. On Linux side the same tools, which work with disc-images via the console (i.e. bchunk - converting BIN/CUE into ISO or WAV; cdrdao - reading/writing the raw CD image; binwalk - initial pass for any firmware-like .BIN file because of identifying the file system/any compressed files). In order to manage ROM images there have to be used special emulators like Kega Fusion/Genesis Plus GX on Segas Genesis/Mega Drive .bin files or Stella for Atari 2600 .bin files.
In case there comes to use some arbitrary binary file, the following step would be to try to view the file's content with HxD/ImHex or such utilities like 'hexdump' or 'xxd'. It should be said that such firmware-executable file (e.g., boot sector or checksum) might ruin some hardware if edited carelessly. Android devices usually do not support mounting images in .bin format. But VLC could play media-streamed data in .bin files, however, it will be necessary to use desktop utilities. Thus, once it does not help - check such things like the file size and its location and nearby files (.cue, .md5/.sig). If it did not work out in the very beginning, it may be a wrong file association. Change it only after checking if it is a disc-image/MacBinary-wrapper/image ROM/binary.
Technical details
Raw BIN file type can include sector-by-sector dump of CDs and DVDs (optical-disc version containing 2352-byte raw sectors compared to 2048-byte data sectors of ISO 9660-based .ISO images). The sector includes a synchronization section, a header, raw data (user data plus any additional ECC-related info), and subchannel stuff (if applicable). Hence, .BIN requires an associated cue sheet in order to provide details (e.g., mode such as MODE1/2352 or AUDIO of each track, INDEX, pregaps and names/filenames, and track numbers) missing there, while also providing more details about the contents as the cue sheet is a text file, while the raw dump preserves raw sector structure for restoration of the media to disc or drive. As different .BIN file format versions lack a standard or recognizable identifier or a standard header, identification is done by file extension, making this type of detection very unreliable (another reason for using 'application/octet-stream' in MIME types). Bin does not imply a particular form of compression; however, if compressed material exists within, it is embedded in the payload.
The BIN file name may be also used for unrelated binary formats. Typically, the first occurrence of the "SEGA" ASCII string happens at 0x100 bytes past start (usually 0x100 bytes past start); other parts include game console model/variant, titles (domestic and international), the product code and checksum of all, or portions of ROMs/RAM regions. MacBinary format uses the header with the size of 128 byte before saving the fork(s); versions called Macbinary II or III expanded and extended those headers with specific rules and validation stuff. Various firmware files in Bin include: Flash Page Dump or Flat Binary based upon ELF format, images used by bootloader such as u-Boot, compressed kernel images of linux, file systems SquashFS/JFFS2, signature/checksum data, vendor or device-specific data; typical sizes: small MCU firmware, Atari rom - a few kiloBytes, a maximum size of 16 bit-console ROM image ranges between 512 Kbytes and several megabytes.
How to convert .BIN files
A BIN and a Cue image should be converted into ISO if and only if this image contains only one data track on behalf of the request by a user to receive an mountable ISO9660 or UDF image of disc. This should be performed by using bchunk in tandem with input CUE sheet. E.g., bchunk input.bin input.cue output. A .BIN file does not carry any information regarding track information, pregaps and sector modes. Audio and Mixed mode discs are extracted as follows: bchunk -w audio.bin audio.cue track.
For any damaged or multi-session disc images and unusual sector formats, one can use either IsoBuster or PowerISO first, as usual tools do not support such kinds of layouts in their converters. To extract all embedded elements inside a firmware bin file the binwalk should be used: binwalk -e firmware.bin. Please remember that such an operation does result in obtaining analysis output rather than proper copy of a firmare image. The embedded engineers also build BIN images out of .elf, .hex files and S-record via objcopy. Such BIN image no longer contains load addresses, relocation information, etc. ROM images are often just renamed during conversion.
| Convert to | Tool | Command / note |
|---|---|---|
| ISO | bchunk | bchunk input.bin input.cue output Converts a BIN/CUE CD image to ISO plus WAV tracks where applicable; data-track offsets and mixed-mode layout depend on the CUE sheet. |
| TOC/BIN or CDR | cdrdao | cdrdao read-cd --read-raw --datafile disc.bin --device /dev/sr0 disc.toc Creates or manipulates raw disc images using cdrdao's TOC format; device name varies by system. |
| Extracted filesystem/files | IsoBuster | Useful on Windows for recovering files from BIN/CUE images, damaged optical media images, and multi-session discs. |
| Raw extracted firmware components | binwalk | binwalk -e firmware.bin Scans for embedded filesystems, compressed streams, bootloaders, and kernels; output is analysis/extraction, not a universal conversion. |
| ISO from single-track data BIN | iAt / iat | iat input.bin output.iso Works only for compatible single-track data images; audio or multi-track BIN/CUE images need the CUE sheet and a disc-image tool. |
| WAV audio tracks | bchunk | bchunk -w audio.bin audio.cue track Extracts CD audio tracks from BIN/CUE images to WAV when the CUE sheet describes audio tracks. |
| Plain binary dump from Motorola S-record | GNU objcopy | objcopy -I srec -O binary input.srec output.bin Common embedded-development conversion; the resulting .BIN has no metadata about load address unless stored elsewhere. |
Common problems and fixes
In case "Invalid or unsupported image file" pops up on the screen while trying to open .BIN with PowerISO, WinCDEmu, or similar software that works with images, most likely .BIN is not an image file at all, or you don't have an associated .CUE file with a proper reference to the file inside. Edit the CUE in text mode and change the wrong filename to match your BIN file or vice versa.
If "Cannot open file as archive" error message is produced after launching .bin files with such software as 7-Zip, keep in mind the following things: the problem might relate to some features particular to .bin files. They have raw bytes inside and not ZIP, RAR, or 7z structure.
Firstly try to figure out what was used to generate the dump in the first place; never go further without doing that. The next error related to mounting a file is a message about a failure with a sector type, track mixing, or with copy protection scheme.
Such problems cannot be handled by mounting utilities but you can use tools like bchunk, cdrdao or IsoBuster and see better results. In regard to firmware images and errors, you will most likely see messages "wrong model," "bad check-sum," "signature verification failed," or "image too old".
This might happen because .bin files can correspond to different revisions of hardware (or to hardware from other areas), as well as different bootloader versions. Some ROM emulators are unable to work with some dumps due to various reasons; e.g. you might get black screen if your dump is byte-swapped, overdumped, underdumped, or needs a BIOS file.
Antivirus programs consider dumps to contain packed or unknown binaries that could lead to infection of other files, large downloads may get truncated, so always verify your SHA-256 and MD5 and do it on time in order to avoid any problems. The same goes to large files, you might also need to pay attention to MacBinary.
Security considerations
However, .BIN format can also consist of an executable binary, such as machine code; boot sector, firmware code and images; ROM code; or install package payload - although execution by itself is determined not via extensions. Be aware that firmware BIN images from unreliable sources may potentially render routers, cellular handsets, BIOS/UEFI boards, microcontrollers, and other IoT devices into bricks if flashed in the device. Additionally, raw disc images may contain auto-starting malware or exploits, and old Windows auto-run binaries, as well as copyrighted games contents, so treat suspicious raw images in virtual machine or using read-only mount point. Parsers and binary file format analyzers can suffer from vulnerabilities regarding their memory safety. Raw .BIN images don’t trigger macros, so the security measures depend only upon the source of files, signatures and checksums. Regarding the MacBinary image format, the information included into the metadata can be filename, type/creator, notes and time-related values.
History and versions
The .BIN format predated the PC internet age and has been informally designated for binary in cases where an officially agreed extension did not exist. One notable historical usage was that of MacBinary, which was adopted back in 1985 as a means of transferring classic Macintosh files through mechanisms lacking ability to store resource forks/Finder info, and which saw its successor forms - MacBinary II (1987) and MacBinary III in 1990s.
Raw BIN/CUE disc image became popular thanks to 1993 Golden Hawk Technology utility called CDRWIN, since it became necessary way to store audio and mixed-type media as there wasn't efficient way to describe this type of media with a conventional ISO.
Usage of Game ROM files predates disc images tradition. The first Sega Genesis/Mega Drive .bin dumps were made at time of the console launch in Japan in 1988, and are still widely available in such form. However, Atari 2600 ROM dumps reflect a 1977 cartridge platform, and use of bin format persists today since most ROMs are basically array of bytes in addressable form and don't include file system.
There is no single .bin standard or registry-controlled specification, but bin extension is popular for various uses until today since bin containers are easy, platform neutral to work with and consume.
Related formats
Iso extension is the image for disc with ISO 9660 and UDF data tracks; it mounts more easily than a BIN file but cannot accurately represent all kinds of mixed-mode or raw-sector CDs. Also, .CUE files should come along with many .BIN images as a descriptive sheet because the information about track numbers and boundaries, modes of sectors, and whether it’s audio or data, could get missed otherwise.
There is an IMG format which works like .BIN but could refer not only to raw image files of floppy disks, HDDs, SDCard, and other types of media but optical disks, as well. Other optical image extensions are MDF/.MDS (Alcohol 120% software) and CCD/.SUB/.IMG (CloneCD), NRG (Nero).
For cartridges ROM files should better have .SMD extension, .GEN - Genesis extension, .MD - Mega Drive file extension, or else .A26 if you are dealing with Atari cartridge.
Work on firmware usually uses files that are addressed, e.g., ELF file with all symbol tables and .HEX (or its relative SREC files).
No comments yet. Be the first to share your experience with this file type.