Understanding the Real Difference Between CHD Format and Redump Standards

The world of retro game preservation often feels like an alphabet soup of acronyms. Among the most frequent sources of confusion for newcomers and seasoned enthusiasts alike is the distinction between CHD and Redump. While these two terms often appear in the same forum threads and file descriptions, they are fundamentally different concepts that serve complementary roles in the emulation ecosystem.

To clarify the situation immediately: Redump is not a file format, and CHD is not a rival preservation group. Redump is a quality standard and a verification project dedicated to ensuring game disc dumps are perfect replicas of the original media. CHD, or Compressed Hunks of Data, is a specialized file container designed to compress those perfect replicas into a more manageable size without losing a single bit of data.

Understanding how these two interact is the key to building a high-quality, space-efficient, and future-proof digital game library.

The Preservation Gold Standard: What is Redump?

Redump is a community-driven disc preservation project that functions as the ultimate database for optical media. The project covers systems ranging from the PlayStation 1 and Sega Saturn to the PlayStation 3 and Wii U. The goal of Redump is simple but ambitious: to catalog every retail game disc ever produced and provide a "fingerprint" (a cryptographic hash) that proves a digital copy is an exact, 1:1 match of the original plastic disc.

The Anatomy of a Redump Set

When a game is referred to as "Redump-verified," it means the data within the files matches the entries in the Redump database. For CD-based systems, these files usually come in a .bin and .cue pair.

• The .bin file is a raw, sector-by-sector copy of the disc. Unlike a standard .iso file, which only captures data tracks, a raw .bin file includes sub-channel data, error correction codes, and audio tracks.
• The .cue file is a plain-text metadata sheet that tells the computer exactly where each track starts and ends.

For DVD-based systems like the PlayStation 2 or GameCube, Redump typically uses the .iso format. However, even these ISOs are strictly checked to ensure that "junk data" or "padding" placed on the disc by manufacturers hasn't been stripped away. In the eyes of Redump, if the original disc had 1GB of empty space filled with zeros, the digital copy must have that 1GB of zeros too.

Why Verification Matters

In the early days of the internet, game rips were often "dirty." Groups would remove intro videos to save space, or the software used to rip the disc would fail to read the lead-in and lead-out areas correctly. This led to games that might crash at specific points or lose their background music. Redump solved this by establishing a rigorous dumping protocol. If your file's MD5 or SHA-1 hash matches the Redump database, you have the digital equivalent of a brand-new disc.

The Efficiency Engine: What is CHD?

While Redump ensures accuracy, the resulting files are often bloated and disorganized. A single PlayStation 1 game might consist of one .cue file and thirty separate .bin files for audio tracks. Furthermore, the "padding" that Redump insists on preserving can waste gigabytes of space on your hard drive. This is where CHD (Compressed Hunks of Data) comes in.

Developed by the MAME (Multiple Arcade Machine Emulator) team, the CHD format was created to handle the massive hard drives and CD-ROMs found in arcade machines. It has since become the preferred format for modern emulators like DuckStation, PCSX2, and RetroArch.

How CHD Compression Works

CHD uses lossless compression. This is a critical distinction. Unlike a .jpg image or an .mp3 audio file, which throws away data to save space, CHD is like a .zip or .7z file specifically optimized for disc images. When an emulator reads a CHD file, it decompresses the data "on the fly" in memory. The game engine believes it is reading a raw, uncompressed disc, but the file on your hard drive is significantly smaller.

CHD is organized into "hunks"—blocks of data that are compressed individually. This allows the emulator to jump to any part of the disc instantly without having to decompress the entire multi-gigabyte file first, which is why it outperforms generic compression formats like ZIP or RAR for gaming.

CHD vs Redump: A Side-by-Side Comparison

To better understand their roles, we can look at how they differ across key functional areas.

The Relationship Synergy

The most important takeaway is that you do not need to choose between them. In a modern workflow, you use Redump to verify your source and then use CHD to store your library. A CHD file created from a Redump source is, for all intents and purposes, a "Compressed Redump."

Why You Should Convert Your Redump Sets to CHD

For anyone managing a library larger than a few dozen games, the transition to CHD offers three transformative benefits.

1. Massive Storage Savings

Disc-based games are notoriously inefficient. For example, a Sega Saturn disc might have 500MB of red-book audio. In a raw .bin format, that audio takes up 500MB of space. When converted to CHD using the FLAC compression algorithm (which CHD supports internally for audio tracks), that same audio might shrink to 200MB without any loss in quality.

For DVD systems like the PS2, the savings are even more dramatic. Many PS2 games were printed on 4.7GB DVDs but only contained 1GB of actual game data. The rest was "padding" to ensure the laser read the data from the outer edges of the disc more quickly. CHD identifies this padding and compresses it to almost nothing. In a collection of 500 PS2 games, converting from Redump ISO to CHD can easily save over 1 terabyte of space.

2. Elimination of File Clutter

Managing a PS1 collection in .bin/.cue format is a nightmare. A single game like Ridge Racer might have dozens of files. This makes browsing folders difficult and increases the chance of losing a single track file, which would break the entire game. CHD wraps everything—the data track, all audio tracks, and the metadata—into one single file. Moving, copying, and scanning your library becomes significantly faster and cleaner.

3. Native Integration and Performance

Modern emulators have moved away from requiring users to manually "mount" images. Because CHD is a seekable format, emulators like PCSX2 or DuckStation can read it directly. There is no performance penalty for using CHD; in some cases, because the computer is reading less data from the hard drive (due to compression), load times can even be slightly faster on slower mechanical drives.

Practical Guide: How to Convert Redump to CHD

If you have a collection of Redump-verified images and want to convert them, the process is straightforward but requires specific tools. The industry standard is chdman, a command-line utility bundled with MAME.

Using chdman for CD and DVD Images

For those comfortable with the command line, the basic syntax for converting a Redump .cue file to a .chd is:

chdman createcd -i "GameName.cue" -o "GameName.chd"

For DVD ISOs, the command is:

chdman createdvd -i "GameName.iso" -o "GameName.chd"

Batch Processing

Manually converting hundreds of games is tedious. Most users prefer using a "bat" script or a GUI wrapper. A common method for Windows users is to create a .txt file, paste a loop command that targets all .cue and .iso files in a folder, and rename the extension to .bat.

Alternatively, tools like NamDHC provide a graphical interface where you can drag and drop your entire Redump library, and it will handle the conversion, including the use of multi-threading to speed up the process on modern CPUs.

Potential Downsides and Metadata Loss

Is there any reason not to use CHD? While it is nearly perfect, there is one technical caveat involving Redump's strict metadata requirements.

The .cue File Dilemma

Redump's .cue files sometimes contain very specific "pre-gap" information or non-standard index points that are technically difficult to represent within the current CHD specification. When you convert a Redump .bin/.cue to CHD, and then later try to convert that CHD back to .bin/.cue, the resulting .cue file might not be a 100% text-match for the original Redump .cue.

However, the binary data ( the actual game and audio) remains identical. For 99.9% of users and emulators, this doesn't matter. The game will play exactly the same. Only "hardcore" preservationists who want to keep their files in a state where they can be instantly re-verified against the Redump database without any tool-assisted workarounds should keep the original .bin/.cue files.

Compatibility with Real Hardware

If you plan to play games on original consoles using "Optical Drive Emulators" (ODEs) like the Terraonion MODE or the XStation, you must check compatibility. While some modern ODEs are beginning to support CHD, many still require the raw .bin/.cue or .iso formats provided by Redump. Always verify your hardware's requirements before deleting your uncompressed source files.

Verifying CHD Integrity Against Redump

A common question is: "If I convert my game to CHD, how do I know it's still a 'Redump' copy?"

Advanced tools like verifydump (available on GitHub) allow users to check their compressed CHD files against Redump DAT files. The tool temporarily decompresses the data in memory, calculates the hash, and compares it to the Redump entry. This provides the best of both worlds: the space-saving benefits of CHD with the peace of mind provided by Redump's verification standards.

Summary: A Cohesive Strategy for Retro Gaming

The debate shouldn't be "CHD vs Redump," but rather how to use them together.

1. Acquire and Verify: Always start with Redump-verified images. This ensures your source material is flawless and complete.
2. Convert for Use: Convert those images to CHD for your active emulation library. You will save 30-70% of your storage space and eliminate file clutter.
3. Archive Strategically: If you have the storage space, keep your original Redump .bin/.cue sets on a cold-storage backup drive. Use the CHD files on your "daily driver" devices like the Steam Deck, PC, or Android handhelds.

By following this strategy, you respect the rigorous work of the preservation community while enjoying the technical advantages of modern compression.

Frequently Asked Questions

Does converting to CHD reduce game quality?

No. CHD is a lossless format. It is mathematically identical to the original data. It is not like converting a high-definition video to a low-bitrate one; it is more like putting a document into a folder. When you take it out, every word is exactly where it was.

Which emulators support CHD?

Almost all major modern emulators support it, including:

• RetroArch: Most cores (Genesis Plus GX, Beetle PSX, Stella, etc.).
• DuckStation: (PS1).
• PCSX2: (PS2).
• Flycast: (Dreamcast).
• Kronos / Mednafen: (Sega Saturn).

Can I convert a CHD back to an ISO?

Yes. Using the chdman extractdvd or extractcd command, you can revert a CHD file back to its original uncompressed state. This makes the format "future-proof," as you are never locked into it.

Why is Redump better than No-Intro?

They aren't competitors; they cover different media. "No-Intro" focuses on cartridge-based systems (NES, SNES, GBA), while "Redump" focuses on disc-based systems. If you are looking for a CD-based game, Redump is the standard you should look for.

Is CHD the same as CSO?

No. CSO (Compressed ISO) is an older format primarily used for PSP games. While it also offers compression, it is generally less efficient than CHD and doesn't support the complex multi-track structures found in CD-based games as well as CHD does. For most systems, CHD is now the superior choice.