Mobile-first
Designed for Android browsers, portrait and landscape.
PLAY · RIGHT IN YOUR BROWSER
Your Wii.
On the web.
A mobile-first browser project exploring GameCube and Wii emulation. Game files are processed locally; no game upload server is used.
◇ Game files stay on your device
FIRST ENGINE INTEGRATION
Try the Gecko WebAssembly build
This experimental build wires Gecko's Wii disc boot path for restored Wii ISO/RVZ images. NKit images are not restored by the browser build and cannot boot yet. A successful launch attempt is not proof of playable gameplay; the first goal is to capture the exact boot/apploader result. Large images may exceed browser memory, especially on phones.
Open experimental engineLOCAL IMAGE RESTORE
Restore an NKit image on Android
The browser itself cannot run the native NKit restore engine reliably on multi-gigabyte images. The practical no-server route is to run the open-source nkit2iso tool locally in Termux. Your game image stays on your phone and is not uploaded.
Before starting
Have several gigabytes of free storage: your example image needs roughly 4.7 GiB for a full Wii ISO, plus working room. Keep the original NKit file until the output has been checked.
Have several gigabytes of free storage: your example image needs roughly 4.7 GiB for a full Wii ISO, plus working room. Keep the original NKit file until the output has been checked.
Open the Android restore guide
Get Termux from official releases ↗
This is a real local workaround, not an in-browser conversion. The guide explains the commands and how to verify that restoration succeeded.
DEVELOPER TEST
Test disc-file reading
Run browser checks against a locally selected disc image. This verifies small range reads and file-boundary handling; it does not launch a Wii game.
Open disc-reader testClient-side
GitHub Pages hosting, with no custom server or backend.
Keyboard input
The experimental Gecko browser build currently uses keyboard controls.