- Top Pick: Retroid Pocket 5
- Runner-up: Anbernic RG556
- Also consider: Anbernic RG35XX H
Plenty of retro handhelds can now do something the original consoles never could: play a two-player game with someone in another house, another city, or another country. The feature behind it is netplay, and on most handhelds it runs through RetroArch. Netplay is not game streaming, and understanding that difference is the key to setting it up correctly the first time.
Used well, netplay turns a pocket device into a virtual couch. Used carelessly, it produces desyncs and sessions that collapse after two minutes. This guide explains how the system works, why its matching rules are so strict, and what gear makes it reliable.
As an Amazon Associate, we earn from qualifying purchases.
Quick Answer
Netplay on a retro handheld runs the same game on both devices and syncs only controller inputs, so both players must use the identical core, game file, and emulator version. A relay server is easiest to set up, a direct connection is faster, and adding input delay frames or using rollback cores hides most of the remaining lag.
Two Handhelds, One Virtual Console
Netplay works because classic games are deterministic. Given the same starting state and the same sequence of button presses, the emulated console produces the same result every time, down to the frame. RetroArch exploits this with a lockstep design: both handhelds run the full game locally, and the only data traveling over the network is controller input, a few bytes per frame.
That design has three big consequences. Bandwidth needs are tiny, so even a modest home connection can carry a session. There is no video compression and no streaming artifacts, because nothing is streamed. And the two sides must stay in perfect lockstep. If one device emulates even slightly differently, the two games drift apart, inputs stop making sense on the far side, and the session desyncs or freezes.
Relay Server vs Direct Connection
RetroArch offers two ways to connect, and choosing between them is the first real setup decision.
A direct connection links the two handhelds peer to peer. The host forwards a port on the router, typically UDP port 55435, and the client connects to the host’s public address. This path adds the least latency because traffic goes straight between the two homes. The cost is friction: port forwarding confuses many routers, and carrier-grade NAT can block it entirely.
A relay server removes that friction. Both players connect outward to a public relay, which passes the input traffic between them. No port forwarding is needed, NAT problems mostly disappear, and joining a public lobby takes seconds. The trade-off is an extra hop: traffic detours through the relay’s location, so a distant relay adds noticeable delay.
The practical rule is simple. Use a relay for a quick session with minimal setup. Use a direct connection when both players are comfortable with router settings and want the lowest latency. On the same home network, a direct local connection is best of all, because traffic never leaves the house.
The Matching Rule: Same Core, Same File, Same Version
Netplay refuses to be casual about compatibility, and this is where most failed sessions are born. Three things must match exactly on both handhelds.
The core must be identical, including its version. Two different NES cores, or the same core built months apart, can emulate the same game slightly differently, and slight differences are all a desync needs. The game file must be identical too, byte for byte: a different dump, region, or patched copy changes the data emulation starts from. The RetroArch version should also match, because netplay protocol details change between releases.
When a session fails to start, RetroArch usually says so during the handshake rather than mid-game, which is the polite outcome. The annoying failures come from near matches: the same game from a different source, or a core updated on one handheld but not the other. Keeping a shared, known-good setup with your regular partner eliminates almost every problem here.
Latency, Delay Frames, and Rollback
Even a perfectly matched session has to deal with physics. Inputs take time to cross the internet, and lockstep emulation cannot show the result of a press until it has arrived on both sides. RetroArch handles this with input delay frames: the game holds inputs for a set number of frames so both devices stay synchronized. Each delay frame costs about 17 milliseconds of responsiveness. Two frames is a common starting point for a same-country connection; long-distance sessions may need four or more.
The feel changes by genre. Turn-based and puzzle titles barely notice six frames, racing games tolerate a few, and fighting games expose every frame, which is why serious players prefer direct connections wherever possible.
Some cores offer a second approach called rollback, borrowed from modern fighting game netcode. Instead of delaying inputs, a rollback core predicts them, and when the real input arrives late, it rewinds and re-simulates the last few frames. Done well, rollback feels dramatically more responsive. The cost is processing power: re-simulating frames takes CPU headroom budget handhelds may not have on heavier systems.
One more setting matters: run-ahead and other solo-play latency features should be left off during netplay, because they change how frames are produced and can fight the synchronization.
Gear That Makes Handheld Netplay Work
Netplay is a software feature, but hardware decides how pleasant it feels. A handheld needs built-in Wi-Fi, enough CPU headroom to hold full speed with delay frames added, and a stable RetroArch build. The home router matters just as much, because a weak signal adds jitter no setting can fix. These five products cover the main ways players build a dependable setup.
Retroid Pocket 5
An Android handheld with the processing headroom netplay rewards. The Snapdragon 865 holds full speed on heavier cores while delay frames are added, and Android means the full current RetroArch build for easy version matching with a PC partner.
Specs:
– Chipset: Qualcomm Snapdragon 865
– Display: 5.5-inch AMOLED, 1080 x 1920 touchscreen
– Memory: 8 GB RAM, 128 GB storage
– Connectivity: Wi-Fi, Bluetooth 5.1
– Battery: 5,000 mAh
– System: Android 13
Anbernic RG556
A widescreen Android option with a strong network stack for its class. Dual-band Wi-Fi holds a steadier connection than single-band budget devices, and the T820 chipset has reserve for rollback cores on lighter systems.
Specs:
– Chipset: Unisoc T820
– Display: 5.48-inch AMOLED, 1080 x 1920 touchscreen
– Memory: 8 GB RAM, 128 GB storage
– Connectivity: dual-band Wi-Fi, Bluetooth 5.0
– Battery: 5,500 mAh
– System: Android 13
TrimUI Smart Pro
A Linux handheld that punches above its weight for netplay. Custom firmware builds ship with a well-maintained RetroArch, and its Wi-Fi is reliable on a home network. The modest chipset limits it to 8-bit and 16-bit systems, exactly where lockstep play works best.
Specs:
– Chipset: Allwinner A133 Plus
– Display: 4.96-inch IPS, 1280 x 720
– Memory: 1 GB RAM, 8 GB storage
– Connectivity: Wi-Fi, Bluetooth
– Battery: 5,000 mAh
– System: Linux with custom firmware options
Anbernic RG35XX H
The budget entry point for netplay on Linux firmware. The H700 chipset runs the classic 8-bit and 16-bit catalog at full speed, Wi-Fi is built in, and the horizontal shell suits long sessions. It makes a sensible second device to hand to a guest for a local-network match.
Specs:
– Chipset: Allwinner H700
– Display: 3.5-inch IPS, 640 x 480
– Memory: 1 GB RAM, microSD storage
– Connectivity: dual-band Wi-Fi, Bluetooth 4.2
– Battery: 3,300 mAh
– System: Linux with custom firmware options
TP-Link Archer AX21
The router upgrade that quietly fixes most netplay complaints. Wi-Fi 6 with OFDMA keeps latency steadier when the household is streaming and browsing at the same time, and strong 5 GHz coverage lets a handheld use its best band instead of clinging to a weak signal.
Specs:
– Standard: Wi-Fi 6, AX1800 dual band
– Speeds: 574 Mbps on 2.4 GHz, 1,201 Mbps on 5 GHz
– Features: OFDMA, MU-MIMO, four external antennas
– Ports: gigabit WAN and LAN
– Compatibility: EasyMesh support, works with Alexa
How to Choose
Start with your partner, not your wallet. The best netplay handheld is the one that runs the same cores as the device on the other side, so match your regular opponent first. Android handhelds pair most easily with PCs and phones, while Linux handhelds pair best with each other on the same firmware family.
Next, be honest about your game library. If your sessions are NES, SNES, Genesis, and Game Boy Advance titles, almost any Wi-Fi handheld holds full speed, and the connection matters more than the chipset. PlayStation and Dreamcast sessions need real headroom, because a device that barely reaches full speed alone will dip once delay frames arrive.
Finally, audit your room before your device. A handheld played two rooms from an aging router feels worse than a cheaper handheld played beside a modern one. Playing closer to the router and using the 5 GHz band fix more sessions than any handheld upgrade.
Who Should Skip Netplay
Skip netplay if the games you care about are single-player adventures. Role-playing games, strategy titles, and story-driven games gain nothing from a second device, and save file syncing is a separate, simpler topic.
Skip it if your internet connection is unstable rather than merely slow. Netplay needs very little bandwidth but hates jitter and packet loss, so a congested shared connection or weak mobile hotspot frustrates both players regardless of hardware.
Skip it, too, if you and your partner cannot agree on one fixed setup. Half of netplay discipline is leaving a working configuration alone; players who constantly swap cores and firmware spend sessions troubleshooting handshakes instead of playing.
Frequently Asked Questions
Do both players need the exact same game file for netplay?
Yes. The file must be identical byte for byte, which in practice means the same dump from the same source. A different region release or patched copy counts as a different game to the emulator, and mismatched files are the most common cause of sessions that refuse to start or desync within minutes.
Is a relay server slower than a direct connection?
Usually, yes, by a small margin. A relay adds a detour through a third location, so the extra delay depends on where that server sits. A nearby relay often feels identical to a direct link for slower-paced games, while a distant one is a poor choice for fighting games.
Which systems work best for handheld netplay?
The 8-bit and 16-bit generations are the sweet spot. NES, SNES, Genesis, and Game Boy Advance cores are light enough for budget handhelds to run at full speed with delay frames to spare, and their multiplayer catalogs are huge. PlayStation works well on mid-range hardware; Nintendo 64 and Dreamcast demand stronger devices.
Can a handheld and a PC play together over netplay?
Yes, as long as the matching rule is respected: the core, its version, the game file, and ideally the RetroArch version must line up across both machines. Many players use a PC as host and a handheld as guest, which works well because the PC usually has the stronger connection and more processing headroom.
Final Verdict
Netplay is the most underused feature on modern retro handhelds, mostly because its rules sound stricter than they are. Match the core, match the game file, pick a relay for convenience or a direct connection for speed, and add delay frames until the session feels stable. Do that, and a pocket handheld delivers something the original hardware never offered: a shared couch that stretches across any distance. The Retroid Pocket 5 is the easy recommendation for players who want headroom to spare, and the TrimUI Smart Pro and RG35XX H cover the classic generations with minimal fuss.










