Pick up your handheld, press play on a game from your PC, and go.
Works with Steam's built-in Remote Play: wakes your PC and keeps the stream on a virtual monitor, with your other displays off.
⬇️ Download the latest release · 🎮 Decky plugin · 📝 Changelog
- ✨ What is this?
- 📥 Install, step by step
- 🔐 Pairing your handheld
- ⚙️ Settings and features
- 🔎 How it works
- 🔧 Build it yourself
- 🙏 Credits
This is the PC half of SpoutRemotePlay. It does not stream anything itself. Steam still does the streaming (capture, encode, input and Steam Link on the handheld). The host watches for a Remote Play session and makes sure the stream lands on a virtual monitor, with your other displays off. When the session ends, it puts everything back.
- Windows: Steam makes the virtual display itself (using the SudoVDA driver) and sizes it for your device. The host waits for it, turns your other displays off, and restores them afterwards.
- Linux: Steam doesn't make a virtual display, so the host makes one that matches your device and removes it afterwards.
| 🖥️ Virtual monitor per device | On Linux, resolution and refresh rate come from that device's settings. On Windows, Steam sizes its own display. |
| ⭐ Primary while streaming | The virtual monitor is your main display during the session, so Steam streams it. |
| 🌑 Other displays off | Every other display turns off during the session and comes back when it ends. On Windows you can choose displays to keep on. |
| 🔐 Paired devices only | Unpaired clients never get a monitor. |
| 🧩 Apps | Add programs to Steam from the web page, with optional artwork. |
| ⏻ Shut down | A paired device can shut the PC down, for example from the Decky plugin. |
| ⏰ Wake relay | A paired device away from home can ask this PC to wake another PC on its network. |
Together with the Decky plugin, the flow is: wake the PC → press play in Steam → stream.
Why "Spout"? It's a play on Valve. A valve controls the flow of steam, and a spout is where the steam comes out. Steam does the streaming. Spout gives it somewhere to pour: a virtual monitor shaped for your handheld.
Install the host on your PC, then install the Decky plugin on your handheld.
Decky Plugin Store: the plugin is submitted to the store in decky-plugin-database PR #1146, which is still open. Once it is merged, the plugin will be available straight from the Decky store. Until then, install it from a ZIP file as described in the plugin README.
Files are on the latest release:
| System | File | Notes |
|---|---|---|
| 🪟 Windows | SpoutRemotePlayHost-Setup-vX.Y.Z.exe |
Installer (recommended) |
| 🪟 Windows | spout-host-vX.Y.Z-windows-amd64.exe |
Portable, no driver or autostart |
| 🐧 Linux | spout-host-vX.Y.Z-linux-amd64.tar.gz |
Run ./install.sh |
- Download
SpoutRemotePlayHost-Setup-vX.Y.Z.exe(not the barespout-host-*.exe) and run it. - Pick your options (explained below) and finish the wizard. It installs the host, a tray icon and a Start Menu shortcut.
- The host's web page opens. Keep it handy for pairing.
- Do the Steam setup below.
Installer options:
- SudoVDA virtual display driver. If SudoVDA is already installed (for example by ArtLight or Apollo), it is reused and left alone, so both apps work side by side. Uninstalling SpoutRemotePlayHost never removes it. Otherwise the installer adds a SudoVDA built from SudoMaker/SudoVDA (MIT) in CI and signed with a self-signed certificate. That certificate goes into the Windows Trusted Root and Trusted Publishers stores, and both are removed on uninstall unless another app replaced the driver since. Untick this to install the host only.
- Start automatically when I sign in. A logon task runs the host, also on battery and with no time limit.
- Allow Decky to scan this PC on the local network. The host listens on
0.0.0.0:47995, and a firewall rule allows it on all network profiles (home networks are often marked Public). Other machines still need a token. - Spout Sign-In (off by default). Lets a paired device type your PIN at the Windows sign-in screen. See Sign in after Wake-on-LAN.
Good to know:
- Starting the host while it already runs just opens its web page.
- The exe has no console. Errors show in a message box and go to
%APPDATA%\SpoutRemotePlayHost\spout-host.log. - Ctrl+Alt+Shift+Q (Moonlight's quit-stream shortcut) ends the session's display handling and brings your displays back. If another app already uses it, the hotkey is turned off (and logged) and everything else runs normally.
Steam makes its own virtual display for Remote Play using the SudoVDA driver. The menu names follow public descriptions of the Steam client beta, so Steam's wording may differ.
- Install the host with SudoVDA virtual display driver ticked (or keep an existing SudoVDA).
- In Steam, join the client beta: Steam > Settings > Interface > Client Beta Participation. Then restart Steam.
- In Steam > Settings > Remote Play > Advanced Host Options, pick SudoVDA as the virtual display device if Steam offers it.
- Stream from your handheld. The host waits up to 20 seconds for Steam's display, turns the other displays off, and restores them when the session ends. If Steam's display never shows up, your displays are left on.
Tested on Windows 11 with an Odin 2 Portal on the Steam client beta: the other displays turned off during the stream and came back afterwards.
Steam and the host only run once someone is signed in. So a PC that was just woken sits at the sign-in screen and can't stream. With Spout Sign-In ticked in Setup, the Decky plugin shows a numpad when the PC is on but nobody is signed in (or it's locked). Type your Windows PIN and the PC signs in. If Steam isn't running 5 seconds later, the host starts it minimized. Run the host with -start-steam=false to turn that off.
How it stays safe:
- Setup installs the
SpoutSignInsystem service. It starts at boot and listens on0.0.0.0:47994, with a firewall rule. - Setup also turns on the Windows "Do not display the lock screen" policy, so the PIN box shows right away. Removing Sign-In (or the host) turns it back off, unless it was already on.
- It only accepts devices paired with this host, and allows 5 tries per 5 minutes on top of Windows' own PIN lockout.
- It only types when nobody is signed in or the session is locked, and only while the sign-in screen has the keyboard. It never types into a signed-in desktop or a UAC prompt.
- It trusts the paired devices in
%APPDATA%\SpoutRemotePlayHost\paired.json. Programs running as you can edit that file. At worst, one could type guesses at your lock screen, and Windows' PIN lockout limits that. - The PIN is typed once and never stored or logged. Only digits work, so you need a numeric Windows Hello PIN, not a password.
- The service logs to
%ProgramData%\SpoutRemotePlayHost\spout-host.log.
- Download
spout-host-vX.Y.Z-linux-amd64.tar.gzand extract it. - Open a terminal in the extracted folder and run
./install.sh. It sets up a user systemd service. Run./install.sh --uninstallto remove it. - Enter your sudo password when asked. The script also sets up the driver with DKMS:
- It installs
dkmsand kernel headers for you (Fedora, Arch, Debian, Ubuntu, openSUSE). - On Fedora it gets headers for the exact running kernel from Koji, so no reboot is needed. Only as a last resort does it build for the newest installed kernel and ask for a reboot.
- It adds a sudoers rule limited to
/usr/local/libexec/spout-vdisplay. Pass--no-driverto skip the driver.
- It installs
- The service listens on
0.0.0.0:47995so the Decky plugin can reach it. Other machines still need a token.
Tested on: KDE Plasma on Wayland with Linux 6.16 or newer. Other setups haven't been tried, so they may or may not work. The Linux backend uses the vibeshine_drm kernel module (the same driver ArtLight uses) and kscreen-doctor.
Tested by streaming from a Linux PC to an AYN Odin 2 Portal: the host made a virtual display for the stream and removed it afterwards.
- In the Decky plugin, pick this PC.
- The handheld shows a 4-digit PIN, and the host shows a notification (Windows and Linux).
- Type the PIN into the host's web page.
Requests expire after 2 minutes and are cancelled after 5 wrong PINs. Confirming and revoking can only be done on the host PC.
The Monitor config tab of the web page has:
- Defaults: the virtual monitor for devices without their own settings (Linux only, since Steam sizes its own display on Windows). Each device can override this from the Devices tab or from the plugin.
- Displays during a session (Windows): tick the displays to keep on while streaming. Unticked ones turn off and come back afterwards. If Windows turns one back on mid-session (for example a monitor that wakes from sleep), the host turns it off again.
There is no codec setting. Steam picks the codec itself, and PyroWave isn't available with Steam streaming.
You don't need an Android app, because Steam Link already streams. The Devices tab has an Other Steam devices section listing devices Steam knows about (read from the running Steam client). Set a virtual monitor for each one (resolution, refresh, auto-create). When a stream starts, the host matches the client name in Steam's log to that device.
- Pair the device in Steam first.
- The list also shows other PCs Steam can see. Ignore those.
- The device list is verified against real Steam on Linux. An actual Android stream hasn't been tried yet.
Wake-on-LAN packets stay on your local network, so a handheld on a VPN such as WireGuard can't wake a PC by itself. The host can relay it. A paired device calls POST /api/wake with {"mac": "aa:bb:cc:dd:ee:ff"} and its token, and the host sends the magic packet on every network it's on. The Decky plugin does this automatically: when you wake a PC, it also asks every other online paired PC to send the packet. Something at home has to be on, such as a second PC running the host.
A paired device can send POST /api/power with {"action": "shutdown"}. Windows does a full shutdown after 5 seconds (so Wake-on-LAN still works), though apps with unsaved work can block it. Linux runs systemctl poweroff.
The Apps tab adds programs to this PC's Steam library as non-Steam shortcuts, so you can stream them like any game. The Decky plugin can list them.
- Steam integration: Steam is controlled through its local debug port. Click Enable Steam integration once, then restart Steam.
- Local only: adding, removing and deleting apps only works from this PC, because it runs programs on the host. Paired devices can only read the list.
- Artwork (optional): save a free SteamGridDB API key and new shortcuts get a cover, hero, logo and icon. If you paste the key with its label (e.g.
Key: …), the label is dropped. Auto artwork takes SteamGridDB's top pick of each type; Choose artwork shows the options (and other games with a similar name) so you click the ones you want. Images are only downloaded from SteamGridDB. Choosing artwork and setting it in Steam is tested on Windows; setting artwork is also verified on Linux. - Add and remove are verified on Linux Steam. Whether the Steam Link client lists them isn't verified yet.
- Browse… opens this PC's own file dialog to pick the program (a web page can't see real file paths). On Windows it's tested opening in the right folder, cancelling, and refusing a second dialog while one is open. On Linux it uses
kdialogorzenityand is not tested yet. - Import from Steam lists the non-Steam games already in Steam (read from
userdata/<you>/config/shortcuts.vdf, so Steam doesn't need to be running) and adds them to the list, linked to their existing Steam entry. Nothing in Steam changes. Tested on Windows with 8 Xbox games. Deleting an imported app also removes it from Steam.
The host checks GitHub for a new release a minute after it starts and every 6 hours. When one is out you get a desktop notification, and the web UI shows Install update. Monitor config → Updates shows the status, has Check now, and an Install updates automatically option that installs new releases on its own, but never while a device is streaming.
- Downloads come only from this repository's releases and must match the SHA-256 digest GitHub publishes for them.
- Windows: runs the new Setup silently with the tasks you picked before (autostart, LAN, Sign-In). If the host isn't running as administrator, Windows asks for permission first. Setup restarts the host when it's done.
- Linux: replaces
~/.local/bin/spout-hostwith the one from the release and restarts in place. Only the binary is updated; re-runinstall.shfrom a new release if its notes mention driver or service changes. - Builds you compile yourself (version
dev) don't update. - If an update fails, the reason shows under Updates and in
spout-host.log. You can always install a release by hand from the Releases page. - Tested on Windows: an installed 0.8.0 updated itself to 0.8.1 from the real release in about 5 seconds (download, digest check, silent Setup, previous tasks kept, host and Sign-In service back up), and with Install updates automatically on it installed 0.8.2 on its own about a minute after the host started. Not tested yet: the Linux path and the Windows permission prompt.
Two independent signals tell the host a stream started, so it doesn't rely on one fragile hook:
- From the handheld: the plugin reports Steam's Remote Play start and stop to the PC you're streaming from (
POST /api/session, using the device's own token). - From the PC: the host reads Steam's
streaming_log.txt. A start looks like "Streaming started to …". The end is "PipeWire: Deinitializing streaming" on Linux and "Encoding complete" on Windows.
Only paired devices get a virtual monitor. A session from an unpaired client (or a plugin call using the API token instead of a device token) is logged and ignored. The monitor uses that device's settings, survives a stream restart or reconnect (90 s grace on Windows, 5 s on Linux; reconnects are tested and work), and is only removed by the device that owns it.
go build ./cmd/spout-host
GOOS=windows GOARCH=amd64 go build ./cmd/spout-hostReleases are built by CI when a pull request is merged into main.
This project builds on the ideas and work of others, and I'm grateful to them:
- Moonlight – the open-source game streaming client that started it all.
- StreamLight – a Moonlight fork with deeper host integration.
- ArtMoon and ArtLight – the gamepad-first client and its one-installer host. The virtual-monitor design, the pairing flow and the Linux driver choice follow ArtLight.
- SudoVDA (MIT) – the Windows virtual display driver.
- libvirtualdisplay (MIT, GPL-2.0 module) – the Linux
vibeshine_drmvirtual display module, derived from the Linux kernel's VKMS.
SpoutRemotePlayHost is an independent project and is not affiliated with any of them or with Valve.
If this is useful to you, you can ☕ buy me a coffee on Ko-fi.
