The Wii U sold just 13.56 million units before Nintendo discontinued it on January 31, 2017, making it the company’s lowest-selling home console ever – but the small library it left behind includes some of the best games Nintendo has ever shipped, from The Legend of Zelda: Breath of the Wild to Mario Kart 8. Cemu is the open-source emulator that brings that library to modern Windows, Linux, and macOS machines, often at 4K and well above the console’s native frame rate. The project has 9,534 stars on GitHub and active near-daily commits as of this writing. This guide walks through a complete, legal Cemu setup in 12 steps: installing the emulator, understanding its folder structure, dumping your own Wii U games, choosing a graphics API, installing graphic packs, configuring a controller, and connecting to Pretendo Network for online play. Budget 30 to 45 minutes for the full walkthrough if you already have a Wii U to dump from.
What Is Cemu?
Cemu debuted on October 13, 2015, as a closed-source Windows-only project built by developers known as Exzap and Petergov. It started as what Wikipedia describes as a proof-of-concept, capable of booting Mario Kart 8 and The Legend of Zelda: The Wind Waker HD but initially missing GamePad support and audio entirely. The project stayed proprietary for nearly seven years, which drew criticism from other emulator authors who felt Cemu benefited from techniques pioneered by open projects without contributing back.
Two moments changed Cemu’s trajectory. The first came in March 2017, when Cemu ran Breath of the Wild within hours of its console release – a feat that reportedly pushed the project’s Patreon funding from a modest baseline to around $22,317 a month, according to Wikipedia’s sourced history of the project. The second came in August 2022, when version 2.0 finally open-sourced the entire codebase under the Mozilla Public License 2.0, added the first official Linux builds, and introduced built-in Pretendo Network support for online play. macOS builds followed later. The current stable release, version 2.6, shipped February 6, 2025, and despite no new tagged release in the time since, the GitHub commit history shows active work on Vulkan fixes and CPU-recompiler improvements through at least July 2026.
Technically, Cemu emulates the Wii U’s custom tri-core PowerPC “Espresso” CPU and its AMD Radeon-derived “Latte” GPU at a low level. Community-built Graphic Packs – text-based mod files that intercept and adjust a game’s rendering pipeline – are what let Cemu push resolutions far past the Wii U’s native 720p-ish output and unlock frame rates above the original 30 or 60 FPS caps. The same community proved this early: mods that doubled Breath of the Wild‘s native 30 FPS to a smooth 60 FPS circulated within Cemu’s community not long after the emulator could run the game at all.
Is Cemu Legal? Wii U Game Dumps and Copyright
Emulator software itself is legal in most jurisdictions – courts in the US and elsewhere have repeatedly held that emulators are legal so long as they don’t contain copyrighted firmware or code lifted from the original hardware. Cemu, like Dolphin and PCSX2, is a clean-room implementation released under an open-source license, and using it is not in question. The gray area, as with any console emulator, is where the games come from.
The safest and most defensible approach is to dump games you personally own directly from your own Wii U, which this guide covers in Step 4. Downloading ROMs from the internet is a different matter legally in most countries, even for games you already own physical copies of, and this guide does not cover or endorse it.
It’s worth understanding why Cemu has never faced the legal pressure that hit two prominent Nintendo Switch emulators. In March 2024, Yuzu’s developer, Tropic Haze, agreed to pay Nintendo $2.4 million and shut the project down entirely, after Nintendo blamed the emulator for mass piracy of The Legend of Zelda: Tears of the Kingdom ahead of its release. Nintendo followed up in October 2024 by contacting Ryujinx’s lead developer directly; the project shut down and removed its GitHub repositories shortly after. Both cases involved a console Nintendo was still actively selling and profiting from. The Wii U, by contrast, has been fully discontinued since January 2017, its eShop has not accepted new purchases since March 27, 2023, and Nintendo has never targeted Cemu, Dolphin, or PCSX2 – all of which emulate consoles Nintendo and Sony no longer sell.
Cemu System Requirements for 2026
Cemu’s official requirements, published on cemu.info, are modest compared to most modern PC games, since the Wii U itself topped out at roughly Xbox 360-class hardware. The table below combines the official minimums with the community-recommended CPU tier for smooth full-speed emulation.
| Component | Minimum | Recommended |
|---|---|---|
| Operating System | Windows 7 x64 or later | Windows 11, Ubuntu 22.04+, or macOS 12+ |
| CPU | Any 64-bit x86 CPU | AMD Ryzen 3 or Intel Core i5 or better (single-core speed matters more than core count) |
| GPU / Graphics API | OpenGL 4.5 | Vulkan 1.2-capable GPU (recent NVIDIA or AMD card) |
| RAM | 4GB | 8GB or more |
| Other software | Microsoft Visual C++ 2017 x64 Redistributable (Windows only) | Latest GPU drivers |
| Storage | A few hundred MB for Cemu itself | Several GB free per dumped Wii U title, plus space for graphic packs |
Intel integrated graphics can run Cemu, but performance is inconsistent and Vulkan is strongly preferred over OpenGL on Intel hardware if you have the choice. Apple Silicon Macs run Cemu through the macOS build, though translation overhead means M-series chips should be treated as closer to the “recommended” tier than the minimum one for a comfortable experience.
What You Need Before You Start
- A Windows, Linux, or macOS PC that meets the requirements above
- A Wii U console you own, powered on and connected to the internet (needed once, for Step 4)
- A USB drive or SD card, at least 32GB recommended, formatted FAT32 with a 32KB (32768-byte) allocation unit size
- The Microsoft Visual C++ 2017 x64 Redistributable installed (Windows users only)
- A supported controller if you don’t want to play with a keyboard: Xbox, PlayStation, or Switch Pro controllers all work as generic input devices
- Roughly 30-45 minutes, most of which is spent dumping and decrypting your own games
Step 1: Download and Install Cemu
Download Cemu only from its official GitHub releases page or cemu.info. Several lookalike domains rank in search results for “Cemu download” that are not affiliated with the cemu-project team – treat any site other than github.com/cemu-project or cemu.info as unverified, and never run an installer from one. The official release ships four build types: a Windows x64 zip, an Ubuntu 22.04 x64 zip, a macOS .dmg, and a generic Linux AppImage that works across most modern distributions.
# Windows – after downloading cemu-2.6-windows-x64.zip
# Right-click the zip > Extract All, to a folder OUTSIDE Program Files
# e.g. C:\Emulation\Cemu
# Linux – AppImage method (works on most distros)
chmod +x Cemu-2.6-x86_64.AppImage
./Cemu-2.6-x86_64.AppImage
# Linux – Ubuntu 22.04 zip method
unzip cemu-2.6-ubuntu-22.04-x64.zip -d ~/Emulation/Cemu
cd ~/Emulation/Cemu && ./Cemu.sh
On Windows, avoid extracting Cemu into Program Files or any other folder that requires administrator rights to write to – Cemu needs to write its settings, cache, and (by default) its emulated storage into its own directory tree, and admin-protected folders cause permission errors down the line. If you do end up needing elevated permissions for a specific peripheral driver, right-click Cemu.exe, open Properties, and enable “Run this program as an administrator” from the Compatibility tab rather than moving the whole install.
Step 2: Set Up Portable Mode and Folder Structure
By default on Windows, Cemu now stores its settings and emulated Wii U storage in %appdata%\Roaming\Cemu, separate from wherever you extracted the program. Most users setting up a dedicated emulation folder prefer portable mode instead, which keeps everything – program, settings, and saves – in one self-contained folder that’s easy to back up or move to another PC.
To enable it, per the official Cemu Wiki, create a folder literally named portable in the same directory as Cemu.exe. Cemu detects this folder on launch and stores the mlc01 emulated-storage directory and all settings inside it instead of your Windows user profile.
# Windows (PowerShell) – from inside your Cemu folder
New-Item -Path ".\portable" -ItemType Directory
# Linux / macOS
mkdir ./portable
Launch Cemu once after creating this folder. It will generate its internal directory structure (including mlc01, graphicPacks, and controllerProfiles) inside portable automatically.
Step 3: Understand the mlc01 Emulated Storage Folder
mlc01 is the root of Cemu’s emulated Wii U internal storage – the same role the Wii U’s built-in flash memory and any expanded USB storage played on real hardware. It’s where save games, installed system updates, and any DLC you’ve dumped and installed all live. Understanding this folder up front makes later steps – especially adding games and installing updates – much less confusing.
Cemu/
├─ Cemu.exe
├─ portable/
│ ├─ mlc01/
│ │ ├─ usr/ # installed titles, DLC, updates
│ │ ├─ sys/ # system files (from Dumpling, for online play)
│ │ └─ emulatorSave/ # save data
│ ├─ graphicPacks/ # community graphic packs go here
│ ├─ controllerProfiles/
│ └─ settings.xml
└─ keys.txt # optional, for future use
You don’t need to create any of this by hand – Cemu builds the full tree automatically the first time it runs in portable mode. It’s worth knowing the layout, though, since several later steps (installing graphic packs, copying Pretendo’s sys and usr folders, backing up saves) all mean placing files inside specific parts of this tree.
Step 4: Dump Your Own Wii U Games with Dumpling
This is the step that makes the rest of the setup legal and legitimate: extracting game data directly from a Wii U you own, rather than downloading it from a third party. The community tool for this is Dumpling, a browser-based dumping tool that runs entirely on the Wii U itself and requires no permanent modification to the console.
- Format your USB drive or SD card as FAT32 with a 32KB (32768-byte) allocation unit size – the default allocation size Windows picks for large drives will not work.
- Insert the storage device into your powered-on Wii U and log into your Nintendo Network ID.
- Open the Wii U’s built-in web browser and navigate to
dumplingapp.com. - Follow the on-screen instructions, select the games (and, if you want online play, the “Online Files” option) you want to dump, and press start.
- Wait for the dump to finish – larger games can take a while over USB 2.0.
Once finished, your storage device will contain encrypted game dumps, plus – if you selected it – an “Online Files” folder holding otp.bin and seeprom.bin, along with sys and usr subfolders. You’ll use the encrypted game dumps in Step 5 and the online files in Step 11.
Step 5: Decrypt Your Game Dumps
Dumpling’s output is still encrypted with the per-console keys the Wii U uses internally, so it needs one more pass through a decryption tool – commonly CDecrypt – before Cemu can load it. Run it against each dumped title folder on your PC:
# Windows (from a Command Prompt or PowerShell)
cdecrypt.exe "D:\Dumps\MarioKart8" "D:\Decrypted\MarioKart8"
# Linux
./cdecrypt "/media/usb/Dumps/MarioKart8" "~/Decrypted/MarioKart8"
A successful run produces a code, content, and meta folder inside your output directory – that three-folder structure, containing a .rpx file somewhere under code, is what Cemu actually loads. If any of the three folders is missing or the tool exits with an error partway through, re-dump the title rather than trying to load a partial decrypt; Cemu will typically fail to boot the game or crash partway through a level if the data underneath is incomplete.
Step 6: Add Games to Cemu’s Game List
With a decrypted title folder in hand, open Cemu and go to File > Install game if you have a title update or DLC package to merge in, or simply add the base folder to Cemu’s game paths: Options > Game paths, then Add and select the parent folder containing your decrypted titles (not each individual game folder – point it at the folder one level up, and Cemu will scan for every valid title underneath). Once added, your games appear as icons in Cemu’s main window, each showing the title’s icon, region, and current compatibility notes if any are on file.
You can check community-reported compatibility for any title before playing at the official Cemu Compatibility List, which rates games across five tiers – Perfect, Playable, Runs, Loads, and Unplayable – and the Cemu Wiki’s game database, which documents roughly 1,213 individual title pages. Well-known titles like Breath of the Wild, Mario Kart 8, and Xenoblade Chronicles X have long-standing Perfect or Playable ratings and are good first games to try.
Step 7: Choose Vulkan or OpenGL as Your Graphics API
Cemu supports two graphics backends, selectable under Options > General settings > Graphics. Picking the right one for your hardware has a bigger impact on stability and shader-compilation stutter than almost any other setting in the emulator.
| API | Best for | Notes |
|---|---|---|
| Vulkan | Recent NVIDIA and AMD GPUs (GTX 900-series / RX 400-series and newer) | Supports async shader compilation, generally lower stutter, actively prioritized by Cemu’s developers |
| OpenGL | Older GPUs, some Intel integrated graphics, GPUs with under 2GB VRAM | Broader compatibility floor, but no async shader compilation and typically more stutter on first shader compiles |
If your GPU supports Vulkan 1.2, use it as your default. The v2.6 changelog specifically reworked custom scaling-shader support to behave correctly under Vulkan, and most active graphic pack development in the Cemu community targets Vulkan first.
Step 8: Install Graphic Packs for 4K Upscaling
Graphic packs are community-maintained, text-based mod files (using a rules.txt format) that intercept a game’s native rendering calls to raise internal resolution, unlock frame-rate caps, and fix specific visual bugs. They’re maintained in the official cemu-project/cemu_graphic_packs repository, and there are two ways to install them.
- Built-in downloader (recommended): In Cemu, go to Options > Download community graphic packs. This pulls the latest packs directly from the official repository – a feature that’s been part of Cemu since version 1.15.1.
- Manual install: Download the graphic packs release archive matching your Cemu version from the repository’s releases page, extract it, and copy the resulting folders into your
graphicPacksdirectory insideportable/(or%appdata%\Cemu\graphicPacksif you’re not using portable mode).
# Manual method, from your Cemu folder
Expand-Archive cemu_graphic_packs.zip -DestinationPath .\portable\graphicPacks -Force
Once installed, open Options > Graphic packs from Cemu’s main window, find your game in the list, and tick the boxes for the resolution or fix you want – most popular titles ship with multiple selectable resolution options (1080p, 1440p, 4K, and sometimes higher) plus separate toggles for things like FPS++ patches. Only enable one resolution option per game at a time; stacking conflicting graphic packs is one of the most common causes of broken textures, which this guide covers under Common Pitfalls below.
Step 9: Configure Controller Input
Cemu natively understands the Wii U GamePad, Wii U Pro Controller, and Classic Controller input layouts, with partial Wii Remote support. In practice, almost everyone plays through a generic controller – Xbox, DualShock/DualSense, or a Switch Pro Controller – mapped onto one of those native layouts, plus keyboard and mouse as a fallback input device.
- Open Options > Input settings.
- Under Emulated Controllers, choose Wii U GamePad for most single-player games, or Pro Controller for games that support it (this avoids emulating the GamePad’s second screen, which most games don’t need).
- Click into each emulated controller’s slot, select your physical controller from the API dropdown (XInput is the simplest choice for Xbox-style pads on Windows), and either load a default profile or map each button manually.
- Test every input, including analog stick deadzones, before closing the dialog.
The Wii U GamePad’s touchscreen is mapped to left mouse clicks by default, and gyro/motion controls are mapped to holding the right mouse button and dragging, or to your physical controller’s built-in gyro if it has one and you’ve enabled it in the input profile.
Step 10: Add Cemuhook for Motion Controls and Mods
Cemuhook is a widely-used community add-on that layers extra functionality on top of Cemu – most notably H.264 video decoding support and compatibility with popular performance mods like FPS++, which unlocks certain games’ internal frame-rate cap beyond their console default. It is not required for basic play, but it’s a near-universal recommendation in Cemu communities for anyone chasing higher frame rates.
# Download the Cemuhook build matching your installed Cemu version,
# then extract its contents into the SAME folder as Cemu.exe
# (do not create a subfolder – the DLLs must sit alongside Cemu.exe)
After installing, restart Cemu and confirm the option appears under the relevant game-specific settings before assuming it’s active – not every graphic pack or mod that mentions Cemuhook actually requires it, so only install it if a specific mod you want calls for it.
Step 11: Connect to Pretendo Network for Online Play
Nintendo shut down the Wii U’s original online infrastructure years ago, so multiplayer and online features in Cemu run through Pretendo Network, a community-run project that reimplements Nintendo’s old Network Station services. Cemu has had built-in Pretendo support since version 2.0 in 2022, and setup only takes a few steps once you have the “Online Files” you dumped in Step 4.
- Create a free Pretendo Network ID (PNID) at Pretendo’s own signup page.
- Copy
otp.binandseeprom.binfrom your dumped “Online Files” folder into your main Cemu directory. - Copy the
sysandusrfolders from “Online Files/mlc0” into yourmlc01folder, merging with the existing structure. - In Cemu, open Options > General settings > Account, select your active account, and under Network Service choose Pretendo Network.
- Log in with your new PNID when prompted.
One important warning from Pretendo’s own documentation: never use the same PNID on a real Wii U and in Cemu at the same time. Most games treat simultaneous logins from the same account as suspicious activity, and it can get you disconnected from matches or, in some cases, temporarily banned from Pretendo’s services. Miiverse-style social features are only partially supported through Pretendo and shouldn’t be expected to work identically to how they did in 2017.
Step 12: Launch and Play Your First Game
Double-click a game icon in Cemu’s main window, or select it and press Start. The very first launch of any title compiles that game’s shaders, which shows up as a progress bar and, on Vulkan with async shader compilation enabled, brief stutter the first time a new visual effect appears rather than a long loading screen up front. Subsequent launches are much faster since compiled shaders are cached to disk.
A healthy first boot looks roughly like this in Cemu’s log window:
[General] Loading game profile
[GFX] Vulkan device: NVIDIA GeForce RTX … selected
[CoreInit] Title ID: 0005000E10101C00
[GX2] Shader cache loaded: 1,842 entries
[Audio] Using Cubeb audio backend
Game booted successfully
If instead you see repeated [GFX] Pipeline compilation failed lines or the window closes immediately after the Cemu logo, jump to the Troubleshooting section below before assuming your dump is bad – most first-boot failures trace back to a graphics-API mismatch or a missing redistributable rather than the game files themselves.
Hardening Your Cemu Setup
Emulator setups don’t carry the same network-exposure risk as a dedicated game server, but Cemu’s ecosystem still has a handful of real, well-documented risk points worth closing off.
- Only ever download Cemu from github.com/cemu-project or cemu.info. Search results for “Cemu download” and “Cemu setup” surface multiple lookalike domains that are not run by the Cemu team; treat installers from any other source as untrusted, and never disable your antivirus to “make it work” – that’s a common social-engineering trick used to distribute malware bundled with unofficial emulator builds.
- Only install graphic packs from the official repository (github.com/cemu-project/cemu_graphic_packs) or Cemu’s built-in downloader. Graphic packs are plain text and generally safe, but third-party “custom” pack collections shared on Discord servers and forums bypass the review process the official repo benefits from.
- Use a unique password for your Pretendo Network account. It’s a separate, independently-run authentication system from your actual Nintendo Account, so credential reuse across the two only expands your exposure if either service is ever compromised.
- Keep your dumped game files and BIOS-equivalent system files backed up but private. Your
otp.binandseeprom.binare tied to your specific Wii U console’s hardware identity – treat them the same way you’d treat any other device-specific credential, and don’t upload them anywhere public. - Run Cemu with standard user permissions unless a specific controller driver genuinely requires administrator rights. There’s rarely a good reason for an emulator to need elevated privileges for normal play.
A Complete, Repeatable Cemu Setup Script
If you’re setting Cemu up on more than one machine, or rebuilding after a reinstall, this PowerShell script automates the parts of the process that don’t require your own dumped games or console-specific files – downloading the emulator, extracting it, and building the portable folder structure. You’ll still need to complete Steps 4, 5, and 11 by hand, since those depend on files unique to your own Wii U.
# cemu-setup.ps1 – run from PowerShell on Windows
$version = "2.6"
$installDir = "C:\Emulation\Cemu"
$zipUrl = "https://github.com/cemu-project/Cemu/releases/download/v$version/cemu-$version-windows-x64.zip"
$zipPath = "$env:TEMP\cemu-$version.zip"
New-Item -Path $installDir -ItemType Directory -Force | Out-Null
Write-Host "Downloading Cemu $version..."
Invoke-WebRequest -Uri $zipUrl -OutFile $zipPath
Write-Host "Extracting..."
Expand-Archive -Path $zipPath -DestinationPath $installDir -Force
Write-Host "Enabling portable mode..."
New-Item -Path "$installDir\portable" -ItemType Directory -Force | Out-Null
Write-Host "Creating graphic packs folder for later..."
New-Item -Path "$installDir\portable\graphicPacks" -ItemType Directory -Force | Out-Null
Remove-Item $zipPath
Write-Host "Done. Launch Cemu.exe once to finish generating folders, then:"
Write-Host " 1. Dump your own Wii U games with Dumpling (Step 4)"
Write-Host " 2. Decrypt them with CDecrypt (Step 5)"
Write-Host " 3. Add them under Options > Game paths (Step 6)"
Update the $version variable whenever a new Cemu release ships, and verify the download URL against the official releases page before running it, since GitHub’s release-asset URL structure occasionally changes between major versions.
Common Pitfalls When Setting Up Cemu
- Downloading Cemu from a clone site. Several domains that are not affiliated with the cemu-project team rank for “Cemu download” searches and bundle unwanted software with their installers. Stick to GitHub or cemu.info.
- Formatting your dump drive as exFAT or NTFS instead of FAT32. Dumpling and the Wii U’s own browser expect FAT32 with a 32KB allocation unit – anything else will fail partway through the dump or won’t be recognized by the console at all.
- Skipping CDecrypt and trying to load raw Dumpling output. Cemu cannot read encrypted dumps directly; skipping the decryption step is the single most common reason a “successfully dumped” game won’t appear in Cemu’s list.
- Stacking multiple resolution graphic packs on the same game. Enabling more than one conflicting resolution or texture pack for the same title is a frequent cause of broken or purple/black textures – enable one resolution option per game at a time.
- Expecting native save states. Unlike PCSX2 or Dolphin, Cemu has no built-in save-state system; the long-standing tracking issue on GitHub notes that a save state would need to dump all active RAM, and Wii U titles commonly use 2-8GB, which makes the feature impractical with Cemu’s current architecture. Save inside the game itself, the same way you would on real hardware.
- Using the same Pretendo account on a real Wii U and Cemu simultaneously. This routinely triggers anti-cheat or anti-fraud logic in individual games and can get an account temporarily restricted.
- Installing Cemu inside Program Files. Windows’ folder permissions there can silently block Cemu from writing its settings or shader cache, leading to settings that don’t save between sessions.
Troubleshooting Cemu: 10 Common Problems
| Problem | Likely Cause | Fix |
|---|---|---|
| Black screen after the Cemu logo | Graphics API mismatch for your GPU | Switch between Vulkan and OpenGL under Options > General settings > Graphics |
| “vcruntime140_1.dll is missing” on launch | Missing Windows redistributable | Install the Microsoft Visual C++ 2017 x64 Redistributable |
| Shaders recompile every single session | Shader cache folder deleted or on a network drive | Keep Cemu’s shader cache on a local drive and never clear it between sessions |
| Controller not detected | Wrong input API selected for your controller type | Reopen Options > Input settings and try XInput for Xbox-style pads, DirectInput for others |
| Game doesn’t appear after adding to game paths | Incomplete or still-encrypted dump | Re-run CDecrypt and confirm code/content/meta folders all exist |
| Crackling or choppy audio | Audio buffer size too small for your hardware | Increase the audio buffer size or switch audio API under sound settings |
| Purple or black textures in specific areas | Conflicting graphic packs enabled together | Disable all graphic packs for the title, then re-enable one resolution pack at a time |
| Low frame rate despite a capable GPU | Async shader compilation disabled, or “Accurate barriers” overhead | Enable async shader compilation (Vulkan only) and test disabling Accurate barriers for that title |
| A specific game crashes at the same point every time | Known compatibility issue with that title | Check the title’s page on compat.cemu.info for documented workarounds |
| Online play won’t connect | Pretendo files not copied correctly, or wrong network service selected | Re-check Options > Account > Network Service and confirm otp.bin/seeprom.bin are in the Cemu folder |
Advanced Tips for Cemu Power Users
Once the basic setup is stable, a few deeper options are worth exploring for specific games or use cases.
- Tune Accurate barriers per-game. This setting is enabled by default because it prevents rendering glitches in some titles, but it carries a real performance cost. If a specific game runs smoothly on other emulators or on real hardware footage but stutters in Cemu, test disabling it for that title specifically rather than globally.
- Automate game launches with command-line flags. Cemu supports
-g "path\to\game.rpx"to launch a specific title directly and-fto start in fullscreen, which is how community frontend projects like CemuLauncher build a game-picker UI on top of Cemu. This is useful if you want to add Cemu titles to a general-purpose game launcher like Playnite. - Keep multiple portable installs for different mod configurations. Because portable mode is just a folder, you can keep a “vanilla” Cemu install for stable, verified graphic packs and a second copy for testing romhacks or experimental patches, without either configuration interfering with the other.
- Report and check compatibility before assuming your setup is broken. The official compatibility database is community-maintained and actively updated; a game running poorly is sometimes a known, documented issue with the title itself rather than anything wrong with your configuration.
- Watch the GitHub commit history, not just release tags. Cemu hasn’t shipped a new version number since v2.6 in February 2025, but the project’s commit history shows near-daily work, meaning meaningful fixes can land well before the next tagged release.
Cemu vs Other Ways to Play Wii U Games in 2026
Cemu isn’t the only way to revisit the Wii U library, though it’s increasingly the most practical one now that Nintendo has stepped back from the platform entirely.
| Option | Cost | Visual upgrade over original | Status in 2026 |
|---|---|---|---|
| Cemu on PC | Free (you need your own dumped games) | Up to 4K+ and unlocked frame rates via graphic packs | Actively developed, 9,534 GitHub stars |
| Original Wii U hardware | Used-market only; console discontinued | None – native resolution only | eShop purchases ended March 27, 2023; redownloads of past purchases still work |
| Wii U digital library (already purchased) | N/A, sunk cost | None | Can still redownload and receive updates, per Nintendo’s own support page |
The eShop closure is worth sitting with for a moment: Nintendo confirmed that as of March 27, 2023, it’s no longer possible to buy anything new for the Wii U, though previously-purchased digital titles can still be redownloaded “for the foreseeable future.” That’s a narrower promise than it sounds – it depends entirely on Nintendo’s authentication servers staying online indefinitely, with no firm end date attached. A personal, legally-dumped backup running in an actively-maintained open-source emulator is the only version of your Wii U library that doesn’t depend on a third party’s server staying up.
Frequently Asked Questions
Is Cemu free?
Yes. Cemu has been fully open-source under the Mozilla Public License 2.0 since version 2.0 in August 2022, and the GitHub releases are free to download and use.
Is Cemu legal to use?
The emulator itself is legal, the same way Dolphin and PCSX2 are. The legal risk, as with any emulator, comes from how you obtain games – dumping titles from a Wii U you personally own is the defensible approach this guide covers; downloading ROMs from third parties is a different legal question this guide does not address.
Do I need to own a Wii U to use Cemu?
To play games legally, yes – you need your own Wii U to dump games from using Dumpling, as covered in Step 4. You don’t need to keep the console connected afterward except to re-dump additional titles or the online files.
What’s the difference between Cemu and Dolphin?
They emulate different, unrelated consoles. Cemu emulates the Wii U exclusively, while Dolphin emulates the GameCube and original Wii. Despite the Wii U’s backward compatibility with Wii software on real hardware, the two emulator codebases are entirely separate projects built around different CPU and GPU architectures.
Can Cemu run games at 4K and 60 FPS?
For many titles, yes, using community graphic packs installed in Step 8. Breath of the Wild is the best-known example, with community patches that double its native 30 FPS to 60 FPS alongside 4K resolution options, though results vary by game since each graphic pack is built and maintained separately for that specific title.
Does Cemu support save states?
No. Unlike PCSX2 or Dolphin, Cemu has no save-state system, tracked in a long-standing open GitHub issue. The technical blocker is RAM size: a save state needs to capture all active memory, and Wii U games commonly use several gigabytes, making the feature impractical with Cemu’s current design. Use each game’s own native save system instead.
Can I play Cemu games online?
Yes, through Pretendo Network, a community-run reimplementation of Nintendo’s original online services, covered in Step 11. You’ll need your Wii U’s dumped “Online Files” and a free Pretendo account, and you should never use the same account on a real Wii U and Cemu at the same time.
What GPU do I need for Cemu in 2026?
Officially, any GPU supporting OpenGL 4.5 or Vulkan 1.2. In practice, a Vulkan 1.2-capable NVIDIA or AMD GPU from the last several years, paired with a Ryzen 3 or Core i5-class CPU, comfortably handles the vast majority of the Wii U library at native or upscaled resolutions.
Related Coverage
- Dolphin Emulator: GameCube & Wii in 4K, 12 Steps
- PCSX2 Setup: 99% PS2 Compatibility in 12 Steps
- RetroArch: 100+ Cores in 12 Steps, 30 Min
- EmuDeck on Steam Deck: 20+ Emulators, 12 Steps
- Batocera 43.1 Setup: 200+ Systems, 12 Steps
- Batocera vs RetroPie vs Recalbox: 200+ Systems
For more emulation and retro-gaming coverage, visit the gaming section.




