Here is the fact to build everything else on: the Wii U outputs a 1080p signal to your TV, but the vWii environment inside it still renders Wii games at their original standard-definition resolution — up to 480p. The Wii U upscales that 480p image to fill its 1080p output; the game itself never becomes a 1080p game, and no loader setting can change that. USB Loader GX’s job on a modern TV is the achievable one: make sure the 480p image is produced correctly (right aspect ratio, progressive scan where the game supports it), passed cleanly to the Wii U, and scaled as well as your chain allows. This guide covers each link in that chain honestly.

This page assumes a working vWii install — if GX is not set up in vWii yet, follow our vWii install guide first, with files from the Download page.

The Signal Chain, Link by Link

1. The game renders at up to 480p inside vWii. Wii software was built for 480i/480p. That is the ceiling, set by the games themselves.
2. GX and vWii settings decide how that 480p is framed — aspect ratio and screen mode, covered next.
3. The Wii U scales 480p to its 1080p HDMI output. This upscaling is the Wii U’s, done once, and its quality is fixed.
4. Optional external scalers can process the HDMI signal further — the mClassic section below covers the one most Wii U owners consider.
5. Your TV does the final display — its own game mode and scaling settings still matter.

GX Settings That Actually Matter: r1282 Screen Mode and Aspect Ratio

Release r1282 (June 25, 2025) specifically improved vWii display behaviour in GX: games that only support 4:3 now use the correct aspect ratio automatically instead of being stretched to fill a 16:9 frame, and a dedicated vWii Screen Mode setting was added for use when 16:9 is enabled, letting you control how the image is presented rather than accepting a distortion. Practically: update to r1283 if you have not (it includes the r1282 changes — see the update guide), leave the aspect handling on its automatic behaviour for your first tests, and only adjust Screen Mode per your preference after seeing a 4:3-only game and a native 16:9 game side by side. A stretched image is a setting problem GX can fix; a soft image is the 480p ceiling, which it cannot.

In-Game and System 480p Settings

Progressive scan is decided in more than one place. On the console side, vWii inherits the Wii U’s output configuration — the Wii U is an HDMI machine, so the old Wii-era component-cable setting dance is gone. In GX, per-game video options include forcing video modes; leave the per-game video mode on its default/disc setting unless a specific game needs attention, because forcing 480p (or any mode) globally on games that do not expect it causes more black screens than improvements. Some games also carry their own display options in their menus. The sane order is: defaults everywhere, test the game, change one thing, test again. The themes guide’s advice applies equally to video settings — most “bad picture” reports are one stale per-game override away from fixed.

The HDMI Chain and the mClassic Option

From the Wii U onward, the chain is ordinary HDMI: Wii U → (optional inline processor) → TV. Keep the cable run simple and use the TV’s game mode to minimise the processing and lag your TV adds. The one add-on built for exactly this job is the Marseille mClassic, an HDMI upscaler dongle that sits between the console and the TV and applies its own upscaling and anti-aliasing processing to the image it receives. Positioned honestly: it processes the 480p-originated signal the Wii U sends — it does not and cannot recover detail the game never rendered — but its anti-aliasing and scaling are a different (many owners find better) treatment than a TV’s basic upscale, and it is switchable, so you can compare on your own screen. If you want to try one, it is available from the mClassic official store and via Amazon — mClassic. A simpler accessory in the same chain for original-Wii owners is a Wii-to-HDMI adapter such as those at Amazon — Wii2HDMI, which converts the Wii’s analogue output to HDMI without changing its resolution.

Disclosure: some links on this page are affiliate links. See our Affiliate Disclosure for how they work — they never change which settings or steps we recommend.

Setting Expectations, and a Word on “HD Remaster” Claims

Any guide or product claiming a loader — or any setting inside GX — makes Wii games render in native 1080p is selling something untrue. What is genuinely available to you is: correct aspect ratio without stretching (r1282’s fix), progressive 480p where games support it, the Wii U’s own competent upscale to its 1080p output, an optional external processor like the mClassic if you prefer its treatment, and a TV in game mode. Combined, that is a clean, faithful picture of a 480p library on a modern panel — which, for most players returning to these games, is exactly what they wanted “better picture” to mean. Pair it with the right source material — well-kept backups, correct settings per game — and vWii through GX is the best way to keep a Wii library on a current TV.

Frequently Asked Questions

Does USB Loader GX make Wii games 1080p on Wii U?

No. vWii renders Wii games at up to 480p, exactly as a Wii does. The Wii U upscales that image to its 1080p HDMI output. GX improves framing and correctness — aspect ratio and screen mode, especially since r1282 — but no loader can raise a game’s internal rendering resolution.

Why do some of my games look stretched on the TV?

That is the aspect-ratio issue r1282 addressed: 4:3-only games were being stretched into 16:9. Update to r1283, let GX apply the correct aspect ratio automatically, and check the vWii Screen Mode setting if a particular title still looks wrong after updating.

Is an mClassic worth it for vWii?

It depends on your TV and your eyes. The mClassic applies its own upscaling and anti-aliasing to the HDMI signal and many owners prefer the result to a TV’s built-in scaling of 480p content. It does not add real detail or make games render above 480p — judge it as a better treatment of the same image, and buy from the official store or Amazon links above if you try it.

Related Guides

• Install USB Loader GX on Wii U (vWii)
• Update USB Loader GX to r1283
• USB Loader GX Themes and Customisation
• Nintendont in USB Loader GX — GameCube Setup

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

USB Loader GX is named for USB drives, but it has supported loading Wii games from an SD card for years — and r1282 quietly made that option much more serious. Several well-known titles that previously refused to run from SD became playable, and for a compact setup — a Wii with a large SD card and no spinning drive at all — SD loading removes the USB drive, its cable, and its power quirks from the equation entirely. This guide covers the settings that enable SD loading, the honest trade-offs against USB, and which games r1282 specifically fixed.

Baseline first: GX itself should be installed and current — Setup Guide for the install, Download page for r1283 files. SD loading is a storage choice inside a working setup, not an alternative install method.

How SD Loading Works in GX

GX can read Wii game backups from the SD card’s /wbfs/ folder, in the same .wbfs format and folder structure that Wii Backup Manager creates for a USB drive. The difference is purely which device GX is told to look at for Wii games. GameCube games have always been at home on SD through Nintendont (see the GameCube folder structure); SD loading for Wii games is the newer, historically fussier side — which is exactly why the r1282 changes matter.

Step-by-Step: Enable SD Loading

1. Prepare the card. Use a good-quality SD/SDHC/SDXC card formatted to FAT32 for the partition GX reads (large cards formatted for this job are normally handled with a proper FAT32 formatter on PC). Card quality genuinely matters here — our best SD cards for Wii homebrew guide explains what to buy and what to avoid.
2. Add games with Wii Backup Manager. On your PC, transfer your own Wii backups to the card with Wii Backup Manager, targeting the card as the destination drive. It builds the /wbfs/Name [ID]/ structure and splits files correctly for FAT32. Copying loose ISOs onto the card by hand is the most common reason SD games “don’t exist” as far as GX is concerned.
3. Enable SD mode in GX. Open GX, go to Settings and the loader/hard-drive settings area, and enable the SD card mode option for Wii games (labelled as SD Card Mode in current builds). GX will then treat the SD card as a game source for Wii titles.
4. Set the game source/filter. In the main list’s source menu, make sure Wii games are enabled so the SD-hosted titles are included in the library, alongside (or instead of) any USB-hosted ones.
5. Restart GX and confirm the library. After changing the storage mode, restart the loader and check that your SD games are listed with titles and covers — covers download exactly as they do for USB games, per our covers guide.
6. Test one game thoroughly. Launch a game, play past its opening, save, and exit back to GX with the Return To behaviour you configured. Only then declare the setup working and move the rest of your library over.

What r1282 Changed: The SD-Playable Names

The r1282 release notes (June 25, 2025) state it plainly: Kirby’s Return to Dream Land, Excite Truck, and The Adventures of Tintin can now be played from the SD card. These were known holdouts — titles whose SD behaviour was broken before that release — so their explicit mention in the official log is the reliable signal that SD loading was reworked, not just left as-is. The same release removed the need for old cIOS versions for the Just Dance series, which further reduced the per-game fiddling a modern SD setup needs. On r1283 (which keeps all r1282 changes), an SD-first setup is a legitimate choice rather than a compromise for these titles. If you are still on r1281 or older, update before judging SD loading — you would be testing the old behaviour.

SD vs USB: The Honest Trade-Offs

Choose SD when your library is modest, you want the quietest and simplest hardware setup (no drive, no Y-cable, no port-power surprises), or the console travels. A single large, good card can hold a respectable Wii and GameCube collection, and both live happily on it — Wii games in /wbfs/, GameCube games in /games/. Choose USB when your library is large: hard drives offer far more capacity for the money, and very large collections mean very large cards. Speed differences in real gameplay are rarely the deciding factor — loading behaviour is dominated by the game, not the medium — but cheap no-name cards are a genuine reliability risk in a way that a decent hard drive is not. Whichever you pick, keep the same discipline: proper /wbfs/ structure from Wii Backup Manager, and backups of the card/drive contents on your PC.

One layout warning: Nintendont and GX data also live on the SD card. Leave breathing room rather than filling a card to the last megabyte — emulated memory cards, covers, and configuration all need somewhere to grow.

Frequently Asked Questions

Can USB Loader GX really run Wii games from SD, or only GameCube games?

Both. GameCube-from-SD through Nintendont is the long-established route, and GX also loads Wii games from the SD card’s /wbfs/ folder when SD Card Mode is enabled in settings. The Wii side improved notably in r1282, which is another reason to run a current build.

Which games did r1282 make playable from SD?

The r1282 release notes name Kirby’s Return to Dream Land, Excite Truck, and The Adventures of Tintin as now playable from the SD card. Those three were called out because they were known SD holdouts before that release.

Is SD loading slower than a USB hard drive?

In practice, gameplay is not meaningfully different for most titles; the real SD risks are capacity cost and poor-quality cards, not speed. A good card from a reputable brand is the entire secret — see our SD card buying guide linked above.

Related Guides

• Best SD Cards for Wii Homebrew
• GameCube Games Folder Structure
• Covers and GameTDB in USB Loader GX
• Update USB Loader GX to r1283

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

USB Loader GX has been skinnable for most of its life, and current r1283 builds keep the full theme system: downloadable themes that restyle the whole interface, several built-in view modes for the game library, and — since r1282 — a fast way to switch themes between the Wii, GameCube, NAND, and EmuNAND channel views without digging through menus. This guide covers where themes are installed, how to switch and preview them safely, the view modes worth knowing, and the small language and font options that round out personalisation.

Themes are cosmetic: they change how GX looks, never how games run. If your loader is not installed yet, start with the Setup Guide and the Download page; then come back and make it yours.

Where Themes Live

GX looks for themes in its theme folder on the SD card (or the device holding your GX data). The standard path, relative to the device root, is:

• /apps/usbloader_gx/theme/ — the theme folder inside the loader’s own app directory.
• Each theme is kept as its own package/folder inside that location, with its images and theme configuration together.
• The exact location GX reads can be adjusted under Settings > Custom Paths, like the cover folders described in our covers guide. If you move GX data, move the theme folder too, or themes will silently revert to the default look.

Installing a Theme, Step by Step

1. Get a theme built for USB Loader GX. Themes are distributed as archives containing the theme’s assets. Use themes made for GX — assets for other loaders are not interchangeable.
2. Extract it on your computer first. Unpack the archive and confirm you have the theme’s own folder/files, not a folder nested inside another folder from the zip. The “extra nested folder” mistake is as common with themes as it is with apps.
3. Copy it into the theme folder. Place the theme into /apps/usbloader_gx/theme/ on the SD card, keeping its internal structure exactly as extracted.
4. Apply it in GX. Start GX, open Settings and find the theme/GUI appearance options, then select the new theme from the list of installed themes. GX applies it immediately, so you can judge it in place.
5. Restart GX once after a big change. Most theme elements swap live, but a restart guarantees every screen — including the game-info and settings screens a quick preview never visits — has picked up the new assets.
6. Keep the default theme reachable. If a theme renders badly on your display (oversized text and missing buttons do happen with community themes), the cure is always the same: switch back to the default theme in Settings, then delete or fix the problem theme’s folder at your leisure. You cannot brick a loader with a theme.

The r1282 Quick Theme Switching

Release r1282 (June 25, 2025) improved theme support so you can switch themes quickly between the loader’s main views — Wii games, GameCube games, real NAND channels, and EmuNAND channels. In practice this means the different sources in your library can carry a different look, and flipping between them no longer means a trip through Settings each time. It pairs naturally with how most people actually organise a big setup: one view for Wii discs, another for GameCube through Nintendont, another for WiiWare on EmuNAND. Combined with the per-view cover types GX already supports, each source can feel like its own console shelf. The current r1283 build keeps this behaviour — see our update guide for what else changed between revisions.

View Modes: The Other Half of “Theming”

Before installing anything, the built-in view modes already change the library more than most themes do. GX offers list, grid, and cover-flow style presentations of the same library, switchable from the main screen’s view controls. Cover views lean on the 3D covers and disc art from GameTDB; list views suit very large libraries where scrolling box art is slower than reading titles; grid sits in between. Sorting and filtering — by title, by source, by favourites — also live at this level and are worth setting up before judging any theme: a theme looks wrong when the real problem is a 600-game unsorted wall. Pick the view that fits your library size first, then theme it.

Fonts and Language, Briefly

GX’s interface language follows the community translation files shipped with the loader, switchable in Settings — translation completeness varies by language and improves release to release (r1283, for example, included an updated Korean translation). Themes can also bundle their own font assets; if a theme shows boxes or missing characters in your language, that theme’s font lacks your characters, and switching the theme (or its font) is the fix, not a loader fault.

Frequently Asked Questions

Where exactly do I put a theme I downloaded?

Extract it and place the theme’s folder inside /apps/usbloader_gx/theme/ on the SD card (or your GX data device if you use custom paths). Avoid an extra nested folder from the zip, then select the theme in GX’s appearance settings.

A theme made GX hard to read or navigate. Is my install damaged?

No. Themes are purely cosmetic and fully reversible. Reopen Settings, switch back to the default theme, and GX returns to its standard look immediately. A bad theme cannot affect games, saves, or the loader’s core files.

Can Wii, GameCube, and channel views really use different themes?

Yes — r1282 improved theme support to allow quick switching between the Wii, GameCube, NAND, and EmuNAND views. It is a presentation feature: the same library and settings sit underneath whichever look each view uses.

Related Guides

• Covers and GameTDB in USB Loader GX
• Update USB Loader GX to r1283
• EmuNAND and WiiWare in USB Loader GX
• Nintendont in USB Loader GX — GameCube Setup

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

The cover-flow library is the face of USB Loader GX, and it runs on GameTDB — the community game database (formerly WiiTDB) that maintains cover artwork, disc art, and the wiitdb.xml information file GX uses for titles, synopses, and ratings. GX can download all of it automatically, in bulk, with one controller button. This guide explains the four cover types, the batch download, where the files live, how to keep wiitdb.xml current, and what to check when covers refuse to appear. If your problem is specifically that cover downloads fail, we also have a dedicated fix page: USB Loader GX covers not downloading — fix guide.

Everything here assumes GX is installed and your games already appear in the list — covers decorate games, they do not create them. If games themselves are missing, fix that first via the Setup Guide; the Download page has the current loader files.

The Four Art Types GX Uses

• 2D covers — the flat front box art. Used by the simpler list and grid views.
• 3D covers — the front art rendered onto a 3D box. This is the image the classic GX cover view is known for, and the one most themes expect.
• Disc art — the printed face of the game disc, shown when a game is selected in several views and used by disc-launch animations.
• Full covers — the complete front-and-back cover sheet. Larger files, used by views that show the open box / back cover information.

Downloading “covers” in GX lets you choose which of these types to fetch. A game can have some types and lack others — GameTDB’s collection is community-maintained, so an obscure or very new title may have a 2D cover but no disc art yet. Missing disc art for one title is a database gap, not a fault in your setup.

Batch Download: The (1) Method

1. Connect the console to the internet. Cover and database downloads happen over the Wii/vWii’s normal connection. Run the system connection test first if you have not used this console online.
2. Press (1) on the Wii Remote in the game list. In USB Loader GX, pressing 1 with the library open brings up the download menu for covers and game information. (On some themes the same menu is reachable from the settings/downloads area — the (1) shortcut is the standard route.)
3. Choose what to download. Select the cover types you want (start with 3D covers and disc art for the classic look, plus 2D for list views) and include the game information update so wiitdb.xml refreshes at the same time.
4. Let it work through the library. GX checks each game against GameTDB by its game ID and downloads only the missing art — running the download again later is incremental, not a full re-download. Large libraries take a while the first time; that is normal.
5. Restart or rescan if a cover lags. A cover downloaded for a game occasionally only renders after the library refreshes. A restart of GX is the simple cure.

Where Covers Live, and Custom Paths

GX stores downloaded art in its data folders on SD or USB, organised by type — separate folders for the 3D covers, 2D covers, disc art, and full covers within the GX image/cover directory structure. You rarely need to touch these by hand, but two hand-managed cases exist: adding a cover for a homebrew or custom title that GameTDB does not know (name the image file with the game’s six-character ID, in the right folder, at a sensible size), and moving a library between devices (copy the cover folders along with the games so you do not re-download everything). The exact folders GX reads are configurable under Settings > Custom Paths if you keep GX data somewhere non-standard — if covers suddenly “vanish” after reorganising files, a moved data folder plus a stale custom path is the first thing to check.

Keeping wiitdb.xml Current

The wiitdb.xml file is GameTDB’s game information database in a single file: correct titles (including games whose internal names are cryptic), release info, synopses, player counts, and controller support. GX uses it to name and describe your library — and cheat-code downloads are also keyed to the same game IDs. Let GX update it as part of the (1) download routine whenever you add games, and stale titles or missing info usually resolve themselves. If your library shows wrong names for several games at once, an outdated wiitdb.xml is a far more likely cause than bad backups, particularly for GameCube titles where the folder ID drives identification.

When Covers Will Not Download

Run this short checklist, then move to the dedicated fix guide: the console passes its internet connection test; the game IDs are correct (covers are matched by ID, so a misidentified game gets no art or the wrong art); the device holding GX’s data folders is writable and not full; and you have restarted GX once since adding the games. Failures that survive those checks — server errors, partial downloads, art that downloads but never displays — are covered step by step in the covers-not-downloading fix in our Troubleshooting cluster.

Frequently Asked Questions

What is the difference between 3D covers and full covers?

A 3D cover is the front artwork presented as a three-dimensional box — the standard GX library look. A full cover is the complete unfolded cover sheet, front and back, used by views that display the back of the box. Most users want 3D covers plus disc art; full covers are optional and use more space.

Why does one specific game never get a cover?

Because GameTDB is community-maintained and matching is by game ID. If that exact ID has no art uploaded, GX cannot invent one. Check the game is identified with the correct ID first; if it is, the gap is in the database, and you can add the image manually in the covers folder named by that ID.

Do covers download for GameCube games too?

Yes. GameCube titles in your GX library get covers from GameTDB by the same ID-based process — which is one more reason to include the correct [ID] in each GameCube game folder name.

Related Guides

• Fix: USB Loader GX Covers Not Downloading
• GameCube Games Folder Structure
• Ocarina Cheats in USB Loader GX
• USB Loader GX Themes and Customisation

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

Ocarina is the cheat engine built into USB Loader GX (and inherited from the original standalone Ocarina app): it applies Gecko-format cheat codes to a game as it launches, without modifying the game itself. Used well, it is how players unlock widescreen patches, remove nuisance limits, or revisit a favourite game with a twist. Used carelessly, it is also how saves get corrupted and online accounts get banned. This guide covers the whole GX workflow — turning Ocarina on per game, getting codes from GameTDB, generating the .gct file GX actually reads, and the one etiquette rule that is not optional.

Ocarina settings in GX are per game by design. There is no sensible “cheats on for everything” workflow, and this guide will not give you one: codes are written for a specific game, a specific region, and often a specific revision. Confirm your loader is current from the Download page first, and treat the Setup Guide as the baseline install this page builds on.

How Ocarina Works in GX

For each game, GX can hold a cheat file in the Gecko .gct format — a compiled bundle of codes. When you launch a game with Ocarina enabled for that title, GX loads the .gct and the codes take effect in memory for that session only. Your backup image is never altered, and disabling Ocarina returns the game to stock behaviour completely. Codes themselves are distributed as plain text lists (the .txt form), and GX contains a code manager that can download the text file for a game, let you tick individual codes, and generate the .gct from your selection. That generated file — not the text file — is what gets applied at launch.

Step-by-Step: Adding Cheats to a Game

1. Select the game in GX and open its individual settings. Ocarina is configured per title: choose the game, open Game Load / game settings, and find the Ocarina option.
2. Download the code list. With the console online, use the Ocarina / cheat management option for that game (GX offers to download cheats for the selected title). GX fetches the code list for that game’s ID and region from the cheat database mirrored alongside GameTDB — the same service family that supplies your covers and game info (see covers and GameTDB).
3. Choose codes deliberately. In the code manager, enable only the codes you actually want. Codes that conflict with each other — two codes writing the same behaviour differently — are a common cause of freezes. If you are troubleshooting, one code at a time is the rule.
4. Generate the .gct. Save/apply your selection in the code manager. GX writes the compiled .gct file into its cheat storage (the codes location within the GX data folders on SD/USB, named by the game’s ID). If you manage cheats on a PC instead, place a ready-made .gct with the game’s ID as its file name in that same codes folder — GX only looks for the .gct at launch time, regardless of which side created it.
5. Turn Ocarina ON for that game. Back in the game’s settings, set Ocarina to On. This switch is separate from having a .gct file: a file with the switch off does nothing, and the switch on with no file does nothing either. Both halves are required.
6. Launch and test. Start the game and confirm the code’s effect. If the game freezes before or at launch, the first suspect is a bad or conflicting code — disable codes in halves until the culprit shows itself. If everything freezes, turn Ocarina off for that title and confirm the stock game still runs; that separates a cheat problem from a game problem.

Where Codes Come From, and Region Discipline

The code lists GX downloads are community-maintained Gecko code lists keyed to each game’s ID. That ID encodes the region — a code written for the US release of a game generally will not work on the European release, because the game’s memory layout differs. If a downloaded list produces no effect at all, a region mismatch is the likely reason, not a broken loader. Likewise, some codes exist in versions for different revisions of the same game. The fix is always the same: match the code list to the exact ID of the backup you are launching, which GX shows in the game’s information.

Keeping Cheats from Hurting Saves

Codes that alter inventory, currency, unlocks, or progress write those changes into your save when the game saves. That is sometimes the point — and sometimes a nasty surprise when a “fun” code corrupts a long-running file. Before experimenting on a save you care about, back it up (save management is part of the wider GX feature set; see also the save-path discussion in our EmuNAND guide for how GX separates save locations). And treat any code that promises online advantages as what it is: a way to get banned, not a feature.

Frequently Asked Questions

I downloaded cheats but nothing happens in game. What is missing?

Usually one of three things: Ocarina is not switched On in that game’s individual settings; the .gct was never generated from the text code list (tick codes and save in the code manager); or the codes are for a different region/revision than your backup. Check them in that order.

Where does GX store the .gct files?

In the codes folder inside the USB Loader GX data folders on your SD card or USB drive, with each file named by the game’s six-character ID (for example RMCE01.gct). If you build a .gct on a PC, it goes in that same folder with that same naming.

Can Ocarina codes damage my game backup?

No — codes act in memory for the session and never modify the backup file. They can, however, affect save data if the game saves while a code is altering values, and they will get you banned if used online. Back up saves you care about and keep Ocarina off online.

Related Guides

• Covers and GameTDB in USB Loader GX
• Wiimmfi in USB Loader GX — Online Play
• EmuNAND and WiiWare in USB Loader GX
• Nintendont in USB Loader GX — GameCube Setup

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

A Wii’s internal NAND flash is small, and every WiiWare title and Virtual Console game you install competes for that space — along with save files and system channels. USB Loader GX’s EmuNAND feature solves this by redirecting channel storage to an SD card or USB drive: you dump (copy) your NAND once, tell GX where the copy lives, and from then on WiiWare and VC channels can be installed to, and launched from, that much larger storage. This guide walks through the dump, the path settings, installing channels, and the save-data rules that keep people out of trouble.

EmuNAND in GX is primarily a channel-storage feature: think of it as moving your downloadable games off the cramped internal memory. It is set up from inside GX’s Settings under the Features area. Before starting, make sure GX itself is installed and current — the Setup Guide and Download page cover that baseline.

Before You Start

• A working USB Loader GX r1283 install on Wii or vWii (on vWii, use only vWii-safe tools for any WAD handling — see the caution below).
• An SD card or USB drive with free space for the NAND dump and the channels you plan to install. A NAND dump is only a few hundred megabytes at most; the channels are what grow.
• A NAND backup made with your usual backup method, kept somewhere safe. The EmuNAND dump is a working copy, not a substitute for a real backup.
• The WiiWare/VC WAD files for titles you own, if you plan to install channels you do not already have on the real NAND.

Step 1 — Dump the NAND

1. Open USB Loader GX and go to Settings > Features.
2. Find the Dump NAND option (labelled along the lines of “Dump NAND to EmuNAND”) and start it. GX copies your NAND contents to the EmuNAND location on SD or USB.
3. Wait for it to finish completely. The dump creates the folder structure GX expects (a nand-style folder tree on the target device). Interrupting it leaves a half-copied NAND that channels will misbehave on — if a dump is interrupted, delete it and run it again rather than patching around it.
4. Confirm the dump exists on the device before moving on: the target should now contain the copied NAND folders and take up visible space.

Step 2 — Point GX at the EmuNAND

1. Back in Settings, open the path settings (Custom Paths / the EmuNAND-related paths) and set the EmuNAND Channel Path to the device and folder that received the dump — for example the SD card or the USB drive.
2. Set the EmuNAND Save Path deliberately too. GX separates where emulated channels live from where emulated save data is written. Pointing both at the same dumped NAND is the normal, predictable choice for most users.
3. In the loader settings, set the EmuNAND mode for channels so GX actually uses the emulated NAND for channel launching (options in this area distinguish between using EmuNAND for saves, for channels, or fully). Choose the mode that matches what you set above, then restart GX so the channel list refreshes.
4. Use the source/filter menu to enable the EmuNAND channels source. Your existing WiiWare and VC titles from the dump should now appear in the GX library alongside disc games, and can be launched from there.

Step 3 — Install WiiWare and VC Channels to EmuNAND

1. In Settings > Features, find GX’s Install WAD to EmuNAND style option (the WAD manager for EmuNAND). Point it at the WAD file for a title you own, stored on SD or USB.
2. Run the install. The channel is written into the emulated NAND on your SD/USB device — not into the console’s real NAND. That is the entire point of doing it this way.
3. Refresh the library (restart GX if the new channel does not appear immediately) and launch the channel once to confirm it starts and can create its save data.
4. Repeat per title. Install one, test one: a single bad WAD is much easier to identify that way than after a batch of ten.

Save Data: The Rules That Matter

The most common EmuNAND confusion is saves “disappearing.” Nothing disappeared — the save location simply depends on the mode. If a channel runs from EmuNAND, its saves are written to the EmuNAND save path; if the same channel is later launched from the real NAND (for example from the Wii Menu), it reads the real NAND saves instead, and the two sets diverge. Pick one home per channel and stick to it. Also note that some titles use save features that do not fully cooperate with emulation; if one specific game’s save behaves oddly, run that title from the real NAND rather than fighting it. Finally, back up the EmuNAND folder when you back up your drive — that folder now contains channels and saves that exist nowhere else.

EmuNAND channels and disc games coexist happily in the GX interface: enable the sources you use, keep the dumped NAND healthy, and WiiWare stops being a storage juggling act. For a different kind of channel work — installing the GX forwarder itself — see our separate forwarder channel guide, which is about the real NAND and follows different rules.

Frequently Asked Questions

What is the difference between EmuNAND Channel Path and EmuNAND Save Path?

The channel path is where the emulated NAND holding your WiiWare/VC channels lives; the save path is where save data for emulated content is written. Most users point both at the same dumped NAND on the same device, which keeps channels and their saves together and easy to back up.

My WiiWare game shows its old save, not my recent progress. Why?

You almost certainly launched it from the other NAND. A channel launched from the Wii Menu uses real-NAND saves; launched from GX with EmuNAND it uses EmuNAND saves. The saves are separate sets. Decide which NAND that channel lives on and always launch it the same way.

Can I delete the EmuNAND and start over?

Yes — delete the EmuNAND folder on the device, run Dump NAND again from Settings > Features, and reinstall any extra channels. Remember that deleting the folder also deletes the channels and saves stored only in EmuNAND, so copy anything you care about first.

Related Guides

• USB Loader GX Forwarder Channel (UNEO)
• Install WADs Safely with YAWM ME
• Nintendont in USB Loader GX — GameCube Setup
• Covers and GameTDB in USB Loader GX

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

Nintendo Wi-Fi Connection, the original online service for Wii games, shut down in 2014. Wiimmfi is the community-run replacement server project that has kept many of those games playable online ever since. USB Loader GX includes a Private Server setting that can point games at Wiimmfi instead of the dead Nintendo service, so titles like Mario Kart Wii and Super Smash Bros. Brawl can still find opponents — with no involvement from, and no endorsement by, Nintendo. This guide shows the GX-side setup, explains the waiting period new Wiimmfi profiles face, and sets honest expectations about which games still have a community.

Two ground rules before the steps. First, Wiimmfi is a fan project: be a good citizen on it, because the community and its moderators are the only reason it exists. Second, you need a legitimate copy of each game you play — Wiimmfi works with games launched from your own backups through GX, which is exactly the setup below. Make sure the loader itself is current via the Download page and the Setup Guide before changing online settings.

How the Private Server Setting Works

GX cannot rewrite a game’s networking code by itself. What it does is apply the Wiimmfi patch on the fly as the game launches: the game is redirected from Nintendo’s retired servers to Wiimmfi’s servers. In GX this is controlled per game and globally through the Private Server option. Setting it once globally is the convenient route if everything you play online goes through Wiimmfi; the per-game setting is there for the exception cases. No extra homebrew app needs to be installed for the GX method — the patching happens at launch.

Step-by-Step Setup

1. Confirm your console is online. In the Wii (or vWii) system settings, run a connection test on your Wi-Fi or wired connection. GX and the game both use the console’s normal internet connection; if the connection test fails, no server setting will save you.
2. Open GX global settings. In USB Loader GX, go to Settings and find the Loader Settings / features area that contains the Private Server option. Set it to Wiimmfi. On current r1283 builds this is a named option, not a manual server address you type in.
3. Or set it per game. Select a game in the list, open its individual game settings, and set Private Server to Wiimmfi there instead. Per-game is useful if you only want certain titles patched. If a per-game value and the global value disagree, the per-game value is the one that applies to that title — check it first when a single game refuses to connect.
4. Launch the game and create your profile. Start the game through GX as normal and go to its Nintendo WFC / online mode. Wiimmfi registers your console and profile on first connection and issues the friend code the game uses going forward.
5. Expect the waiting period on a new profile. Wiimmfi deliberately keeps newly registered profiles waiting before full online access is granted — historically this has been a matter of days (the project has used a seven-day wait for new consoles). This is an anti-abuse measure, not an error. If a brand-new profile cannot join matches yet but can connect, the correct action is to wait, not to reinstall anything.
6. Add friends by friend code, as in the original era. Wiimmfi keeps the original friend-code system. Exchange codes with people you actually want to play with, enter them in the game’s own friend roster, and both sides must register each other before private rooms work — exactly as Nintendo WFC behaved.

Which Games Still Have a Community?

Activity concentrates heavily in a few famous titles. Mario Kart Wii is Wiimmfi’s flagship — it has the largest and most consistent player base, including the well-known community distributions built around it. Super Smash Bros. Brawl retains a dedicated, smaller community. Beyond those two, availability thins out quickly: many supported games are technically connectable but only see players when sessions are organised in advance through community forums or Discord servers. That is the honest picture — Wiimmfi keeps the infrastructure alive for a long list of titles, but spontaneous matchmaking really only exists for the biggest one or two. If a quieter game matters to you, organising a session with friends (each on Wiimmfi, codes exchanged) is the reliable way to play it, rather than waiting alone in an empty lobby.

Rules and Etiquette That Keep You Unbanned

Wiimmfi is moderated. Cheating in online races or matches — including using cheat codes through the Ocarina engine in online play — is the fastest route to a ban, and bans can apply to your console. Keep Ocarina off for online titles (our Ocarina guide explains the per-game switch), race clean, and do not use modified game files that change gameplay in public rooms. Treat the service as borrowed community infrastructure, because it is.

If It Does Not Connect

Work in this order: console connection test passes; Private Server set to Wiimmfi globally or per game (and no conflicting per-game value); the waiting period for new profiles has passed; and the game itself is one Wiimmfi supports. An error at the game’s own connection screen with everything above correct is worth checking against Wiimmfi’s own status information, since server-side issues do happen and no local setting fixes them.

Frequently Asked Questions

Do I need to patch my game ISO to use Wiimmfi with USB Loader GX?

No. With the Private Server option set to Wiimmfi, GX applies the redirection when the game launches. You do not need to modify your backup image, and you should keep a clean backup — patching is only needed for methods that do not involve a loader.

Why can my new profile connect but not play online yet?

Wiimmfi applies a waiting period to newly registered consoles/profiles as an anti-abuse measure. During the wait you may be able to connect but not fully participate. It expires on its own; reinstalling GX or recreating the profile only restarts the clock, so patience is the actual fix.

Is Wiimmfi an official Nintendo service?

No. Nintendo Wi-Fi Connection closed in 2014. Wiimmfi is an independent, community-run replacement with no Nintendo affiliation or support. It works remarkably well for the games its community still plays, but availability and rules are the community’s, not Nintendo’s.

Related Guides

• Ocarina Cheats in USB Loader GX (keep them offline)
• Nintendont in USB Loader GX — GameCube Setup
• Install USB Loader GX on Wii
• Update USB Loader GX to r1283

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

Most “my GameCube games do not show up” problems are not broken downloads or broken loaders. They are folder problems. Nintendont — the application USB Loader GX hands GameCube games to — looks in exactly one place, with exactly one file name, and USB Loader GX uses the same layout to build its GameCube library. Get the structure right and games appear with correct names and covers; get one character wrong and a perfectly good backup stays invisible. This guide gives the exact layout, the two-disc rule, and what each GameCube file type means.

If Nintendont itself is not installed yet, do that first with our Nintendont setup guide, and make sure the loader is current from the Download page. This page is purely about how the game files themselves must be arranged.

The Exact Structure

On the SD card or USB drive that holds your GameCube games, the layout at the root of the first partition (which must be FAT32, or exFAT) is:

• /games/ — one folder at the device root, spelled exactly games, lower case.
• /games/Game Name [GAMEID]/ — one subfolder per game. The name part is for you; the six-character Game ID in square brackets is what GX and GameTDB use to identify the game for its correct title and cover art. Example: /games/The Legend of Zelda The Wind Waker [GZLE01]/
• /games/Game Name [GAMEID]/game.iso — the game image itself, renamed to exactly game.iso, whatever it was called originally.
• /games/Game Name [GAMEID]/disc2.iso — only for the second disc of a two-disc game, placed in the same folder as game.iso.

Step by Step: Adding a Game Correctly

1. Start from your own backup. Rip or use a backup of a game you own. A clean, full GameCube ISO is 1.35 GB for a single disc; a much smaller file is either a compressed/scrubbed format (see below) or an incomplete dump.
2. Find the Game ID. The six-character ID (for example GM4E01 for the US release of Mario Kart: Double Dash!!) is stored inside the image and listed on GameTDB. GX can also read it from the image itself, but including it in the folder name makes identification — and therefore covers and correct titles — far more reliable.
3. Create the folder. Inside /games/, create one folder per game using the pattern Name [ID]. Keep the brackets and the ID exactly as shown; do not add disc numbers or region notes inside the brackets.
4. Rename and copy the image. Rename the image to game.iso and place it inside that folder. For a two-disc game, rename the second disc to disc2.iso and place it in the same folder — never in a second game folder of its own.
5. Refresh GX. In USB Loader GX, make sure the GameCube source is enabled in the filter menu, then let the loader rescan. The game should now appear; download its cover with the method in our covers and GameTDB guide.
6. Launch once and let Nintendont create its files. The first launch creates the emulated memory card file alongside the game. After that first successful run, leave those generated files alone — deleting them deletes your saves.

File Types You Will Meet: .iso, .gcm and .ciso

.iso is the standard GameCube disc image and the format this structure assumes. If your backup is a full ISO, game.iso is all you need. .gcm is an older GameCube image extension from early dumping tools; the data is essentially the same kind of image, and for this layout the practical approach is to treat a genuine full-size .gcm as an ISO — place it in the game folder renamed to game.iso. .ciso is a compressed ISO: compression removes the padding data from the image to save space. Nintendont can read compressed images, but a compressed image must still follow the same folder and naming rules, and some homebrew tools are fussier about compressed images than about plain ISOs. When in doubt — and especially when a game misbehaves — a plain, full ISO is the baseline to test with before blaming the loader.

How This Differs from the /wbfs/ Folder

Wii games and GameCube games live in completely separate structures, and mixing them up is the second most common layout mistake. Wii backups belong in a /wbfs/ folder, usually managed by Wii Backup Manager, stored as .wbfs files (or split .wbfs/.wbf1 pairs on FAT32) inside their own Name [ID] subfolders. GameCube games belong in /games/ as game.iso. A GameCube ISO dropped into /wbfs/ will not be listed as a GameCube game, and a Wii game placed in /games/ will not be listed as a Wii game. The two loaders-within-the-loader genuinely do not look in each other’s folders. Keep both trees on the same drive if you like — just keep them separate.

Quick Troubleshooting Checklist

Game missing from the GX list? Work down this list before re-downloading anything: the GameCube source filter is enabled; the folder is at the root and spelled games; the image inside is named exactly game.iso; the device’s first partition is FAT32 or exFAT; the image is a complete backup (a truncated copy from an interrupted transfer is a classic cause); and GX has been restarted or rescanned since the files were added. Nine times out of ten, one of those six checks is the whole fix. If games list correctly but fail to start, the problem has moved from layout to Nintendont itself — return to the Nintendont setup guide and test the same game by launching Nintendont directly from the Homebrew Channel.

Frequently Asked Questions

Does the folder name have to include the Game ID in brackets?

Strictly, Nintendont mainly needs game.iso inside a subfolder of /games/. But the [ID] in the folder name is what USB Loader GX and GameTDB use to identify the exact game and region, which drives correct titles and cover art. Always include it — it costs nothing and prevents misidentified games.

Where does the second disc of a two-disc game go?

In the same folder as the first disc, renamed to disc2.iso. Do not create a separate folder for disc two and do not name it game2.iso. Nintendont handles the disc swap using that exact file name.

Can GameCube and Wii games share one drive?

Yes. Keep Wii games under /wbfs/ and GameCube games under /games/ on the same FAT32 (or exFAT, for the GameCube side) partition. The loaders read their own folders and ignore the other one.

Related Guides

• Nintendont in USB Loader GX — Full Setup
• Covers and GameTDB in USB Loader GX
• Loading Wii Games from SD Card
• Install USB Loader GX on Wii

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

USB Loader GX does not run GameCube games by itself. It acts as the front end — the cover-based library you browse — and hands the actual work to Nintendont, the homebrew application by FIX94 that runs GameCube games in Wii mode. Understanding that split explains most setup mistakes: GX finds and lists the games, Nintendont loads them, controls the controllers, and emulates the memory card. This guide sets up both halves correctly on a Wii or in Wii U vWii, from installing Nintendont into its own apps folder to the per-game settings that matter.

Nintendont is not an emulator in the usual sense. It runs GameCube code natively in the Wii’s Wii mode by translating GameCube calls to Wii equivalents, which is why compatibility and speed are so strong on original hardware. It supports emulated memory cards, Bluetooth controllers such as the Wii Classic Controller and Wii U Pro Controller, USB HID controllers, the official GameCube controller adapter, cheat codes, and optional widescreen and progressive-scan forcing. None of that works, however, until GX knows where Nintendont lives and your games follow the folder structure Nintendont expects.

What You Need

• A Wii or Wii U vWii with USB Loader GX r1283 already working — if it is not installed yet, follow the Setup Guide first and get the files from the Download page.
• Nintendont itself: Nintendont on GitHub (official, FIX94). A backup copy is available as Mirror (Terabox).
• An SD card and/or USB drive whose first partition is FAT32 (or exFAT) — Nintendont requires this for the device that holds GameCube games.
• Your own GameCube game backups in ISO form, organised as described in step 3 and in detail in our GameCube folder structure guide.
• A controller Nintendont supports: an original GameCube controller, a Classic Controller or Wii U Pro Controller over Bluetooth, a USB HID gamepad, or GameCube controllers through the official adapter.

Step-by-Step Setup

1. Install Nintendont as its own Homebrew Channel app. Download Nintendont from the official link above and extract it. Copy the nintendont folder into the apps folder on your SD card so the path is SD:/apps/nintendont/boot.dol, with its meta.xml and icon.png alongside. Do not put Nintendont inside the usbloader_gx folder — GX looks for it as a separate app.
2. Test Nintendont on its own first. Launch it once directly from the Homebrew Channel. If Nintendont itself opens and shows its menu, the install is good. If it does not appear in the Homebrew Channel, the folder structure is wrong — fix that before touching any GX setting.
3. Place your GameCube games correctly. On the SD card or USB drive, create a games folder at the root. Each game goes in its own subfolder named with the game name and its six-character Game ID in brackets, and the image must be named exactly game.iso — for example /games/Mario Kart Double Dash!! [GM4E01]/game.iso. Two-disc games add the second disc as disc2.iso in the same folder. GX and Nintendont both rely on this layout; a bare ISO at the drive root will not be listed.
4. Tell GX to show GameCube games. Open USB Loader GX, open the source/filter menu (the icons along the top of the game list), and make sure the GameCube source is enabled alongside Wii games. If the GameCube source is off, your correctly placed games stay invisible even though Nintendont is installed.
5. Set the GameCube loader in GX settings. Go to Settings, then the GameCube section, and confirm the GameCube mode/loader is set to Nintendont (not DIOS MIOS and not Devolution, both long-abandoned alternatives). Also confirm the Nintendont path points at the device holding apps/nintendont if GX offers a path option on your build.
6. Configure memory card emulation. In the same GameCube settings — or per game, by selecting a game and opening its GameCube options — enable the emulated memory card (often labelled Memcard Emulation). Nintendont creates a virtual card file on the same device as the game. Per-game cards are the safer choice for large libraries; a shared card is fine for a handful of titles. Keep the card size modest unless a specific game asks for more, and never delete the card file while experimenting with other settings.
7. Choose your controller. Original GameCube controllers plug straight into a Wii with GameCube ports, or through the official GameCube adapter. Bluetooth controllers such as the Classic Controller and Wii U Pro Controller pair through the Wii’s normal Bluetooth and are picked up by Nintendont directly. USB HID controllers connect to a free USB port. If you need hardware, a genuine-style GameCube controller and the official GameCube controller adapter are the two pieces most vWii owners need, because the Wii U has no GameCube ports of its own.
8. Launch a first game and keep the defaults. Select a GameCube game in GX and start it. GX hands over to Nintendont, which shows its own brief loading screen. For the first test, leave video options on default/auto — forced widescreen and forced progressive scan are per-game experiments for later, not part of a first working setup.
9. Adjust per game, not globally, after that. Back in GX, open a game’s individual settings to change only that title: memory card behaviour, video mode, widescreen patching, or cheat settings (see our Ocarina cheats guide). Avoid global changes — they tend to break games that were already working.

Common Problems

If GameCube games do not appear in GX at all, check the GameCube source filter first, then the /games/Name [ID]/game.iso structure character by character, then confirm the device’s first partition is FAT32 or exFAT. If a game appears but boots to a black screen, launch Nintendont directly from the Homebrew Channel and start the same game there: if it fails there too, the problem is the image or a Nintendont setting, not GX. If controllers do not respond in-game, remember GameCube games need a controller Nintendont supports — the Wii Remote alone is not a GameCube controller.

Disclosure: some links on this page are affiliate links. See our Affiliate Disclosure for how they work — they never change which settings or steps we recommend.

Frequently Asked Questions

Do I still need Nintendont if USB Loader GX lists my GameCube games?

Yes. Listing a game and running it are two different jobs. GX is the front end; Nintendont does the actual work of running GameCube games in Wii mode, including memory card emulation and controller handling. Without Nintendont installed in apps/nintendont, GameCube titles have nothing to launch with.

Can Nintendont and USB Loader GX be on different devices?

They can, but the simplest layout keeps Nintendont on the SD card in apps/nintendont and the games on either the SD card or a USB drive whose first partition is FAT32 or exFAT.

Does Nintendont work on Wii U vWii as well?

Yes. The same Nintendont install works inside vWii, and it is the standard way to play GameCube backups on a Wii U. On vWii you will typically use a Classic Controller, Wii U Pro Controller, USB HID pad, or GameCube controllers through the official adapter.

Related Guides

• GameCube Games Folder Structure — /games/ [ID]/game.iso
• Covers and GameTDB in USB Loader GX
• Install USB Loader GX on Wii U (vWii)
• Loading Wii Games from SD Card in USB Loader GX

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