Convert ISO to WBFS

Wii USB loaders commonly expect games as .wbfs files on a USB drive, while disc dumps are often stored as full-size .iso images. Converting a valid Wii dump reduces storage used by unused disc sectors and allows large games to be split for FAT32 storage.

What an ISO file is

An ISO is a disc-image file; for Wii software, it is normally a raw image of a Wii optical disc. Wii dumping utilities, preservation workflows, and emulators such as Dolphin commonly use .iso files. A single-layer Wii disc image is usually 4.37 GiB (4,699,979,776 bytes), including padding and sectors not used by the game.

The .iso extension does not prove that a file is a Wii game. WBFS conversion tools accept Wii disc images, not PC software discs, DVD-video images, or arbitrary files renamed to .iso.

What a WBFS file is

WBFS is a Wii-specific game container that stores the disc blocks needed by the game and omits unused padding. The resulting size varies by title; some games shrink substantially, while games that use much of the disc shrink little.

A .wbfs file is different from the obsolete WBFS partition format. Current Wii homebrew setups normally use individual WBFS files on a regular FAT32 partition, typically under /wbfs/. FAT32 has the broadest compatibility with Wii homebrew and USB loaders. Some loaders can read NTFS, but FAT32 is the safer choice when compatibility matters.

FAT32 cannot hold a single file larger than 4 GiB. A loader-compatible conversion splits an oversized title into files such as GAMEID.wbfs and GAMEID.wbf1; both parts must remain in the same folder.

Convert with Wii Backup Manager on Windows

Wii Backup Manager is the practical desktop option for Windows. It reads Wii ISOs, creates loader-compatible names and folders, splits files when required, and transfers games directly to a USB drive.

1. Back up the USB drive, then format it as FAT32 if the target loader requires FAT32. Do not format it as a WBFS partition.
2. Open Wii Backup Manager. In the Drive 1 tab, select the target USB drive.
3. Open the Files tab and choose Add → Files, then select the Wii .iso.
4. Select the added game and choose Transfer → Drive 1. To create files on a local disk instead, use a folder destination.
5. Enable or accept file splitting for a FAT32 destination. The usual output layout is wbfs/Game title [GAMEID]/GAMEID.wbfs.

USB Loader GX and WiiFlow normally recognize that layout. Do not rename split parts or move .wbf1 files away from their matching .wbfs file.

Convert with Wiimms ISO Tools

Wiimms ISO Tools (wit) is available for Windows, macOS, and Linux and is useful for scripted conversions. After installing it, convert an image with:

wit copy input.iso output.wbfs

For a USB-loader folder, create a destination using the game ID reported by the image metadata, for example:

wit copy input.iso "wbfs/Game title [GAMEID]/GAMEID.wbfs"

Use the tool's split-file option when the output is going to FAT32 and the converted game exceeds the file-size limit. Check the installed version's wit --help output because option names can differ between releases.

Compatibility and quality limits

Conversion does not transcode video, audio, or game data. It preserves the blocks required for a supported Wii game, but a reconstructed ISO may not be byte-for-byte identical to the original padded dump because unused sectors are omitted or regenerated.

WBFS is for Nintendo Wii disc images. GameCube games should normally remain as GameCube ISOs and be configured for Nintendont or another compatible GameCube loader; converting them to WBFS does not make them usable.

Test the output in the target loader or Dolphin before deleting the source dump. Keep the original ISO when a raw archival image, checksum matching, or software that specifically requires an ISO is needed. Use dumps made from games you own and comply with applicable law.

Online conversion services are not a suitable recommendation for Wii images: uploads are commonly several gigabytes, free services impose size limits, and uploading game dumps creates privacy and copyright risks. Local desktop conversion is faster and avoids transferring the source image to a third party.