How to Use Dolphin Netplay — Online Multiplayer for GameCube and Wii Games 2026

host-or-join-a-dolphin-netplay-session (sortOrder=1, isMostHelpful)

What Dolphin Netplay is: Netplay lets two or more players share a single emulation session over the internet — player input from each machine is synchronized so everyone sees the same game state. It works for most GameCube and Wii games. Both players need an identical copy of the game ISO and the same Dolphin version.

Before you start — requirements:

• Both players must use the same version of Dolphin (download the latest stable from dolphin-emu.org). Mixed versions cause immediate desync.
• Both players need the exact same ISO or ROM file — byte-for-byte identical. The easiest way to verify: check that the file size and CRC32 hash match. A re-dump or patched version on one side will desync at boot.
• A stable internet connection. Wired ethernet is strongly preferred. Dolphin Netplay is sensitive to jitter even at low ping.

Hosting a session:

1. In Dolphin, go to Tools → Start NetPlay.
2. In the Netplay window, click Host.
3. Select your game from the list (it must be in your Dolphin game directory).
4. Set a Port (default: 2626). Click Start.
5. Dolphin provides a session code (traversal address like abc12.dolphin.net) — share this with your friend. The traversal server handles NAT punch-through so most users don't need to port-forward. If traversal fails, see S2.
6. Wait for your friend to join. Once connected, click Start Game in the Netplay window to launch.

Joining a session:

1. Go to Tools → Start NetPlay → Connect.
2. Enter the host's traversal code (or their direct IP:port if not using traversal).
3. Click Connect. Dolphin will verify that your game hash matches the host's. If it doesn't match, you'll get a hash mismatch error before the game launches — get the correct ISO before continuing.

Controller assignment: In the Netplay window, each player is assigned to a controller slot (P1, P2, etc.). The host controls the assignment. Make sure each player's local controller maps to their correct Netplay slot before starting.

port-forwarding-and-traversal-setup (sortOrder=2)

Dolphin Netplay supports two connection methods:

Traversal (default — no port forwarding needed):

• Dolphin's traversal server (slippi.gg / Dolphin's own service) acts as a matchmaker. The host gets a short session code; the client connects via that code.
• Works through most home routers and NAT setups automatically.
• Slightly higher latency than direct connection (~+5-20 ms relay overhead) but much easier to set up.
• If the traversal server is unreachable (rare), switch to Direct Connection.

Direct Connection (manual port forwarding):

1. On the host's router admin panel (usually 192.168.1.1), create a port forwarding rule:
   • Protocol: UDP
   • External port: 2626
   • Internal IP: your PC's local IP (e.g., 192.168.1.x)
   • Internal port: 2626
2. In Dolphin Netplay, set the connection method to Direct and share your public IP address (check whatismyip.com) plus the port (your.ip:2626) with the joiner.

Direct connection gives the lowest possible latency but requires router access. For occasional play, traversal is fine.

Firewall note: Windows Defender Firewall may block Dolphin. If the joiner can't connect, open Windows Defender Firewall → Allow an app and add Dolphin for both private and public networks.

game-compatibility-and-settings-for-smooth-play (sortOrder=3)

Game compatibility: Most single-player GameCube and Wii games work fine in Netplay for co-op or competitive play. Games with compatibility issues:

• Games that use random number generation in real-time can desync if the RNG is not seeded identically — this is rare but happens in some racing games with non-deterministic AI.
• Wii games using MotionPlus (e.g., Wii Sports Resort, Skyward Sword) have limited Netplay support — emulated MotionPlus can diverge between clients.
• GameCube LAN games (Mario Kart: Double Dash!! — LAN mode) need special setup; use Dolphin's built-in Netplay instead of the in-game LAN option.

Settings both players must match exactly:

• DSP emulation engine (Settings → Audio → DSP): both must use the same — HLE or LLE. Mismatches cause desync.
• Memory card emulation vs. GCI folder: recommend both use GCI Folder (Settings → GameCube → Slot A/B → GCI Folder). Standard memory card can create sync conflicts on saves.
• CPU emulation engine: both must use the same (JIT Recompiler or Interpreter). In practice, keep defaults — Interpreter is too slow for Netplay anyway.

Latency / buffer settings: In the Netplay window, the host sets a Buffer value (number of input frames to buffer). Higher buffer = more input lag but fewer frame-drops. Rule of thumb:

• Ping <30 ms (same country): buffer 4-6
• Ping 30-80 ms (different country): buffer 8-12
• Ping >80 ms: buffer 12-20 (noticeable input lag — set expectations with your friend)

The Minimum Buffer button in the Netplay window shows the optimal auto-calculated value based on current latency.

desync-and-lag-troubleshooting (sortOrder=4)

"Desync detected" message / games diverge after a few minutes:

• Most common cause: different ISOs. Even a 1-byte difference in the game file causes desync. Verify file hashes on both machines using a tool like HashCheck or CertUtil (certutil -hashfile game.iso MD5). If they differ, one player needs to get the correct matching file.
• Different Dolphin versions. Both players must run the exact same release — even minor version bumps between stable and beta can cause desyncs.
• One player applied a graphics texture pack or cheat code that alters game memory — disable all codes in Netplay mode.
• Mismatch in the DSP engine setting (see S3 above).

High lag / unplayable frame rate:

• Increase the Netplay Buffer value (S3). More buffer = fewer stutters, more latency.
• Switch to a wired ethernet connection. Wi-Fi jitter is the single biggest cause of Netplay stutter.
• Close bandwidth-heavy applications (streaming, downloads) on both sides during the session.
• If using traversal and experiencing consistently high latency, try Direct Connection — it removes the relay hop.

Memory card / save issues:

• In Netplay, both players share the host's virtual memory card. Individual saves are not synced back to each player's local card by default.
• After a session, export the memory card: Dolphin → Config → GameCube → Slot A → Export all saves. Share the export with the other player if they need the save file.
• For Wii games, the Wii save system is per-machine — Netplay shares the host's Wii NAND, so only the host accumulates saves locally.

Joiner keeps getting "connection refused":

• Check the host's firewall (see S2). The most common fix is adding Dolphin as an exception in Windows Firewall.
• If using Direct Connection, confirm the host's public IP hasn't changed (many ISPs rotate IPs). Check again at whatismyip.com.
• Confirm the port (2626) is forwarded on the host's router for UDP.