How to Batch Convert Wii Games with Wii Backup Manager
Wii Backup Manager 0.4.5 Build 78 by fig2k4 processes conversion and transfer queues with multithreading, so a folder of dozens of ISO backups can be converted to WBFS in one unattended run instead of game by game.
Batch conversion is where this program earns its keep. Converting a collection one title at a time is an afternoon of clicking; queueing the whole folder, letting multiple threads work in parallel, and reviewing a single log at the end takes minutes of your attention. This guide shows how to build a clean queue, choose settings that suit large runs, deal with the one or two files that inevitably fail, and verify the finished library without testing every game by hand.
Step 1: Stage Everything in One Place
Gather the source backups into a single folder tree first — ISOs, CISOs, WBFS files awaiting re-conversion, and RAR archives can all live together, because Wii Backup Manager reads each format directly. Staging matters for two reasons: the Add → Folder scan then captures everything in one pass, and any file you forgot is obvious when you compare the folder count with the queue count afterwards. Keep the staging folder on a fast local drive if you can; batch reads from a slow network share become the bottleneck no thread count can fix.
Step 2: Build the Queue
- Launch Wii Backup Manager and open the Files tab.
- Click Add → Folder and select the staging folder; let the scan finish completely.
- Review the list: every game should show a title, Game ID and plausible size. Zero-size or unreadable entries are corrupt sources — untick or remove them now so they do not fail mid-run.
- Tick all games for conversion, or work in sub-batches of a few dozen if you prefer checkpoints.
Duplicates deserve a quick pass at this stage. The same game added twice — once as ISO, once inside a RAR — will waste a full conversion slot and produce two copies on the drive. Sorting the list by Game ID makes duplicates sit next to each other where they are easy to spot.
Step 3: Choose the Destination and Start the Run
Click Transfer and choose the destination: a Drive tab for a loader-ready library (recommended — the program builds the /wbfs/GameName [GameID]/ structure and splits large games for FAT32 automatically), or a folder if you are staging WBFS files on the PC. The filesystem guidance in formatting a drive FAT32 for Wii applies unchanged to batch runs. Confirm the destination has enough free space — estimate from the WBFS sizes the queue reports, not the larger ISO sizes.
Start the transfer and leave it alone. Multithreaded processing converts several games simultaneously, so total time scales far better than a single-file run. Keep the PC awake (disable sleep for long runs) and do not use the destination drive for anything else until the queue drains.
Handling Errors Without Restarting the Batch
The log pane is the batch tool’s most important feature. When the run finishes, read it top to bottom: every game gets an entry, and failures are recorded with their reason — usually a corrupt source image or a destination write problem. The correct response to a failed game is narrow: replace that one source file, add it alone, and convert it by itself. There is never a reason to re-run the successful majority.
If many games fail with write errors at the same point, suspect the destination drive — a failing cable, a drive dropping off the USB bus, or a full volume — rather than the sources. Fix the hardware cause, then re-queue only the games missing from the destination. Comparing the destination’s game count with the queue count tells you exactly which ones those are.
Step 4: Verify a Large Library Efficiently
- Count check: games on the destination vs games ticked in the queue — the numbers must match, minus any logged failures you have noted.
- Size sanity: total destination size should be plausibly smaller than the ISO total (WBFS trims padding) but not dramatically smaller.
- Spot-boot test: launch three games in USB Loader GX — the largest split title, one mid-size game, and one small game. Split titles exercise the .wbfs + .wbf1 chain described in ISO to WBFS conversion.
- Metadata pass: finish with the GameTDB covers download so the verified library also looks complete in the loader.
Once verified, the staging ISOs can be archived or deleted according to your storage policy — keeping the originals is the safer archival choice, since WBFS files cannot rebuild the original padding, as explained in WBFS to ISO. For the single-game version of this workflow and everything around it, see the complete Wii Backup Manager guide.
Organising the Finished Library
A completed batch leaves you with a correct but flat result: hundreds of games in /wbfs/, each in its machine-named folder. Resist the urge to tidy those folders by hand in Explorer — the folder names carry the Game IDs that loaders and cover matching depend on, and renaming for neatness breaks the very systems that make the library pleasant to use. Organisation belongs in the tools, not the filesystem: Wii Backup Manager’s lists sort and filter by title, region and size, and the loader presents the library with GameTDB titles and covers regardless of folder names.
What is worth doing after a batch is a light audit while everything is fresh. Remove duplicate Game IDs if the count check exposed any, note which games failed and why in case you re-dump them later, and run the cover pass from the GameTDB covers guide so the library is complete in the loader from day one. A library that was batched, verified and audited in one sitting stays trustworthy for years — most of the horror stories in Wii forums trace back to a library that grew by unverified handfuls, on a drive that was never checked until it failed.