How to Convert ISO to WBFS with Wii Backup Manager
Wii Backup Manager 0.4.5 Build 78 by fig2k4 reads ISO, CISO and RAR game backups and writes WBFS files, automatically splitting any game over 4 GB into a .wbfs file plus .wbf1 continuation parts for FAT32 drives.
WBFS is the format USB loaders actually play from a USB drive: it strips the padding and filler data from a full 4.7 GB ISO image, so most games shrink dramatically while remaining bit-identical where it matters. This guide covers the complete conversion — adding ISOs, picking the right output, understanding split files, and checking the result before you delete the source ISO. If your end goal is a playable drive rather than files on your PC, you may prefer to transfer directly as described in adding games to a USB drive, which performs this same conversion during the copy.
Before You Convert: What WBFS Conversion Actually Does
A Wii ISO is a full disc image, including large areas of padding that contain no game data. The WBFS format stores only the real data partitions, which is why a 4.7 GB ISO commonly becomes a WBFS file of 1–3 GB, and small games can drop below 500 MB. Nothing playable is removed: Wii Backup Manager can later rebuild a full ISO from the WBFS file, which is covered in converting WBFS back to ISO.
One consequence matters for archiving: a WBFS file is not a byte-for-byte disc image. If your goal is long-term preservation of an exact image, keep the original ISO (or a lossless format) as your archive and treat WBFS as the playing copy. For a drive that lives in the Wii, WBFS is the right choice.
Step 1: Add Your ISO Files
- Launch Wii Backup Manager (see the install guide if it is not set up yet).
- On the Files tab, click Add and choose Files, or Folder to scan a whole directory.
- Select your .iso files. CISO and RAR archives can be added the same way — they are read directly.
- Confirm each game shows the correct title and Game ID in the list. The Game ID is how loaders match covers and per-game settings.
Tick the checkbox beside every game you want to convert. If a file fails to load or shows a size of zero, the source image is corrupt — re-dump or re-download that game rather than converting a broken input, because the conversion will faithfully preserve the damage.
Step 2: Choose the Output — Drive Transfer or Files
There are two ways to produce WBFS files. Transferring to a Drive tab (Transfer → Drive 1) converts and copies in one operation and builds the loader-ready folder structure /wbfs/GameName [GameID]/gameid.wbfs for you — this is the right choice when the destination is your Wii drive. Converting to files on your PC keeps loose .wbfs files you can organise yourself, which suits staging a large library before copying.
Whichever route you choose, the filesystem of the destination decides whether splitting happens. On FAT32, files cannot exceed 4 GB, so splitting is mandatory and automatic. On NTFS, a single unsplit .wbfs is possible. The trade-offs between the two are explained in formatting a drive FAT32 for Wii and the WBFS vs FAT32 vs NTFS comparison.
Step 3: Run the Conversion and Watch the Log
Click Transfer and choose your destination. Wii Backup Manager processes the queue, using multiple threads so several games can convert in parallel on a multi-core PC. Progress is shown per game, and the log pane records the source, destination and any errors. Do not disconnect the destination drive or close the program mid-transfer: an interrupted WBFS file will be incomplete and the loader will either ignore it or fail when the game reaches the missing data.
When the queue finishes with no errors in the log, the conversion is done. If the log reports a read error on a specific ISO, that source file is damaged — replace it and convert just that game again.
Split Files Explained: .wbfs and .wbf1
On FAT32, any game whose WBFS data exceeds the split size is written as two or more parts inside the same game folder: gameid.wbfs holds the first part and gameid.wbf1 (then .wbf2, and so on, in principle) holds the continuation. This is not corruption and it is not two games — it is one game stored as a chain of files, and USB Loader GX reads the chain transparently. You will never notice the split while playing.
Two rules keep split games working. First, keep all parts together in the same /wbfs/GameName [GameID]/ folder with their original names — renaming or moving only the .wbfs file breaks the chain. Second, never delete a .wbf1 file to ‘save space’: it contains the second half of the game. If you later need to join the parts back into a single file, follow how to merge .wbf1 files.
Step 4: Verify the Result
- Open the destination in a Drive tab and confirm every game appears with the correct title and a plausible size (smaller than the source ISO, but not tiny).
- Check the game folder contains the .wbfs file and, for large games on FAT32, the .wbf1 part.
- If covers are missing, download them with the GameTDB covers guide rather than renaming files by hand.
- Load the drive in USB Loader GX once before deleting any source ISOs — one successful boot per game is the real verification.
Converting a whole collection at once? The queue, threading and verification workflow in batch converting Wii games scales this same process to dozens of titles. And if you are starting from a blank drive, begin with the complete Wii Backup Manager guide so the drive itself is set up correctly first.
A Note on CISO and Keeping Your Source Files
Wii Backup Manager can also write CISO, a compact ISO variant, but for a Wii drive there is rarely a reason to choose it: loaders expect WBFS on the drive, and CISO’s role is mainly as an intermediate or space-saving PC format. Stick with WBFS output for anything destined for the console. Whichever format you produce, keep the source ISO until the converted game has booted once on real hardware. Storage is cheap; re-dumping a scratched disc that has degraded further in the meantime may not be possible. The verified-boot rule — convert, test, then decide about the source — is the cheapest insurance in this entire workflow.