Emulator netplay lets two players run the same classic game over the internet, and this guide covers host setup, guest connection, latency expectations, and which titles suit online play.

Classic local-multiplayer games were built around a couch, two pads, and one television. Netplay recreates that arrangement between machines: each player runs the same core and same ROM, and the emulator syncs input frames across the connection. It works best on fighting games, beat-em-ups, racers, and versus puzzlers, and needs a little setup on both sides before the first round. Once the lobby clicks, the difference from real hardware is mostly the occasional delay spike rather than missing features.

How emulator netplay differs from online games today

Modern online games run servers and lag compensation built into the engine. Retro emulators have no server code inside the game itself, so the frontend synchronizes inputs frame by frame. One machine acts as host, sets frame delay, and broadcasts state; guests send controller input back in lockstep. Only button presses and sync markers cross the wire, which keeps bandwidth low on shared connections. This frame-perfect model means both players should use the exact same ROM revision and core version, or desyncing freezes the match mid-game. Region mismatches and patched fan translations usually explain a connection that holds for two rounds then breaks.

RetroArch host and guest flow

Launch the same core and game on both PCs first. The host opens Quick Menu, Netplay, Start Host Netplay, picks a port, and copies the host address. Guests choose Netplay, Connect to Netplay Room, paste the address, and wait for sync. Assign the second player’s controller to a separate port on the host side so pads do not collide. Run-ahead and shaders are cosmetic and do not break sync, while cheats, state loading, and recording inside the match usually do. Save room details in netplay history to skip retyping later. On Android RetroArch behaves the same over Wi-Fi; cellular data routes poorly behind carrier firewalls, so home Wi-Fi simplifies hosting.

Latency, rollback, and choosing frame delay

Netplay hides ping behind frame delay: both machines buffer inputs for a few frames before applying them. A close local player can run at low delay for snappy feel; a distant guest usually needs two to six extra frames to stay smooth. Increase delay when inputs skip or characters jump backward, and lower it gradually once the connection holds. Few retro cores support rollback-style prediction, so choppy Wi-Fi shows up as hiccups rather than smoothed ghosts. Wired Ethernet on both ends beats Wi-Fi; keep voice chat in a separate app so game traffic stays clear.

Systems that suit online versus and co-op

• 16-bit versus fighters and shooters: Street Fighter II, Mortal Kombat, and Samurai Shodown stay popular because short rounds reward quick rematches.
• Sega Genesis co-op classics: Streets of Rage II and III, Golden Axe, and ToeJam and Earl were designed for drop-in two players; the Genesis classics list highlights several more suited to a lobby.
• Kart and party racing: Mario Kart SNES and later kart titles work when frame delay stays low, and item chaos reads well over modest lag.
• Beat-em-ups and action RPGs: side-scrolling brawlers tolerate small delays better than precision fighters, making them friendly first netplay targets.

Local pads, split keyboards, and lobby etiquette

One PC can host two local players with a guest connecting online for three or four-way matches, provided the core supports multiple ports. A shared keyboard works in a pinch, but two pads remove key conflicts during simultaneous movement and special moves. Agree before the lobby on disconnection rules: drop a run rather than reloading a save state mid-match, keep ROM versions identical, and record wins in a text file if ranking friends. Save states stay outside netplay for the same reason cheats do; our emulator basics guide covers state limits for offline runs that feed into these habits.

Troubleshooting common netplay failures

Refused connections point to firewall blocks on the host port; forward the chosen port on the router or use a relay option if available. Persistent desyncs mean differing core versions or ROM revisions; update the frontend together and compare file sizes first. Audio drifting from visuals follows high frame delay; lower it gradually and watch dropped frames in the overlay. Keyboard players struggling in fighters should switch to a pad before blaming the connection. With those checks out of the way, a regular friend lobby becomes one of the more rewarding ways to keep a retro library alive.