WBFS Folder Structure Guide — How USB Loader GX Organizes Games

When USB Loader GX shows an empty library, the games are usually on the drive — they are just not where the loader looks, or not named the way it expects. The loader’s rules are strict but simple, and once you see the whole structure laid out, most “missing games” problems diagnose themselves. This guide documents the exact layout: the wbfs folder, the per-game subfolder convention, split files, and where the loader’s own support files live, plus the one-line pointer to the separate GameCube layout.

The Structure at a Glance

At the root of your FAT32 game drive (or the FAT32 partition the loader scans), the layout is:

USB:/
└── wbfs/
    ├── Game Title [GAMEID]/
    │   └── GAMEID.wbfs
    └── Big Game Title [BIGID6]/
        ├── BIGID6.wbfs
        └── BIGID6.wbf1

Three elements do the work. First, the folder literally named wbfs, in lower case, at the root of the drive — not inside another folder, not on the desktop of the drive’s second partition. Second, one subfolder per game, named Game Title [GAMEID], where GAMEID is the game’s six-character ID. Third, inside that subfolder, the game file itself named exactly GAMEID.wbfs — the file name is the ID, not the title. When a single game exceeds the split size, additional parts named GAMEID.wbf1, .wbf2, and so on sit in the same folder — see the Wii Backup Manager guide for why splitting exists and why you must never separate the parts.

Why the Naming Rules Are Not Optional

The Game ID is the key to everything the loader attaches to a game: its display title, downloaded cover art, cheat files, and per-game settings such as video mode and cIOS choice. The loader finds the game file by structure, then reads the ID to look all of that up. Rename GAMEID.wbfs to something friendlier and the pairing breaks — the game may vanish, appear with a raw ID as its title, or lose its covers. Rename the subfolder’s bracketed ID and you create the same class of problem. The title portion of the folder name (before the brackets) is the only part that is safe to adjust, and even there, the healthy habit is to let Wii Backup Manager (official site) generate names rather than typing them — a backup copy is at Mirror (Terabox). Tools that generate the structure never make the typos that humans make at 1 a.m.

Where the Loader’s Own Files Live

The game library is only half the tree. USB Loader GX keeps its configuration, cover cache, and support data in its own folders, by default under the loader’s app directory — typically on the SD card at SD:/apps/usbloader_gx/, with image and configuration subfolders created on first run (covers land in an images tree organized by type). Two practical consequences follow. First, you can wipe and rebuild the game drive without touching your settings, and vice versa — they are separate trees. Second, when covers refuse to download or settings keep resetting, the SD side is where you look: check the card is not full, not locked, and not failing, as the SD card guide explains. If you prefer the loader’s data on the USB drive instead, that is a path setting inside the loader’s global options — change it deliberately, in the loader, not by moving folders by hand.

GameCube Games Use a Different Folder

GameCube titles do not go in wbfs at all. Nintendont reads them from a separate games folder at the drive root, with its own per-game subfolder and ISO naming rules. Mixing the two systems — a GameCube ISO dropped into a wbfs subfolder — simply makes the game invisible to both loaders. The full GameCube layout is documented in our dedicated guide: GameCube games folder structure. One drive happily holds both trees side by side: wbfs for Wii, games for GameCube, both on the same FAT32 partition.

Structure Mistakes That Hide Games

The double folder. Extracting a zip carelessly produces wbfs/Game Title [ID]/Game Title [ID]/GAMEID.wbfs — one level too deep. The loader scans one level; the game is invisible. The ISO in the root. A full ISO sitting at the drive root or directly in wbfs is not in a game subfolder, so it is never listed; convert and place it with a transfer tool instead. Uppercase WBFS folder on a case-sensitive step: FAT32 itself is forgiving, but tooling along the chain is not always — keep the folder name exactly wbfs. Games on the wrong partition. On a drive with leftover manufacturer partitions, the library can end up on a partition the loader is not scanning; one clean FAT32 partition, per the formatting guide, removes the ambiguity. Split parts separated during a manual copy: a .wbf1 left behind makes a large game fail exactly at the point the second part should load — often misdiagnosed as a bad backup when it is really a filing error.

Checking Your Tree in Two Minutes

Plug the drive into a PC and compare it against the diagram at the top of this page: root → wbfs → one folder per game → file named by ID. Count the subfolders and compare with the count in Wii Backup Manager’s Drive tab and the count in the loader; all three numbers should match. Where they differ, the odd one out tells you which step to revisit — transfer, structure, or the loader’s partition setting. That two-minute audit resolves most library problems without reinstalling anything.

For the complete build-out, see the setup guide, and get the loader from the Download page.

Frequently Asked Questions

Can I put the wbfs folder on the SD card instead of USB?

The structure rules are the same wherever the loader scans, and the loader can work with storage on SD — but the intended layout is games on the USB drive and the loader’s own files on SD. Keeping that separation makes troubleshooting far simpler.

Do folder names have to match the exact game title?

The title text is cosmetic; the bracketed Game ID is not. Wii Backup Manager generates both from the backup itself — trust its output and avoid hand-renaming either the folder’s ID portion or the .wbfs file name.

Why does one game show twice, or not at all, after I reorganized by hand?

Duplicates come from the same game existing in two subfolders (often an old nested copy); invisibility comes from nesting or renaming. Delete the stray copies in Wii Backup Manager’s Drive view and re-transfer one clean copy.

Related Guides

• Add Games with Wii Backup Manager
• Format a Drive to FAT32 for Wii — GUIFormat Guide
• Best Hard Drive for Wii & USB Loader GX
• Install USB Loader GX on Wii — Complete r1283 Guide

New to all of this? Start with the USB Loader GX Setup Guide hub and get the loader itself from the Download page.