Valve has restated that Steam for Linux is not currently officially supported on Arm-based devices. On October 5, 2026 (Japan time), on the GitHub tracker for Linux Steam bugs, the Valve-side account kisak-valve replied to an Arm-device report and closed the post. At the same time, the company is developing a way to run existing PC games on Steam Frame, which uses Arm. A Steam client that runs on Arm is one thing; supporting general-purpose Arm Linux devices is another, and the difference comes down to how the client is distributed and which features each device supports.
The trigger wasn't launching games, but AV1 in Remote Play
The closed Issue #13689 concerns Remote Play, which receives video of a game running on another PC. The reporter had installed Armadaによる, a Fedora 44-based system, on an AYN Odin 3 handheld powered by the Qualcomm SM8750. The Linux kernel was 7.2.6, and they were using a beta native Arm64 build of the Steam client.
On that setup, HEVC video could be decoded in hardware. The problem was that although the receiving device's video-processing hardware is reported to support AV1, Steam did not advertise AV1 to the sending side as an available format, so it never appeared as an option. In other words, this was not a report that Steam wouldn't start at all, or that no games could run on Arm.
In response, kisak-valve wrote that "Steam for Linux is currently not supported on Arm-based hardware" and pointed to #4061, an earlier request for Arm support. The report was closed as a duplicate. No specific plan for fixing the AV1 handling was given.
Hardware that supports AV1 doesn't guarantee the app will choose it
According to the reporter, the formats reported by the Linux video device interface V4L2 included H.264 and HEVC, followed by VP9, and then AV01, which denotes AV1. But in the log tracing Steam's processing, the search stopped once it found H.264 or HEVC and never reached the AV1 entry.
The official Linux kernel documentation explains that the VIDIOC_ENUM_FMT call, which queries supported formats, works by incrementing an index from 0 and enumerating until it returns EINVAL, signaling the index is out of range. Even if a driver lists AV1, an application that doesn't query that far won't recognize it as an available format. A chip's capabilities and the path an app actually uses have to be verified separately.
However, this report alone can't establish the cause inside Steam's implementation. The trace log shown directly reveals only the queries for the leading H.264 and HEVC and the processing that selected HEVC; the claim that four formats are listed rests on the reporter's separate verification. Nor is there any basis for extending the Odin 3 observation to all Arm devices or to Steam Frame's AV1 support.
Still, it does show that simply building the client for Arm doesn't make every feature of a device usable. For video reception, users can select a feature only when everything is connected, from detecting supported formats to negotiating with the sender to actually decoding.
Comparing three kinds of "Arm support" against primary sources
For standard Steam for Linux, Valve's public README lists a 64-bit x86_64/AMD64 Linux kernel as a requirement. Graphics drivers and the core library glibc are needed in 32-bit as well as 64-bit versions. The support FAQ likewise treats the latest Ubuntu LTS and designated desktop environments as supported for the standard client. Saying it "runs on Linux" can't be read as including Arm devices with a different CPU.
Comparing materials as of October 2026, Steam Frame's Arm support and official support for using Steam on general Arm Linux devices do not coincide.
| Use case | Devices/configuration covered by the source | What the source says about scope |
|---|---|---|
| Standard Steam for Linux | x86_64/AMD64 kernel, with 64- and 32-bit libraries | Requirements listed in Valve's README. The October reply states Arm devices are currently not supported |
| Steam Frame | Snapdragon 8 Gen 3, Arm64 SteamOS. Windows x86 games run via Proton and FEX | Valve's developer documentation explains the execution method for this specific product. It does not guarantee general Arm Linux devices or all games |
| Steam Snap for Arm64 on Ubuntu | A package bundling the x86 Steam client with FEX | Ubuntu's call for testing describes it as experimental and states it is outside Valve's official support |
The table extracts the target devices, execution configuration, and scope of support from materials checked on October 6, 2026. It is not a comparison measuring game performance or compatibility. It shows that while development for Steam Frame is progressing, the same support can't be expected on other Arm devices.
With the Steam Snap, even if the package targets Arm64, the Steam client inside isn't necessarily Arm-native. Ubuntu's Mitchell Augustin explained in the January call for testing that the x86 Steam client and FEX were bundled. In an August 4 update, he said they are testing a native Arm64 build but plan to wait to migrate the Snap until it is offered to all users on the regular Steam download page. This is Ubuntu's migration decision, not an announcement by Valve of a formal release date.
When reading that "an Arm version of Steam exists," it helps to distinguish whether the client itself is built for Arm or whether an x86 build is being run through instruction translation. Beyond that, who accepts bug reports for which devices is a practical factor in everyday use.
Proton and FEX bridge two separate gaps
Steam Frame's developer documentation describes Proton, which bridges Windows and Linux, and FEX, which bridges x86 and Arm64, as separate items. To run existing Windows x86 games on an Arm device, two gaps must be crossed: the OS and the CPU instructions.
Proton is a compatibility layer that combines an improved Wine implementation with graphics API translation to run Windows games on Linux. DXVK, for example, translates DirectX calls to Vulkan. FEX, by contrast, translates x86 instructions into instructions Arm64 can execute. Making the Steam client Arm-native doesn't mean existing games have been rebuilt for Arm.
According to FEX's developers, FEX supports 32-bit and 64-bit x86 applications and can be used together with Wine and Proton. It also has a mechanism to forward OpenGL and Vulkan calls to Arm-side libraries, reducing the emulation burden. Rather than translating everything a game does in the same way, the design makes use of what the host can handle. This does not mean performance loss disappears, or that every Arm device would perform the same.
Valve also described, in its official GDC 2026 slides, work to broaden Proton's Arm64 support and run x86 games on Steam Frame's Arm chip. The aim stated in the developer documentation is to let developers focus on one best version of a game rather than maintain many separate builds. The thinking is that multiplying under-tested, under-updated alternate versions is unlikely to benefit users either.
What this approach leverages is the existing library of PC games. But on the device actually running them, functions such as GPU drivers and video processing also have to connect. The AV1 report highlights the gap between that device-specific implementation and what Valve currently accepts as supported.
An 11-year-old request, and Arm development that is moving
Issue #4061, which kisak-valve referenced, was opened on October 12, 2015 and was still open as an Arm support request when checked on October 6, 2026. The original post reported that installing Steam on an Arm device failed because it couldn't find i386 libraries. In the new report about 11 years later, things have progressed to receiving video on an Arm client, with the AV1 feature at issue. The two posts deal with different technical stages.
In 2026, Ubuntu called for testing of an Arm64 Steam Snap in January, and Valve described Proton and FEX for Steam Frame in its March GDC materials. In August, Ubuntu noted the conditions for moving to a native client, and in October Valve replied that general Arm Linux devices are currently unsupported. Progress in development and a limited scope of support are running in parallel.
The brief reply gives neither a release date for a general-purpose Arm version nor any statement that development is being abandoned. Whether Steam on Arm Linux has matured into a product depends not only on the client appearing through normal distribution channels but also on whether supported devices and features are clearly stated. Once that is in place, users will be better able to judge what to expect on their own devices without relying solely on reports that it launched.