Valve has added the experimental Pyrowave codec to the Steam client beta, giving Remote Play users a high-bandwidth, low-latency option that targets wired LAN setups, HDR, and sharper desktop streaming.
Image: kitguru.net
Valve’s new Remote Play codec is live in beta, but it asks a lot of your network
Valve shipped a Steam Client beta update on September 21 that adds Pyrowave, an experimental video codec for Steam Remote Play. The Steam Deck news page describes it as a codec for “high bandwidth, low latency video streaming,” and points users to Valve’s Steam Remote Play discussion group for the deeper technical notes.
The immediate tradeoff is the story. According to Valve’s explanation quoted by GamingOnLinux, Pyrowave uses five to ten times the bandwidth of other streaming codecs. Valve’s guidance is blunt: users should have computers connected directly to their router with at least Gigabit Ethernet. That makes the Steam Remote Play Pyrowave codec less of a universal upgrade and more of a specialist tool for players who already have the right local network.
This is the kind of beta feature that changes the Remote Play equation for a specific audience first: wired PC-to-PC setups, Steam Deck or SteamOS users streaming from a stronger host machine on the same LAN, and players who care enough about latency to watch the performance graph rather than trust a quality preset. For everyone else, especially Wi-Fi users or anyone streaming across a constrained network, Pyrowave may expose the limits of the setup faster than it improves the experience.
Who can test Pyrowave now
Valve’s September 21 beta release places Pyrowave in the Steam client beta rather than the stable client. GamingOnLinux reports that the fresh Steam beta is available across platforms, while Valve’s own Remote Play explanation says Pyrowave is available now in the Steam beta on macOS and Windows. Linux users need an extra step: Valve says Pyrowave is available in the Steam beta on Linux only if the experimental SteamRT3 Steam Client is enabled.
GamingOnLinux notes that on desktop Steam the experimental SteamRT3 toggle appears at the bottom of Interface settings, while on SteamOS, including Steam Deck and Steam Machine contexts, it is in System settings. The Steam Deck news page separately confirms that the update shipped to the Preview/Beta channel and lists Pyrowave under Remote Play.
Pyrowave is not enabled by default. Valve says users can turn it on through Steam Remote Play’s advanced client settings. Valve also says the codec is “coming soon” to the Steam Link app for mobile devices, but the provided source material does not include a release date for mobile support. For now, the confirmed test path is the Steam client beta on Windows and macOS, plus Linux through the experimental SteamRT3 client.
The latency play is about moving the bottleneck, not deleting it
Valve’s explanation breaks Remote Play latency into four parts: encode, network, decode, and display. Pyrowave attacks the encode and decode side by using the GPU to process frames, which Valve says can produce extremely low end-to-end latency when the network is good. Phoronix also reports that Pyrowave uses the Vulkan API and describes it as a high-bandwidth, low-latency streaming codec.
That qualifier, “when the network is good,” is doing real work. A low-latency codec cannot compensate for packet loss, overloaded Wi-Fi, weak routing, or a network path that cannot absorb its bandwidth appetite. In strategic terms, Pyrowave appears to shift the Remote Play meta away from maximum compression efficiency and toward a local-network assumption: spend far more bandwidth to reduce codec delay and preserve more visual information.
Valve gives users a way to evaluate that tradeoff directly. The company says the Remote Play performance graph can visualize the total latency while streaming, and it reminds testers that total latency is the combination of video codec and network latency. That makes Pyrowave a feature worth testing empirically rather than enabling on faith. If your current Remote Play setup is already network-bound, Pyrowave may worsen stability. If your LAN has headroom and your current stream feels limited by encode or decode delay, the beta could be meaningfully different.
Image quality gets new options, especially for HDR and text-heavy streams
Pyrowave is not only about response time. Valve says the codec supports HDR and YUV 4:4:4, with HDR selected automatically when both host and client support it. YUV 4:4:4 is available as an option but is not enabled by default because Valve says it takes slightly more bandwidth and processing time.
The practical case for YUV 4:4:4 is sharper color detail. Valve specifically calls out desktop streaming and reading text on a 4K display as situations where users may want to turn it on. That distinction matters because game streaming and desktop streaming do not stress image quality in the same way. A fast-moving game can hide some chroma compression artifacts behind motion, while small UI text, browser windows, launchers, and strategy game interfaces can make color subsampling look immediately soft or frayed.
That is where Pyrowave could be especially interesting for the kind of player who uses Remote Play as a whole-PC extension rather than a couch-only game launcher. Strategy games, management sims, CRPGs, and desktop-heavy sessions tend to punish fuzzy text more than cinematic action games do. Valve has not published comparative image-quality captures in the provided material, so claims about visible gains need to wait for testing, but the available options show exactly what Valve is targeting: more precision when the user has enough bandwidth to pay for it.
Bandwidth tuning is now part of the feature, not an afterthought
Valve says Steam normally tunes the video stream for visual quality, with each frame using a constant size designed to look good. Higher frame rates increase the bandwidth required. The Remote Play quality slider can tune visual quality up or down, which directly affects bandwidth.
For users who want direct control, Valve says automatic bitrate can be turned off and Pyrowave can be set manually between 100 Mbit/s and 500 Mbit/s. That range reinforces the LAN-first nature of the Steam beta Remote Play update. At the low end, 100 Mbit/s is already beyond what many casual wireless setups can sustain consistently under real household conditions. At the high end, 500 Mbit/s is a deliberate claim on a large portion of a Gigabit link once overhead, other devices, and network conditions are considered.
The right way to treat Pyrowave in beta is therefore closer to tuning a competitive build than flipping a graphics preset. Start with the default behavior, enable the performance graph, compare latency and stability against your previous Remote Play codec, then consider manual bitrate only if the automatic settings do not fit your network. Valve’s own wording leaves room for mixed results, saying a user’s particular setup “may or may not benefit” because total latency depends on both the codec and the network.
A Linux-adjacent experiment with wider platform ambitions
Pyrowave’s rollout also has a notable Linux angle. Phoronix reports that the codec was developed by Hans-Kristian Arntzen, known for VKD3D-Proton, and says it follows earlier summer rumors about Valve working on a Pyrowave video encoding method for Steam Linux. The beta is broader than Linux, since Valve lists macOS and Windows availability, but Linux users are the ones asked to opt into the experimental SteamRT3 Steam Client to test it.
That platform split is worth watching because Valve’s Remote Play ecosystem now spans desktop Steam, SteamOS handhelds, living-room use, and eventually the Steam Link mobile app if Valve’s “coming soon” note holds. A high-bandwidth codec will not serve every endpoint equally. A wired SteamOS box or desktop client is a cleaner fit than a phone on variable Wi-Fi, and Valve has not provided mobile timing or mobile-specific requirements in the supplied material.
There is also a historical wrinkle in the rollout. GamingOnLinux reports that Pyrowave briefly appeared in a previous release and was then removed, interpreting its return as a sign Valve considers it ready enough for public testing. Valve has not framed this beta as final, and the codec remains experimental. The sensible expectation is iteration: bug fixes, platform expansion, and clearer guidance after users start feeding Valve real performance data across hardware, routers, GPUs, and display paths.
Should you enable the Valve Pyrowave video codec today?
If you are on the Steam client beta, have a wired Gigabit Ethernet LAN, and use Remote Play for latency-sensitive local streaming, Pyrowave is worth a controlled test. That is the audience Valve’s own requirements point toward. It is especially worth trying if you stream from a powerful host PC to another local machine, care about HDR, or want cleaner 4K desktop text with YUV 4:4:4 enabled.
If your Remote Play setup depends on Wi-Fi, powerline networking, a congested home router, or internet streaming outside the home, the case is weaker based on Valve’s stated bandwidth demands. The Steam Remote Play latency gains are conditional, and the codec’s five-to-ten-times bandwidth increase can turn a marginal network into the limiting factor.
The cleanest buyer-style advice for a beta feature is to avoid changing too many variables at once. Opt into the Steam client beta only if you are comfortable testing unfinished features. Enable Pyrowave in the advanced Remote Play client settings. Use the performance graph. Compare the same game, same resolution, same frame rate, and same network path before and after. If latency drops without instability or visible quality loss, Pyrowave earns its place in your setup. If the graph shows network pressure or inconsistent frame delivery, Valve’s older streaming codecs may remain the better practical choice until the experiment matures.