Valve pushed out two Steam Deck client updates in rapid succession this month, and together they amount to the biggest software shake-up the handheld has seen since SteamOS 3.0. A stable-channel release dated October 13, 2026 added a customizable home screen mode called Big Art Mode, two new screensavers, and roughly 96 individual changes spread across eight categories of the official changelog. Two days later, a beta-channel update took the architectural leap further, converting the Linux Steam client to a 64-bit application that now runs inside a Steam Runtime container. For a platform that just crossed into its fifth year on store shelves, that is a lot of plumbing work packed into one week.
None of this is cosmetic housekeeping. Valve is simultaneously selling a living-room box (the Steam Machine), a VR headset (Steam Frame), and a revived gamepad (the Steam Controller), all running variants of the same SteamOS foundation that increasingly defines Valve’s corner of the gaming hardware market and that the Steam Deck update is rebuilding underneath. The October patch cycle is the clearest sign yet that Valve is treating the Steam Deck client less like a single device’s firmware and more like the shared operating layer for an entire hardware family. Here is what actually changed, why the 64-bit rewrite matters more than Big Art Mode, and what it signals about where SteamOS goes next.
Don't miss new tech stories on Google
Add Shattered once in the Google app and our stories show up in your news suggestions.
What Changed in Valve’s October 2026 Steam Deck Update
The headline feature in the stable update is Big Art Mode, a new home-screen option that pulls the currently selected game’s artwork into the background of the interface, turning the Steam Deck’s library view into something closer to a console dashboard than a file browser. Valve also added a Personal Calendar card to the Recommended tab, giving the home screen a rotating source of content beyond the usual “recently played” rail, according to the changelog republished by Steam Deck HQ.
Screensavers are the second visible addition. Users can now enable a game-art slideshow pulled from recently played titles and in-game screenshots, or a retro-styled bouncing Steam logo that nods directly at the classic DVD-logo screensaver gag. Valve also opened the feature to custom screensavers, which can be dropped into a local config directory using the bouncing-logo asset as a template. It is a small feature on paper, but it is also the kind of personalization that handheld rivals running stock Windows 11 generally cannot offer without third-party software.
Underneath the new visuals, Valve tightened up power-state handling. The system now warns users explicitly before a power-menu action would shut down an active game, and it prompts for user switching if waking from sleep would kick an active session running elsewhere on the same Steam account. A new “Default to Desktop Mode” toggle lets users skip Big Picture Mode entirely on boot, a request that has circulated in Steam Deck forums since the device’s 2022 launch.
Steam Input, Proton Defaults, and Everyday Fixes
Steam Input, Valve’s controller-remapping layer, picked up roughly 22 individual changes in this cycle, more than any category besides the general quality-of-life bucket. The update adds new configuration windows for Steam Input and improves keyboard-glyph support in the footer when a Steam Deck is docked to a mouse and keyboard. For a platform whose entire value proposition rests on translating PC games built for keyboard and mouse into something playable with two trackpads and a gyroscope, continued investment in the input layer is arguably more consequential long-term than any cosmetic feature.
One change in particular will matter to anyone who side-loads non-Steam PC games: Windows binaries added as non-Steam games will now default to running through Proton automatically, rather than requiring users to manually flag them as Windows executables first. Valve also fixed a bug in which Windows games would incorrectly display as “Not Compatible” in the library view until a user manually selected a Proton version, and it made the “Select compatibility tool” dropdown permanently visible with the recommended Proton build promoted to the top of the list as a “Default” option.
Download performance on high-latency connections improved as well, Valve says, alongside a fix for a crash some users hit on older CPUs when starting downloads for games containing many identical files. Smaller but welcome fixes include a repair for desktop shortcuts that previously ignored saved launch options, improvements to the on-screen keyboard’s behavior after toggling Wi-Fi or waking from sleep, and a correction to the Recordings & Screenshots dialog, which had been failing to list every game with associated captures in its filter dropdown.
The Steam Client Goes 64-Bit on Linux
The more structurally significant change shipped two days later, on October 15, 2026, in a separate beta-channel push. Valve’s release notes state plainly that the Linux Steam client is now a 64-bit application, and that it runs inside a Steam Runtime container intended to provide a more consistent experience across different Linux distributions. The container approach borrows technology Valve already uses to sandbox individual Steam games through Pressure Vessel and the Steam Runtime, now applied to the client application itself rather than just the games running inside it.
The practical upside for users running SteamOS or a Linux distribution like Bazzite is fewer dependency conflicts between the Steam client and whatever system libraries a given distro ships. Containerizing the client means Valve can bundle a known-good set of libraries alongside it instead of hoping a user’s distribution has compatible versions installed. For a 32-bit client that has shipped with legacy baggage for the better part of two decades, moving to 64-bit also removes a long-standing technical ceiling on memory addressing and simplifies compatibility with modern 64-bit-only Linux libraries that have slowly been dropping 32-bit support altogether.
It is worth separating the two releases clearly, since coverage has sometimes blurred them together. The October 13 stable update carries Big Art Mode, screensavers, and the bulk of the Steam Input and general fixes. The 64-bit Steam Runtime container client is a beta-channel change dated October 15, documented in Valve’s own release notes and confirmed independently by PC Guide’s coverage of the patch cycle.
Remote Play’s Biggest Fix Pass in Months
Remote Play picked up 12 distinct fixes in the October cycle, the third-largest category after general fixes and Steam Input. Valve fixed broken HEVC hardware encoding on Steam Deck, a bug that had been forcing some streaming sessions to fall back to lower-quality H.264 even on hardware capable of HEVC. The update also enables Vulkan video decoding specifically when a Steam Deck is running the SteamRT3C Linux beta, Valve’s newer runtime track aimed at modernizing the graphics and media stack underneath SteamOS.
Several smaller but persistent annoyances were addressed in the same pass. A crash that occurred when users changed the hardware-encoding setting while not actively streaming is fixed, as is a cloud-save conflict bug that had been blocking some Remote Play launches outright. Valve also adjusted how the client handles low-bitrate connections, aiming to reduce the stuttering that Remote Play users on weaker home networks have reported. None of these are flashy additions, but Remote Play is one of the features Valve leans on hardest to argue that a Steam Deck, a Steam Machine, and a desktop gaming PC are really one continuous ecosystem rather than three separate purchases.
That framing matters more now than it did a year ago. With the Steam Machine positioned as a living-room box and the Steam Deck as the portable half of the same library, a broken Remote Play pipeline undermines Valve’s pitch that switching between devices should feel seamless. Fixing HEVC encoding specifically addresses a visible quality gap: H.264 fallback at the same bitrate produces noticeably blockier video, something enthusiast Steam Deck communities have flagged repeatedly since Remote Play’s expanded rollout.
October 2026 Steam Deck Update at a Glance
The table below summarizes the two releases that make up this update cycle, drawn from Valve’s official release notes and corroborating coverage.
| Release | Date | Channel | Headline Change | Source |
|---|---|---|---|---|
| Steam Deck client update | October 13, 2026 | Stable | Big Art Mode, screensavers, Steam Input overhaul | Valve / Steam Deck HQ |
| Steam beta client | October 15, 2026 | Beta/Preview | 64-bit Linux client, Steam Runtime container | Valve release notes |
| Remote Play fixes | October 2026 cycle | Stable + Beta | HEVC encoding fix, Vulkan decode on SteamRT3C | Valve changelog |
| Steam Input | October 2026 cycle | Stable | New configuration windows, 22 related changes | Valve changelog |
| Proton defaults | October 2026 cycle | Stable | Non-Steam Windows games default to Proton | Valve changelog |
Why Valve Is Investing in Software Right Now
Context matters here. Valve spent much of 2026 expanding SteamOS beyond the handheld it was originally built for. The Steam Controller returned to sale on May 4, 2026, priced at $99, and sold out within roughly 30 minutes of launch. The Steam Machine followed on June 29, 2026, starting at $1,049 for a 512GB configuration and reaching $1,428 for a 2TB bundle with the new controller, with Valve claiming the box delivers more than six times the Steam Deck’s graphics horsepower. Steam Frame, Valve’s SteamOS-based VR headset, rounded out the lineup the same year.
Every one of those products depends on the same underlying Steam client and SteamOS base the Steam Deck uses. A bug fixed in the Steam Deck’s Remote Play stack is a bug fixed for Steam Machine owners streaming to a different room. A 64-bit, containerized Linux client built for the Deck is also the client that ships on the Machine and the Frame headset. Framed that way, the October update is less a routine handheld patch and more Valve doing foundational maintenance on the operating system it is now betting an entire hardware ecosystem on, from a $99 controller to a four-figure living-room PC.
That dependency also explains a small but telling addition buried in the general-fixes category: pressing a controller’s system button can now request a connected TV switch to the Steam Machine as its active HDMI-CEC source. It is a one-line changelog entry, but it only makes sense in a world where Valve expects a single Steam account to move fluidly between a Deck in a backpack and a Machine under the television, exactly the cross-device pitch Valve has been building toward since Steam Frame’s reveal.
Breaking Down the Changelog by Category
Valve’s own changelog groups the October 13 update into eight labeled categories. Counting the individual bullet points in each section gives a clearer picture of where engineering effort actually went, beyond the two or three features that made headlines.
| Category | Changes Logged | Representative Example |
|---|---|---|
| General | 44 | Download speed improvements on high-latency connections |
| Steam Input | 22 | New Steam Input configuration windows |
| Remote Play | 12 | HEVC hardware encoding fix |
| Steam Controller Firmware | 7 | Firmware-level stability updates |
| Screensavers | 4 | New bouncing-logo and slideshow screensavers |
| Desktop Mode | 4 | Confirmation step added before switching modes |
| Home Screen | 2 | Big Art Mode toggle |
| Game Recording | 1 | Recordings & Screenshots dialog fix |
The lopsided weight toward the General and Steam Input categories, 66 of the roughly 96 logged changes between them, undercuts the narrative that this was primarily a cosmetic update built around Big Art Mode. Most of the actual engineering hours clearly went into stability, input handling, and the Proton compatibility layer that determines whether a given PC game runs on the Deck at all.
How to Install the Update: Stable vs Beta Channels
Most Steam Deck owners will get the October 13 feature set automatically through the stable update channel, which is the default setting on every Steam Deck shipped since 2022. Checking for the update manually is straightforward: open the Quick Access Menu, go to Settings, select System, and choose “Check for Updates” under Software Updates. Devices set to automatically download updates overnight should already show Big Art Mode and the new screensavers in the Customization settings menu.
The 64-bit Steam Runtime container client is a different story. That change ships through Steam’s client beta program, which is opted into separately from SteamOS’s own beta channels. On a Steam Deck, that means going to Settings, System, and switching the “Steam Beta Update Channel” option, then restarting Steam to pull the new client. Valve typically runs beta-channel features for several weeks before folding them into the stable branch, so users who want to stay on the tested, default path should expect the 64-bit client to arrive in stable sometime in the coming weeks rather than immediately. If an update appears to hang or the client won’t connect at all, it is worth checking whether the problem is on Valve’s end before troubleshooting the local install.
Users running third-party SteamOS forks like Bazzite, or community tooling such as Decky Loader plugins, should expect a short delay before full compatibility is confirmed, since container-level client changes have historically required coordination with projects that hook into Steam’s lower-level APIs.
Steam Deck’s Installed Base and Why Software Cadence Matters
Valve has never published an official lifetime sales figure for the Steam Deck, and that has not changed with this update cycle. Third-party tracking sites have pieced together an estimate suggesting cumulative sales in the range of roughly 4.95 million units by mid-2026, built from a string of earlier unofficial estimates rather than a single confirmed source. Treat that figure as a rough approximation, not a Valve-confirmed number.
What matters more for this story is cadence, not headcount. Valve ships Steam Deck client updates on a rolling basis rather than the scheduled seasonal firmware drops typical of console makers, and the October cycle is a reminder of how much surface area that covers: home screen behavior, input remapping, Proton compatibility, and the Remote Play streaming pipeline all moved in the same two-week window. That cadence sits against a backdrop of strong overall platform health; Steam’s broader storefront business, separate from Steam Deck hardware sales, posted a record month in September 2026. For a four-year-old handheld competing against a wave of newer Windows-based rivals, that update tempo is one of the few advantages Valve controls entirely in-house, since it owns both the hardware and the operating system end to end.
SteamOS vs Windows 11 Handhelds: The Competitive Landscape
The October update also sharpens the contrast between Valve’s software model and the Windows 11-based handhelds it competes against, including machines like the ROG Xbox Ally line. Valve has also pushed SteamOS itself onto some of those same rival devices as an alternative to Windows 11, with official support for several non-Valve handhelds expanding through recent SteamOS point releases. Windows 11 handhelds generally inherit Microsoft’s update cadence and desktop-first interface conventions, with manufacturers layering their own launcher software on top. SteamOS, by contrast, is built and shipped by the same company that controls the storefront, the compatibility layer, and the controller firmware, which is exactly how features like automatic Proton defaulting and HDMI-CEC-based device switching can ship as a single coordinated patch rather than requiring sign-off from a separate OS vendor.
That vertical control cuts both ways. Windows-based handhelds can run any PC game or launcher natively without a compatibility layer, while Steam Deck and other SteamOS devices still depend on Proton translating Windows API calls into something Linux can execute, which occasionally produces compatibility gaps Windows devices do not face. The October update’s push toward defaulting non-Steam Windows games to Proton automatically is itself an acknowledgment that this friction point is common enough to warrant removing a manual step. Valve is betting that tighter integration and faster, more coordinated updates outweigh the compatibility headroom Windows devices retain, and the pace of this month’s changes is the clearest evidence yet of how aggressively Valve intends to keep closing that gap.
From 2022 Launch to SteamOS 3.9: A Brief History
The Steam Deck launched in February 2022 running an early build of SteamOS 3, a shift away from the original Steam Machine project’s failed 2015 attempt at bringing SteamOS to living rooms. Where that first Steam Machine effort struggled with a thin game library and confusing hardware partnerships across a dozen manufacturers, the Steam Deck succeeded by being a single, Valve-built device with a clear use case: a handheld that could run a PC owner’s existing Steam library without repurchasing anything.
Each major SteamOS revision since then has expanded what the platform can do beyond gaming-first basics. Desktop Mode matured into something close to a full Linux desktop environment. Proton’s compatibility layer grew from covering a minority of the Steam catalog to running the overwhelming majority of actively played titles. The October update’s 64-bit Steam Runtime container client continues that trajectory, trading legacy 32-bit baggage for a more maintainable, sandboxed foundation that extends to the newer Steam Machine and Steam Frame hardware Valve introduced this year. Four years after a device many assumed would be a niche curiosity, SteamOS is now the operating system underneath four distinct product categories at once.
Developer and Community Reaction
Community coverage of the update, including reporting from Valve’s own Steam Deck news channel, has largely framed the patch as overdue rather than surprising, noting that several of the Steam Input and general fixes address complaints that have circulated in Steam Deck forums for multiple SteamOS revisions. The automatic Proton defaulting for non-Steam Windows games, in particular, has drawn attention from users who maintain large libraries of side-loaded, non-Steam titles, since it removes a manual configuration step every time a new game is added.
Reaction to the 64-bit client has been more muted publicly, in part because the change is invisible to most users unless something breaks. Linux enthusiasts tracking SteamOS and Bazzite development have flagged the Steam Runtime container approach as consistent with Valve’s broader strategy of sandboxing dependencies rather than requiring distribution maintainers to match Valve’s exact library versions, a pattern Valve has used for individual games through Pressure Vessel for several years before applying it to the client itself.
What Comes Next: 5 Predictions for Steam Deck and SteamOS
Based on the direction of this update cycle and Valve’s broader 2026 hardware push, a few trends look likely to continue:
- The 64-bit Steam Runtime container client should graduate from beta to the stable channel within the next several weeks, following Valve’s usual pattern of multi-week beta soak periods for architectural changes.
- Expect continued cross-pollination between Steam Deck, Steam Machine, and Steam Frame software updates, since all three now share the same SteamOS foundation and Valve has strong incentive to keep feature parity across devices customers may own simultaneously.
- Remote Play will likely see further encoding and latency improvements as Valve leans harder on the pitch that a Steam Machine and a Steam Deck form one continuous library, rather than two separate purchases.
- Pressure will keep building on Valve to publish an official installed-base number for the Steam Deck, particularly as third-party estimates circulate without Valve confirmation, though Valve has shown no sign of changing that policy.
- Any future Steam Deck hardware revision will almost certainly inherit the 64-bit, containerized client as its baseline rather than shipping with the legacy 32-bit Steam client, making this month’s beta change a foundation-laying step rather than an isolated fix.
None of these are guaranteed, but they follow directly from the pattern Valve has set across its 2026 SteamOS releases: ship core architecture changes quietly through beta channels, pair them with visible user-facing features in the stable channel, and keep every device in the Steam hardware family synchronized on the same underlying software stack.
Frequently Asked Questions
What is Big Art Mode on Steam Deck?
Big Art Mode is a home-screen display option added in the October 13, 2026 stable update. It shows large artwork for whichever game is currently selected in the library view, turning the Steam Deck’s home screen into a more console-like dashboard instead of a simple list.
How do I enable the new Steam Deck screensavers?
Screensavers are accessible through Settings, then Customization, on an updated Steam Deck. Users can choose between a game-art slideshow pulled from recent play sessions and screenshots, or a retro-style bouncing Steam logo, and can also install custom screensaver files into a local configuration directory.
Is the 64-bit Steam client available on the stable channel yet?
No. As of October 19, 2026, the 64-bit Linux client running inside a Steam Runtime container is only available on Steam’s client beta channel, which must be enabled separately from SteamOS’s own update settings.
Will the 64-bit client fix game compatibility issues?
Valve has not framed the 64-bit, containerized client as a direct fix for individual game compatibility problems. Its stated purpose is a more consistent experience across different Linux distributions and removing dependency conflicts between the Steam client and a user’s installed system libraries, which is a separate layer from Proton’s game-level compatibility work.
Does this update affect the Steam Machine or Steam Frame?
Both devices run on the same SteamOS foundation as the Steam Deck, so fixes and features shipped in this update cycle, including Remote Play improvements and the eventual stable rollout of the 64-bit client, are expected to reach Steam Machine and Steam Frame as well, though Valve has not published a device-specific rollout schedule.
Why did my non-Steam Windows games suddenly default to Proton?
Valve changed the default behavior in the October update so that any Windows executable added as a non-Steam game automatically runs through Proton instead of requiring the user to flag it manually first. This also fixed a related bug where some Windows games incorrectly displayed as “Not Compatible” until a Proton version was selected by hand.
How many Steam Decks has Valve sold?
Valve has not released an official lifetime sales figure. Independent tracking estimates put cumulative Steam Deck sales at roughly 4.95 million units by mid-2026, but that number is assembled from third-party projections rather than a confirmed company disclosure.
Where can I read Valve’s full official changelog?
Valve posts official Steam Deck client release notes through its Steam Community announcements and the Steam Deck news page, with community sites like Steam Deck HQ typically republishing the full bullet-point changelog within hours of release.