Play emulated console games with friends who only open a URL. The host PC runs the emulator; its picture and sound go to each friend's browser over WebRTC, and the friends' controllers come back the same way. Friends install nothing and need no game files.
Two kinds of rooms share one guest page:
| Room | Emulator | How the picture is captured | How friends' input gets in |
|---|---|---|---|
| SNES | EmulatorJS (snes9x core) in the host's Chrome | canvas.captureStream() + requestFrame() per emulated frame |
straight into the emulator (player 2) |
| GameCube / Wii | native Dolphin | getDisplayMedia() of the Dolphin window, auto-cropped to the game picture |
browser Gamepad API → WebSocket → a local DSU (cemuhook) server → Dolphin's DSU client (up to 3 friends = 2P–4P) |
Signaling needs no server program: a ~150-line PHP mailbox (guest/signal.php) on any
ordinary HTTPS web host. Every message is end-to-end encrypted with the room password, and the
mailbox name itself is derived from the password, so the web host and anyone holding only the
room URL see nothing useful.
Keywords: browser netplay, remote play together, cloud gaming at home, WebRTC game streaming, low-latency WebRTC, EmulatorJS netplay, Dolphin netplay in the browser, getDisplayMedia window capture, DSU / cemuhook server, Gamepad API, playout delay, jitter buffer, PHP signaling.
Measured on one PC (no network loss) — see docs/LATENCY.md
| What | Before | After |
|---|---|---|
| Dolphin room: friend presses a key → it shows in the friend's video (median, test window) | 54 ms | 25–26 ms |
| Friend's video jitter buffer (Dolphin / SNES) | 8.5 / 11.3 ms | 0.2 / 0.2 ms |
| Friend's audio buffer (Opus 20 ms → 10 ms packets, two runs each) | 29.5 / 55.2 ms | 22.0 / 42.7 ms |
The biggest single win needs no change on the friends' side: the host's Chrome is started
with --force-fieldtrials=WebRTC-ForceSendPlayoutDelay/min_ms:0,max_ms:0/, which makes the
receivers' Chrome render each frame as soon as it is decoded. The rest of the ~25 ms is mostly
waiting for 60 Hz frame boundaries plus encode/decode. Real-network behaviour is not measured.
Requirements: Windows 10/11 for the Dolphin helpers (the SNES room and the guest page are plain web code), Node.js 20+, Google Chrome, and for friends elsewhere an HTTPS web host with PHP 8.
- Put the EmulatorJS 4.2.3
datafolder athost/emulatorjs/(see docs/SETUP.md; it is not bundled). node devserver/server.mjs(orscripts/start-host-snes.bat), then openhttp://localhost:8080/.- Load your own ROM dump with the file picker, press 「ランダムに作る」 then 「部屋を開く」.
- Open the shown guest URL in another browser window, type the password, press 「参加する」.
For friends on the internet, upload guest/ to your web host and enter its addresses in the
host page's settings panel (docs/SETUP.md). For Dolphin rooms see
docs/DOLPHIN.md.
guest/ the page friends open (static files + signal.php mailbox + .htaccess hardening)
host/ host pages: index.html (SNES room), wii.html (Dolphin room), crop.js, ...
devserver/ local Node server: serves the pages, a stand-in mailbox, the DSU bridge (dsu.mjs),
Win32 window geometry for cropping (dolphin_window.ps1)
tools/ measurement and test harnesses (latency, audio queue, 1–3 guest end-to-end, security)
scripts/ Windows launchers for the dedicated host Chrome
examples/ optional short-domain redirect (.htaccess)
docs/ ARCHITECTURE, SETUP, DOLPHIN, LATENCY, SECURITY, JOURNEY (how this was built)
The UI text is Japanese; code comments and these docs are English (the docs have Japanese summaries).
Room id (128-bit random) in the URL fragment, password told separately. PBKDF2-SHA256 (600k iterations) → HKDF splits an AES-GCM-256 key and the mailbox name. signal.php stores only sealed blobs, rate-limits per address (IPv6 per /64), never creates a box on a read, caps boxes per address and files in total. The local server listens on 127.0.0.1, checks Host and Origin, and survives malformed requests. Details and remaining risks: docs/SECURITY.md.
- EmulatorJS netplay — the host runs the game and streams it over WebRTC; this project's SNES room uses the same idea with a serverless mailbox and latency tuning.
- kaillera-next — EmulatorJS browser netplay, streaming and rollback modes.
- webii — phones in a browser as Wii Remotes through DSU (no video).
- Parsec, Steam Remote Play Together, Moonlight/Sunshine — native remote-play tools.
No ROMs, BIOS files or game data are included or linked. Use dumps of games you own. EmulatorJS (GPL-3.0) and its cores (each with its own licence; snes9x is non-commercial) are fetched by you, not redistributed here — see THIRD_PARTY.md.
MIT — see LICENSE.
友達は URL を開くだけで、いっしょにエミュレーターのゲームを遊べる仕組みです。ホストの PC で エミュレーターを動かし、映像と音を WebRTC で友達のブラウザへ送り、友達のコントローラーの入力を 同じ道で返します。友達はダウンロードもゲームのファイルも要りません。
- SNES の部屋: ホストの Chrome の中で EmulatorJS を動かし、絵を 1 コマずつ取り込んで送ります
- Dolphin(GC / Wii)の部屋: ふつうのアプリの Dolphin の窓を取り込み、タイトルバーと黒帯を自動で切って送ります。友達の入力は DSU(cemuhook)で Dolphin に入ります(友達 3 人まで)
- サーバーのプログラムは不要: 握手はふつうの PHP のレンタルサーバーに置く伝言板(約 150 行)だけ。中身はパスワードで暗号化され、箱の名前もパスワードから作るので、サーバーにも URL だけを知る人にも見えません
- 遅延: 同じ PC の中で、Dolphin の部屋の通しの遅れを 54ms → 25ms に。いちばん効いたのは、ホストの Chrome の起動オプション 1 つで友達側の映像のため込みを 0 近くにすること(友達側は何もしない)
- 作った流れ(つまずきと直し方)は docs/JOURNEY.md、遅延の数字と根拠は docs/LATENCY.md、安全の作りは docs/SECURITY.md にあります
- ROM・BIOS・ゲームのデータは含みません。自分で持っているゲームの吸い出しを使ってください