A PlayStation 2 library ripped from your own discs grows faster than almost any other retro collection. Most PS2 games shipped on DVD, the biggest titles used dual-layer discs, and a faithful rip keeps every byte of the original. A few dozen games later, that folder is one of the largest things on your PC.
As an Amazon Associate, we earn from qualifying purchases.
CHD fixes that without giving anything up. It is a lossless compression format from the MAME project that current PCSX2 loads directly, so the compressed file is the one you play. This guide covers the PCSX2 side: which compressed formats the emulator accepts, the chdman commands for DVD and CD games, what savings are realistic, and how to verify or undo a conversion.
Disclosure: this guide includes affiliate links to storage hardware, and purchases made through them may earn this site a small commission at no added cost to you.
Quick Answer
Rip your PS2 disc to an ISO or BIN/CUE image, then convert it with chdman’s createdvd command for DVD games or createcd for CD games. The resulting CHD file is losslessly compressed, loads directly in current PCSX2 with no extra settings, and can be verified or converted back to the original image with chdman at any time.
Why a PS2 Library Eats a Drive
An uncompressed rip is a byte-for-byte copy of the disc, and PS2 discs carry a lot of bytes that are not game data. Publishers often padded discs, pushing real data toward the faster-reading outer edge. Your rip preserves all of that empty or repeated space.
CHD, short for Compressed Hunks of Data, was built by the MAME project for exactly this job. It splits an image into blocks called hunks and compresses each one with lossless codecs, so decompressing a CHD returns the original image bit for bit. Every CHD also carries SHA1 checksums of its data and metadata, so you can prove its integrity later.
The Compressed Formats PCSX2 Loads
Current PCSX2 releases treat CHD as a first-class format alongside ISO, BIN/CUE and MDF images. PCSX2 also accepts three older compressed formats, all worth knowing before you pick one.
CSO is a compressed ISO format carried over from the PSP scene. Decompressing one returns the identical ISO, so it is lossless too, but relies on a single deflate scheme and files usually end up larger than CHD versions of the same game. It only wraps ISO images, so CD-based games in BIN/CUE form do not fit it, and it stores no auditable checksum. ZSO, its LZ4-based sibling, trades ratio for faster decompression, and GZ is a plain gzip-wrapped ISO with the weakest compression of the group. For a game or two any of these is fine; for a whole library, CHD wins on size, structure and verifiability.
Converting With chdman, Step by Step
The converter is chdman, the command-line tool that ships with MAME. Everything below starts from a rip of a disc you own: PS2 games are unencrypted DVDs and CDs, so a standard optical drive produces the ISO or BIN/CUE you need.
For a DVD game, convert the ISO like this:
chdman createdvd -i "Game.iso" -o "Game.chd"
For a CD game, point createcd at the cue sheet, so the track layout and audio survive intact:
chdman createcd -i "Game.cue" -o "Game.chd"
The split matters. Createdvd is tuned for DVD images, with defaults built on LZMA, zlib, Huffman and FLAC codecs, and front-end documentation such as Batocera’s describes it as somewhat more efficient and better performing in-game than the CD path for a DVD. Createcd uses CD-specific codecs that handle audio tracks and subchannel data. Older guides used createcd for DVD ISOs too, and PCSX2 still loads those files, but createdvd is the right default for new conversions.
Leave the other options alone. MAME’s documentation warns that CHDs built with the optional Zstandard codec may not be readable by older software, while the defaults are what emulators expect. Hunk size is best left at the default too: larger hunks squeeze slightly harder but force more decompression work on every small read. When the conversion finishes, keep the original ISO until you have verified the CHD and booted the game once. Only then should the ISO move to the archive drive.
What Actually Shrinks, and What Barely Moves
Expect the library to shrink as a whole, but not every game to shrink alike. The padded, empty and repeated regions of a disc compress dramatically, and aggressively padded games can come down to a fraction of their ripped size. Ordinary game code, textures and models compress moderately well.
The stubborn part is anything already compressed at the factory. Full-motion video on PS2 discs is stored as compressed video streams, and many games pack their audio and assets into archives that were squeezed before mastering. With little redundancy left to find, an FMV-heavy game may barely move. CD-based games sit in between: their data tracks compress like small DVDs, while Red Book audio is handled by FLAC and trims losslessly.
Playing CHD Files in PCSX2
There is no CHD setting to enable. Add the folder to PCSX2, let the game list scan it, and boot a CHD exactly as you would an ISO. Decompression happens on the fly, one hunk at a time. The zlib-family codecs are light; LZMA, per MAME’s documentation, costs more to decompress. On any reasonably current processor, you will not notice the overhead in play.
Storage speed matters less than people fear, because the emulator reads in small pieces, not whole-image streams. A CHD library on a mechanical hard drive, or on a portable SSD over USB, plays the same as one on an internal NVMe drive for most games. The edge case is a very weak CPU with a streaming-heavy title: if a game stutters from its CHD, keep that one title as a plain ISO and compress the rest.
Verifying the Result, and Converting Back
Two chdman commands close the loop. Verify recomputes the file’s checksums and compares them with the digests stored inside it:
chdman verify -i "Game.chd"
A pass means the CHD is bit-identical to the one you created, an integrity check worth rerunning whenever the library moves drives. The info command reports compressed and uncompressed sizes side by side, so you can see what each conversion saved.
Extraction reverses the process losslessly when you need the original back:
chdman extractdvd -i "Game.chd" -o "Game.iso"
Use extractcd instead for a CD game, which restores the BIN/CUE pair. Because nothing was thrown away, the extracted file matches your original rip. This reversibility is the real reason to standardise on CHD: the compressed library is not a one-way door.
Storage and Gear for a Compressed Library
The workflow creates two tiers of files: original rips kept as masters, and CHD copies you actually play. These five products cover both tiers and the playing itself.
WD Elements 14TB Desktop Hard Drive
Master rips belong on a big desktop drive: roomy, always attached, and fast enough for files you touch once a year. This WD Elements holds the full uncompressed library, with space left for your other emulation archives.
Specs:
– Capacity: 14 TB
– Model: WDBWLG0140HBK-NESN
– Interface: USB 3.0 (USB 3.2 Gen 1, up to 5 Gbps)
– Power: included AC adapter
Check the current listing on Amazon
Samsung 990 PRO 2TB NVMe SSD
The play library belongs on the fastest storage in the machine: an internal NVMe drive makes game-list scans instant, with room for a large CHD collection.
Specs:
– Capacity: 2 TB
– Model: MZ-V9P2T0B/AM
– Interface: PCIe 4.0 x4, NVMe 2.0, M.2 2280
– Sequential speeds: up to 7,450 MB/s read, 6,900 MB/s write
– Endurance: 1,200 TBW, 5-year warranty
Check the current listing on Amazon
Samsung T7 Portable SSD 1TB
A portable SSD is the flexible middle tier: carry the CHD library between desktop, laptop and living-room PC, and play straight from it over USB. The T7 is small enough for a controller pouch and fast enough to never be the bottleneck.
Specs:
– Capacity: 1 TB
– Model: MU-PC1T0T/AM
– Interface: USB 3.2 Gen 2, up to 10 Gbps
– Speeds: up to 1,050 MB/s read, 1,000 MB/s write
Check the current listing on Amazon
UGREEN USB 3.0 SD Card Reader
If your setup includes a handheld or a single-board computer, game files spend time on SD and microSD cards. This dual-slot UGREEN reader moves CHD files on and off cards at USB 3.0 speed and reads both slots at once.
Specs:
– Model: 40752
– Slots: SD and microSD, usable simultaneously
– Card support: SD, SDHC, SDXC and microSD, UHS-I
– Interface: USB 3.0, up to 5 Gbps
Check the current listing on Amazon
Sony DualSense Wireless Controller (White)
Storage sorted, the library needs a pad, and the DualSense is the comfortable default for PCSX2: it pairs over Bluetooth or USB-C, its layout follows the DualShock lineage, and PCSX2 maps it without extra software.
Specs:
– Model: CFI-ZCT1W
– Weight: 280 g
– Features: haptic feedback, adaptive triggers, built-in microphone
Check the current listing on Amazon
How to Choose
A handful of games gains little from any of this, but once the rip folder passes a few hundred gigabytes, CHD conversion is the cheapest capacity you will ever buy. Convert three or four games first, verify them, boot each one, and only then batch the rest with a looping script.
Keep the two tiers separate: masters stay uncompressed on the big drive as insurance, while CHDs are the working set on fast storage. On an older machine, keep streaming-heavy favourites as ISOs. And keep the verify step either way: a compressed library you can audit beats a slightly smaller one you have to trust.
Who Should Skip
Skip CHD if your rips also serve hardware or front-ends that cannot read it, since you would end up storing both formats anyway. Skip it for a three-game library replayed constantly, where setup time costs more than the space returns. And skip it if you will not keep the original rips or run verify: without the integrity habit, one corrupted file becomes a lost game instead of a detected problem.
FAQ
Does converting a game to CHD change its graphics or audio?
No. CHD compression is lossless end to end, including CD audio, which is stored with the FLAC codec rather than re-encoded. Extraction returns the original image bit for bit, and verify proves the file matches its stored checksums.
My old DVD conversions were made with createcd. Do I need to redo them?
No. PCSX2 loads CHDs built either way. Createdvd is simply the better default for new DVD conversions. Redo a game only if you want the slightly tighter result; there is no compatibility deadline forcing your hand.
Why did one of my games barely shrink?
Because most of its disc was already compressed before mastering. Video sequences and packed asset archives leave little redundancy for any lossless codec to remove. The big wins come from padded and empty regions, which some games have in abundance and others hardly at all.
Is CSO still worth using instead?
It works, and PCSX2 reads it, but CHD is the stronger default here: smaller files, one file per game for CD titles too, and built-in checksums. CSO mainly makes sense when a file must also serve an older tool or device that never learned CHD.
Final Verdict
For anyone keeping a real PS2 library on a PC, CHD is the format the workflow should standardise on: lossless, reversible, verifiable, and noticeably smaller across a shelf of games, with PCSX2 treating it as a native format. Convert DVDs with createdvd, CDs with createcd, verify everything, archive the masters, and the drive-space problem largely goes away.







