Dolphin Emulator

Nintendo never put the GameCube or the Wii on a phone. Dolphin did, and it did it for free.

Dolphin Emulator is the reference emulator for two generations of Nintendo hardware. It began in 2003 as a closed Windows project, went open source in 2008, and has since become one of the most rigorously engineered pieces of emulation software in existence. The project is stewarded by Stichting Dolphin Emulator, a Dutch foundation that publishes the official Android build on Google Play, and its source code lives on GitHub under GPLv3. Anyone can read it, fork it, or audit it. That transparency is not a marketing line. It is the reason Dolphin has outlived every competitor and survived a public standoff with Nintendo in 2023, when Valve pulled the planned Steam release after Nintendo’s lawyers objected.

The Android build is not a toy port. It shares the core with the desktop version and ships monthly beta updates aligned with the project’s progress reports, which means a fix landing on Windows arrives on your phone within weeks. It carries the full feature set: save states, cheat codes, widescreen hacks, adjustable emulation speed, per-game controller profiles, custom texture packs, and a netplay system that turns couch-only multiplayer into online multiplayer. It also includes an Android TV interface, which matters more than it sounds. A Shield TV or a Chromecast with Google TV plugged into a living room set, paired with a Bluetooth controller, is a functional Wii replacement.

The market positioning is unusual because there is no market. Dolphin costs nothing, sells nothing, and contains no games. It asks you to bring your own ISO, RVZ, or WBFS files dumped from discs you own. That requirement filters the audience hard, and it explains the polarised reception a free emulator with no support desk inevitably gets: the experience is designed to scale with hardware, and a budget MediaTek phone sits on the wrong side of that divide. The difference is largely about the GPU driver underneath. One caution for iPhone owners: the “Dolphin Emulator - Basic” app on the iOS App Store is a third-party product unrelated to this project. The real thing exists only on Android among mobile platforms.

• Resolution scaling far beyond original hardware: Internal rendering at 2x, 3x, or higher turns 480p-era games into crisp 1080p or 1440p output, with anisotropic filtering and anti-aliasing layered on top. Wind Waker at native phone resolution can look better than it ever did on a CRT.
• Save states and speed control: Freeze and restore a game anywhere, then fast-forward through the grind. For a mobile session interrupted by a train stop, this is the feature that makes handheld GameCube viable at all.
• Real Wii Remote support over Bluetooth: Pair an actual Wiimote to your phone for motion-control games that were never designed for a touchscreen. The touch overlays exist as a fallback, but this is the correct way to play Wii titles.
• Per-game profiles for graphics and controls: Every title can carry its own backend, resolution, and input mapping. Dolphin remembers that Xenoblade needs Vulkan at 1x while Animal Crossing can run at 3x on OpenGL.
• Netplay: Online multiplayer for games that shipped with local-only play, synchronised across Dolphin clients. Smash Bros. Melee’s competitive scene runs on this infrastructure.
• Android TV interface and monthly betas: A leanback UI for televisions and a release cadence tied to the project’s public progress reports, both published by the developers themselves.

The onboarding problem is the point

Dolphin’s first-run experience is honest to the point of being unfriendly. The app opens to an empty game list and a folder picker. There is no tutorial, no bundled demo, no “try this game” prompt. You are expected to have already dumped your discs on a hacked Wii or a compatible disc drive, converted them to a sensible format, and copied them to your phone. If that sentence sounds like a chore, this app is not for you, and Dolphin makes no apology for it.

The onboarding friction is deliberate, not lazy. The project has spent two decades refusing to touch anything that looks like piracy facilitation, and that discipline is why it still exists on Google Play while a graveyard of other emulators does not. Once the folder is set, Dolphin scans it, pulls cover art and titles from the disc headers, and presents a clean grid. From that moment the experience improves sharply.

Settings are where the real game is played

The Android version exposes nearly the full desktop configuration surface: CPU core selection, dual-core mode, backend choice between OpenGL and Vulkan, internal resolution, texture cache accuracy, shader compilation modes, and dozens of hacks with names like “Skip EFB Access from CPU.” The average user will not know what half of these do. The average user will also, at some point, need one of them to make a specific game stop stuttering.

This is the tension at the heart of Dolphin on mobile. The desktop version can afford to be a power tool because desktop GPUs have mature drivers and headroom to spare. On Android, the correct settings vary by game, by SoC, and by driver version. Dolphin ships sensible defaults and per-game INI overrides that the community maintains, so many titles work out of the box. But the moment something misbehaves, you are reading wiki pages and toggling asynchronous shader compilation. The app does not hide this complexity, and that honesty is preferable to a dumbed-down alternative that would simply fail silently.

Save states change what a handheld GameCube means

Nintendo’s GameCube library was designed for sessions on a couch. Metroid Prime’s save rooms are twenty minutes apart. Dolphin’s save states collapse that design assumption. You can stop mid-boss, pocket the phone, and resume at the same frame an hour later. Combined with the speed slider, which lets you run at 200 percent through cutscenes and backtracking, this turns a console library into something structurally closer to a handheld one. The feature is not new to emulation, but on a phone it is transformative rather than convenient.

Netplay is impressive and impractical on mobile

Netplay synchronises inputs across clients with a configurable buffer, and for turn-based or slower games it is a genuine way to play Mario Party with someone in another city. On Android, though, latency from mobile wifi and the overhead of running the emulator at full speed while maintaining sync make it a niche capability. The feature exists for completeness and for parity with desktop. Most phone users will never open it, and that is fine.

Controls: bring hardware

The touch overlay is the weakest part of the package. It is functional, customisable, and entirely inadequate for anything requiring an analog stick and a shoulder button simultaneously. Dolphin knows this. The overlay is presented as a stopgap, and the real input story is Bluetooth: any standard gamepad maps cleanly, and a real Wii Remote pairs directly for motion games. A phone in a telescopic controller is, by design, a portable GameCube — a setup money cannot buy as a product, because you already own all the parts.

Aesthetically, the app is Material Design done competently and without ambition. The game grid is clean, the settings screens are dense but legible, and the in-game menu is a minimal overlay that gets out of the way. Nobody will screenshot the interface. Nobody needs to. This is a utility, and it looks like one.

Performance is the whole review, and it is impossible to score in a single number. By design, a recent Snapdragon 8-series device with Qualcomm’s updated Adreno drivers has the headroom to run the majority of the GameCube library and a large slice of the Wii library at full speed with resolution scaling. Games that were CPU-bound nightmares five years ago, like Twilight Princess, are within reach of that class of hardware. The ubershader and asynchronous shader compilation options exist specifically to address the stutter that plagued early Android builds.

Step down to a mid-range Exynos or a MediaTek Dimensity and the picture fractures. Driver quality on those platforms is inconsistent, Vulkan support ranges from excellent to unusable depending on firmware version, and identical specs on paper do not guarantee identical results. The project’s honest answer is that performance scales with the GPU driver, not the GPU. That is true and unsatisfying.

Battery and thermals deserve mention. Dolphin is a JIT-recompiling emulator running a PowerPC core and a full GPU pipeline, and that workload is inherently heavy for a phone: expect aggressive battery drain and enough heat that thermal throttling on extended sessions is a realistic prospect. A cooler or a clip-on fan is not a joke suggestion for long sessions.

On Android phones, Dolphin is a two-tier experience. With a Bluetooth controller and a flagship SoC, it is a genuinely capable portable GameCube. With touch controls on a budget device, it is a frustrating demo of what could be. The app cannot bridge that gap and does not pretend to.

The Android TV build is quietly the most comfortable version. A living-room box paired with a gamepad or a real Wii Remote removes the thermal, battery, and touch-control problems in one move. The leanback interface is sparse, but it puts cover art on a television and launches games without a mouse. For anyone with a Wii in a closet and a Shield under the TV, this is the more convenient device.

The monthly beta cadence is a double-edged sword on both form factors. Fixes arrive quickly. Regressions arrive just as quickly, and Google Play’s automatic updates mean a version bump can change how a game behaves. Power users should pin a known-good version. Everyone else should accept that “beta” is not a courtesy label.

Dolphin on Android is a serious engineering achievement wrapped in an honest, unglamorous package. It refuses to hide its complexity, refuses to bundle content it does not own, and refuses to promise performance it cannot guarantee. Those refusals are exactly why it has survived two decades and a legal skirmish with the most litigious company in gaming.

On the right hardware it can deliver Wind Waker at 1440p, F-Zero GX at full speed, and Metroid Prime with save states, all on a device you already carry. On the wrong hardware it delivers a folder picker and a stutter. The gap between those two outcomes is not Dolphin’s fault, but it is Dolphin’s problem, and it is what keeps this a recommendation for the right audience rather than a universal one. If you have the phone, the controller, and the discs, this is the tool for the job. If you are missing any of the three, wait until you have them.