Valve Pyrowave Steam Remote Play Codec: High Bandwidth Beta
Wednesday, September 23, 2026By Indie Kings | September 23, 2026
Updated September 23, 2026: Valve's Pyrowave video codec is now available in Steam beta for Remote Play, using much more network bandwidth than older codecs while moving encode and decode work to the GPU, per the official Steam Remote Play homestream announcement. It supports HDR and optional YUV 4:4:4, but the codec does not guarantee lower latency on every network.
What Pyrowave changes
Per the official Steam Remote Play homestream announcement, Pyrowave is a new Remote Play video codec created by Hans-Kristian Arntzen. It is being tested in Steam beta on macOS and Windows, with Linux access requiring the experimental SteamRT3 Steam client.
The codec is designed for high bandwidth and low latency. It uses the GPU to encode and decode frames, but the announcement does not promise a fixed latency improvement for every game, network, or computer.
| Feature | What the Steam announcement says |
|---|---|
| Availability | Steam beta on macOS and Windows; Linux uses experimental SteamRT3 |
| Processing | GPU encode and decode |
| Bandwidth | Uses 5 to 10 times the bandwidth of other streaming codecs |
| Color | HDR support when host and client support it; optional YUV 4:4:4 |
| Manual control | Automatic bitrate can be disabled and set from 100 to 500 Mbit/s |
The bandwidth tradeoff
Pyrowave's main warning is simple: the codec can consume 5 to 10 times the bandwidth of other Steam Remote Play codecs, per Valve's announcement. A wired network with at least Gigabit Ethernet is the practical starting point suggested by the announcement.
That does not make Pyrowave better for every setup. A high bitrate can help preserve detail on a fast local network, but it can overwhelm Wi-Fi, mobile connections, or a remote link with limited capacity.
| Network situation | Reasonable first test | Reason |
|---|---|---|
| Wired Gigabit Ethernet | Try Pyrowave at automatic quality first | Matches the bandwidth profile described by Valve |
| Fast Wi-Fi | Test with a performance graph | Wireless conditions can still change during a session |
| Mobile or long-distance streaming | Keep another codec available | High bandwidth can create buffering or packet loss |
| Older PC or GPU | Compare before switching | Codec support does not prove hardware encode or decode performance |
GPU, HDR, and YUV 4:4:4
Per the Steam announcement, Pyrowave uses the GPU for encoding and decoding to reduce end-to-end delay when the network is good. The feature is not a blanket latency fix. Encoding, network transport, decoding, and display timing all contribute to the final result.
HDR is selected automatically when both the host and client support it. YUV 4:4:4 is optional because it uses more bandwidth and processing time, but it can help desktop text and some 4K content retain sharper color detail.
- HDR: Check host and client support before expecting the option.
- YUV 4:4:4: Useful for text and desktop streaming, with a bandwidth cost.
- Quality slider: Higher quality can increase bandwidth needs.
- Performance graph: Use it to see whether a change improves total stream latency.
How to test Pyrowave
The official Steam Remote Play announcement gives a short path for testing the codec. Treat the numbers as a starting point, not a benchmark for every system.
- Update Steam Beta on macOS or Windows. On Linux, enable the experimental SteamRT3 client in Steam settings.
- Open Remote Play advanced settings and select Pyrowave as the video codec.
- Leave automatic bitrate enabled for the first test, then watch the performance graph during play.
- If the local network is wired and stable, compare automatic quality with a manual bitrate between 100 and 500 Mbit/s.
- Test both game video and desktop text. YUV 4:4:4 is most relevant to the latter.
Record the Steam client version, GPU, connection type, game, and observed latency. A single favorable scene cannot establish a universal result, and a failed Wi-Fi test does not prove the codec itself is defective.
Who should try it
Pyrowave is most relevant to someone streaming a desktop or game across a fast local network and willing to trade bandwidth for image quality and potentially lower latency. It is less compelling when the connection is the bottleneck or when the client cannot decode the selected color mode.
For Steam Frame and other Valve hardware experiments, the codec is part of a broader remote-play and VR ecosystem. The earlier Indie Kings Steam Frame engineering article covers the headset's thermal and power design, while the Linux guide covers the wider desktop context. Neither article measures Pyrowave, so treat those links as background only.
FAQ
What is Pyrowave?
Per Valve's Steam Remote Play announcement, Pyrowave is a high-bandwidth, low-latency video codec using GPU encode and decode.
Is Pyrowave available on Linux?
The announcement says Linux access requires the experimental SteamRT3 Steam client. Availability can change as the beta evolves.
Does Pyrowave use less bandwidth?
No. Per the announcement, it uses 5 to 10 times the bandwidth of other streaming codecs.
Does Pyrowave always reduce latency?
No. It is designed to reduce delay, but network conditions, encode time, decode time, and display timing still matter.
What does YUV 4:4:4 do?
It offers more precise color sampling for some content, especially text, but uses more bandwidth and processing time.
Should I manually set the bitrate?
Start with automatic quality, then test manual control on a stable wired network. The announcement gives a 100 to 500 Mbit/s range.
Bottom Line
Pyrowave is a promising Steam Remote Play codec for high-speed local networks, not a universal latency switch. Test it with a wired connection, watch total latency rather than image quality alone, and keep a lower bandwidth codec available for travel or weaker Wi-Fi.
Related: Valve Steam Frame engineering deep-dive | Why indie PC gaming users are switching to Linux