Steam Pyrowave now in the standard client: codec remains experimental

Published Updated 4 min read
Steam Remote Play – offizielles Valve-Schaubild zu Streaming und Remote Play Together
Image: Valve / Steamworks · Image source

Report history

  1. Update

Update of 14 October 2026: Since the Steam client update of 13 October, Pyrowave is also part of the standard Stable channel. Valve continues to describe the new Remote Play codec explicitly as experimental. Users therefore no longer need to activate the Beta channel just to access the codec. This is according to Valve’s official Steam client release notes.

Pyrowave takes a different approach from conventional streaming codecs: it does not aim to squeeze as much picture quality as possible into as little bandwidth as possible. The concept deliberately reverses the priorities. On fast local networks, the data stream may be enormous, provided that encoding and decoding add virtually no additional delay.

Valve first introduced Pyrowave with the Beta update of 21 September 2026 as an experimental Remote Play option. In the patch notes, the company briefly describes the codec as a solution for “high bandwidth, low latency video streaming”. The technically rather unusual approach comes from Hans-Kristian Arntzen, known among other things for his work on VKD3D-Proton.

200 Mbit/s is not a problem here, but part of the idea

The architecture explains why Pyrowave is of particular interest for streaming within your own network. According to the project documentation, the codec targets bitrates of around 200 Mbit/s and more. For an ordinary internet stream, that would be wasteful. Over Gigabit Ethernet or a very fast home network, however, this bandwidth is available and can be traded for lower latency.

Pyrowave works intra-only. Put simply, the codec handles each frame largely independently, rather than laboriously calculating movements and image differences across many frames as typical video formats do. The image data is processed using a wavelet transform, similar to a JPEG 2000 approach. Encoding and decoding run entirely on the GPU via Vulkan compute shaders.

For the current implementation, Arntzen cites less than approximately 0.1 milliseconds for encoding and decoding at 1080p and less than roughly 0.2 milliseconds at 4K. These are developer figures for the codec itself and not a guarantee for the entire end-to-end latency of a Remote Play stream: network, capture, display and input still add to the total.

Steam Remote Play – official Valve diagram on streaming and Remote Play Together
Steam Remote Play streams games from a host PC to other devices. Pyrowave is designed to make particular use of fast local connections. Image: Valve / Steamworks.

Why Valve is testing a new codec for this

Steam Remote Play can transmit games from a gaming PC to other PCs, smartphones, tablets, televisions and other Steam Link devices. The fundamental problem with such systems is always the same: good picture quality, low bandwidth and low latency cannot all be optimised without limit at the same time.

H.264, HEVC and AV1 are excellent compression formats, but they have been heavily optimised to reduce video data efficiently. For its specific purpose, Pyrowave deliberately starts from a different point. Anyone who already has a fast network in the same house does not need to treat bandwidth as if it were scarce.

The developer also cites support for YCbCr 4:2:0 and 4:4:4. The latter is particularly interesting for PC desktops, text and fine UI elements, because colour information does not need to be subsampled as heavily as in many classic video streams.

Now in the stable Steam client, but still experimental

Although Pyrowave has been delivered via the standard Steam client since 13 October, Valve continues to classify the codec as experimental. This matters because its greatest advantage is at the same time its most obvious limitation. Anyone pushing 200 Mbit/s or significantly more through the network on a sustained basis needs a correspondingly stable connection. For ordinary Remote Play over the internet, the concept is therefore not automatically the better choice.

It is precisely within the home network that things could become interesting: a gaming PC in the study, a Steam Deck or handheld on the sofa, a second computer at the television. In other words, scenarios where the data only has to travel a few metres through a fast LAN or Wi-Fi, and every avoided millisecond makes control feel more direct.

With the standard client update of 13 October, the previously open question of whether the codec would be carried over from the Beta channel has been answered. However, the designation experimental remains: Valve is not making any commitments regarding specific end devices, identical results on every network, or a general replacement of existing streaming codecs. The changelog also lists new diagnostic and tuning options for Pyrowave, as well as improvements to Vulkan capture and image display.

Update source: Valve – Steam Client Update of 13 October 2026, Stable channel. The technical background on Pyrowave comes from the developer’s information and Valve’s original Beta release notes.

Write a comment
Your name and comment are public. The email address is optional and will not be published.