So You Want To Play Epic Games Through Steam Link
It doesn't work out of the box. Epic Games has no native integration with Steam Link, period. But people figure it out anyway. Here is how the workaround actually functions in practice. The whole thing relies on one fact: Steam Link streams whatever is running on your desktop. So you need Epic's content accessible on that desktop, and you need a bridge between the two launchers. The most reliable method I've found uses Windows Quick Assist paired with Steam's in-home streaming protocol, not the cloud features either platform advertises. Step one, install the Steam Link app on whichever device you're streaming to — phone, tablet, old laptop, whatever. Launch Steam on your main PC and make sure Big Picture Mode is active. Go into Settings, then Remote Streaming, and verify that "Enable Remote Streaming" is toggled on. This part takes about two minutes if your firewall isn't being difficult.
Here is where it gets specific. Open Epic Games Launcher on your main PC. Add any Epic titles you want to play through Steam Link as non-Steam games inside Steam's library. Right-click any game in your Steam library, select Properties, and under the Shortcuts section, add the Epic game's executable path. You will find this at C:\Program Files\Epic Games\[GameName]\Binaries\Win64\[GameExecutable].exe. This usually takes me about five minutes per game, sometimes longer if Epic has changed the install directory on a recent update. Once the shortcuts are registered, start the game from within Steam. Steam handles the remote session. The Epic launcher runs in the background on your host PC, and Steam streams the desktop output to your client device. Controller input passes through natively for most games. The catch is that some Epic-exclusive titles have anti-cheat systems — specifically Easy Anti-Cheat and BattlEye — that refuse to function through remote desktop or streamer modes. This means games like Fortnite or Rocket League will not work through this setup. You can play single-player Epic exclusives like Death Stranding or Control just fine. Just don't expect competitive multiplayer to cooperate. I hit this wall hard about eighteen months ago. I spent nearly an hour troubleshooting why my Death Stranding save wasn't persisting across sessions. The problem turned out to be that Epic's launcher wasn't properly launching the game when triggered through Steam's shortcut — it was launching a cached version of the launcher instead. The fix was adding a startup argument. In the Steam shortcut properties, I added --epicapp=DeathStranding to the command line. Steam had been calling the launcher exe instead of the game exe directly. Once I pointed the shortcut at the actual game binary rather than the launcher shell, saves synced normally. That took another twenty minutes to diagnose.
Network Requirements That Actually Matter
Everyone tells you to use 5GHz WiFi. That advice is technically correct but practically incomplete. What matters more is latency jitter, not raw throughput. A stable 30ms round-trip on 5GHz is better than a fluctuating 15-60ms connection that looks fast on paper. Run a speed test on both your host PC and your client device. If the jitter exceeds 10ms, you will notice input lag in fast-paced games even if your bandwidth looks adequate. The wired Ethernet connection for the host PC remains non-negotiable if you care about consistent performance. WiFi on the host side introduces variable packet delay that Steam Link's encoding struggles to compensate for. My setup runs on a CAT6 cable from the router to the PC, and I measure around 2-4ms network latency between devices on the same local network. That is what you should aim for.
Get the Full Details

Common Pitfalls Beginners Miss
First, many people try to stream Epic Games through Steam Link's cloud feature. That is a completely different system and does not apply here. Steam Link streams from your local PC. If you are trying to use Steam Cloud to bridge Epic games, you are solving the wrong problem. Second, the Steam Overlay often conflicts with Epic's launcher when both are active. If you see black screens or frozen frames after a few minutes, disable the Steam Overlay for that specific game in Properties. This usually resolves the issue immediately without affecting streaming quality. Third, some users report that their controller stops responding after the game transitions from the Epic launcher to the actual game. This happens because the controller input context switches between the launcher process and the game process. The workaround is to set your controller configuration in Steam Big Picture Mode before launching the game, not after. Steam maps the controller to the Steam shortcut, and once the game inherits that mapping, the controller works. If you configure after launch, Steam may not detect the input context switch.
When This Approach Fails Completely
If your host PC cannot maintain a consistent 60fps at your desired resolution, the stream will look worse than playing native. I have seen people attempt this on machines with integrated graphics or weak GPUs, and the result is unwatchable. You need a dedicated GPU capable of encoding at least 1080p at 60fps while running the game simultaneously. An RTX 3060 or better, or an equivalent AMD card, is a realistic minimum. Lower-resolution streaming at 720p can work on weaker hardware, but you are trading image quality for functionality. If you are dealing with titles that require always-onlineDRM tied to Epic's launcher, this setup will work but you may encounter login prompts mid-session if the launcher decides to re-authenticate. It is rare but annoying when it happens. I have had this occur maybe twice in six months of regular use. For a cleaner experience with Epic games, consider using Moonlight + Sunshine as an alternative. Sunshine acts as an NVIDIA GameStream alternative and handles Epic games directly without needing Steam as a middleman. The setup is more involved initially, but the streaming quality and latency are noticeably better. I switched most of my Epic titles over after finding Steam Link's encoding less efficient at higher resolutions.
The core workflow is straightforward once you get past the initial configuration. Register Epic games as non-Steam titles, launch through Steam, and let the remote session handle the rest. Budget about thirty minutes for your first setup if everything goes normally. Anything longer usually means you are chasing a specific compatibility issue with a particular game.
