What Is a CISO File?

A CISO is a compressed ISO image — a Wii disc image in which the empty, unused blocks of the original 4.7 GB ISO have been stripped out so the file takes up far less space, while still being a single file that backup managers can open and convert like a normal ISO. Wii Backup Manager reads and writes CISO alongside ISO and WBFS, which is why the format keeps appearing in Wii libraries even though the games themselves are usually played from .wbfs files.

Start With the Problem: Every ISO Is the Same Size

A Wii ISO is a sector-by-sector image of a game disc, and it is always 4,699,979,776 bytes for a single-layer game. The disc format reserves that full capacity whether the game needs it or not, so a small party game and a huge adventure both arrive as identical 4.7 GB files. For anyone storing more than a handful of games, most of those bytes are literally nothing — padding areas the console never reads as game data.

Two families of solutions grew around this waste. One trims the image into the loader-friendly WBFS file format. The other keeps the image as one self-contained file but removes the emptiness — and that is exactly what CISO does.

What “Compressed” Means in a CISO

Despite the name, a CISO is not compressed the way a ZIP archive is. ZIP-style compression squeezes the actual data and must decompress everything before use. A CISO instead records which blocks of the disc contain real data and stores only those blocks, together with a small map of where each block belongs. The game data itself is stored uncompressed and unchanged; the savings come entirely from discarding blocks that were empty.

This distinction has practical consequences. A CISO is usually larger than a modern archive format that also compresses the data itself, such as RVZ with zstd. But a CISO is simple and fast: managers can convert it, extract from it and verify it quickly, and its size is predictable — it matches the trimmed size of the same game as a .wbfs file, because both formats keep the same real data.

CISO vs WBFS: Storage File vs Play File

CISO and WBFS contain the same trimmed game data, so the choice between them is about role, not quality:

• WBFS is the play format. Games on the USB drive attached to your Wii live as .wbfs files in the /wbfs/Game Name [GameID]/ structure that USB Loader GX and WiiFlow Lite expect.
• CISO is a storage and transfer format. A single file per game is convenient for keeping a library on a PC drive, moving games between computers, or handing a game to a manager later. Wii Backup Manager opens a CISO exactly like an ISO when you add it to the transfer list.
• Conversion between them is lossless for game data. Going ISO → CISO → WBFS → ISO keeps the game itself intact at every step; only the discarded padding differs.

In practice, most people meet CISO in one of two places: as the output when they ask Wii Backup Manager to convert a game “to CISO” for storage, or as input — a game they already have in CISO form that needs converting to WBFS for the play drive. Our conversion guide covers the second case; the first is the same dialog with CISO chosen as the output format.

CISO vs RVZ: The Newer Alternative

RVZ, the compressed format from the Dolphin emulator ecosystem, goes one step further than CISO: it trims empty blocks and compresses the real data, typically with zstd, so archives are noticeably smaller. TinyWiiBackupManager works with ISO and RVZ natively, including high-compression RVZ archives. If you are building a long-term archive today, RVZ is generally the better container; CISO remains relevant because the classic Wii Backup Manager — still the most common tool on Windows — supports it directly, and because many existing libraries already contain CISO files. Our RVZ format guide explains when the newer format wins.

One Honest Caveat: CISO Is Not a Bit-Perfect Archive

Because a CISO throws padding away, it is not a bit-for-bit copy of the original disc, and it cannot be turned back into a byte-identical ISO of a retail disc. For playing and for everyday library management that makes no difference at all. But if your goal is preservation — a dump you can verify against community databases such as Redump — keep the original ISO (for example one you made from your own disc with CleanRip) or a lossless RVZ as the master copy, and treat CISO as a working copy. Conflating “plays perfectly” with “archives perfectly” is the one real mistake people make with this format.

When Should You Use CISO?

• Use CISO when Wii Backup Manager is your main tool and you want compact, single-file storage on your PC.
• Use WBFS on the drive that actually plugs into the Wii — always.
• Use RVZ when archive size matters most or when TinyWiiBackupManager is your main tool.
• Keep an ISO when the file is a fresh dump of your own disc that you may want to verify later.

Frequently Asked Questions

Can USB Loader GX play a .ciso file directly?

The reliable, documented workflow is to keep games on the play drive as .wbfs files, which every loader reads. If you have a game as CISO, add it in Wii Backup Manager and transfer it to the drive — it will be written as WBFS automatically.

Is CISO smaller than WBFS?

They are normally the same size for the same game, because both store the same trimmed data. Differences appear only if one conversion kept the update partition and the other stripped it.

Can I convert CISO back to ISO?

Yes — Wii Backup Manager converts between ISO, CISO and WBFS in any direction. The result plays identically, though it will not be byte-identical to a fresh disc dump, as explained above. See WBFS to ISO for the same workflow in reverse.