Valve has confirmed that the Steam client will stop receiving updates on 32-bit versions of Windows starting January 1, 2026, according to a report from Twisted Voxel citing the company. The move impacts an estimated 0.01% of Steam users still running Windows 10 32-bit — a sliver so small that most gamers will never notice, but one that forces a handful of holdouts into a long-overdue OS upgrade.

The cut-off: what we know so far

Once the calendar flips to 2026, the Steam client on any 32-bit Windows installation will no longer get security patches, feature updates, or official support from Valve. The company made clear that while the client "will remain functional for a limited period," its core features — the storefront, overlay, chat, and friends integration — rely on drivers and system libraries that have long since abandoned 32-bit compatibility. The result: a progressively degraded experience as these components drift out of sync.

The numbers driving the decision are brutal. Valve’s own Steam Hardware & Software Survey for August 2025 shows Windows 11 64-bit on 60.39% of systems and Windows 10 64-bit on 35.08%. Windows 10 32-bit? 0.01%. Windows 7 64-bit manages 0.07%, and all other 32-bit releases combined barely register. With usage that microscopic, maintaining a separate client build simply doesn’t add up.

Valve’s announcement echoes its previous platform retirements. In January 2024, the company pulled the plug on Windows 7 and 8/8.1, citing the same dependency dance with Chromium — the web engine that powers much of the client interface. When upstream vendors stop supporting a platform, Steam follows. The message this time is identical: upgrade to a 64-bit OS or lose access to a secure, updated client.

Who’s affected, and who can relax

If you’re running Windows 10 or 11 64-bit — and statistically, you almost certainly are — this change doesn’t touch you. Steam will continue to update normally, and all features will work as they always have. The only people who need to worry are the vanishingly few still booting into a 32-bit version of Windows.

That group is tiny for good reason. Most consumer CPUs sold in the last 15 years support 64-bit operations, and all modern drivers and applications target 64-bit environments. The holdouts are typically very old PCs, some niche industrial or embedded systems that happen to run Steam, or users who, for whatever reason, never migrated an ancient installation. If your machine can handle Windows 10 at all, it almost certainly has a 64-bit capable processor — meaning a move to 64-bit Windows is a software, not a hardware, problem.

There’s also a ticking clock from Microsoft. Windows 10 itself reaches end of support on October 14, 2025, just a few months before Valve’s cutoff. Staying on a 32-bit build of an already-retired OS is a double security risk, with no more official patches from either company. The practical takeaway: if you’re still on 32-bit Windows, you need to act now, not in January 2026.

Why now: a history of dropping dead weight

Steam’s decision isn’t a sudden pivot. It’s the latest in a series of legacy OS retirements that began in earnest with the end of Windows XP and Vista support in 2019, accelerated with the Windows 7/8 cutoff in 2024, and now lands on 32-bit architectures. Each retirement followed the same logic: when a platform’s market share falls to near zero and the software components Steam depends on stop supporting it, the cost of keeping a branch alive outweighs the benefit.

The key culprit this time is the embedded Chromium framework. Steam’s store, library, community, and overlay are rendered through a version of Chrome — and Google stopped providing updates for Chromium on 32-bit Windows long ago. Valve could fork the code and backport security fixes itself, but that’s an engineering nightmare for a handful of users. The same goes for GPU drivers, which have been 64-bit-first for years, and anti-cheat systems that increasingly demand a modern OS footprint.

Microsoft’s own roadmap amplifies the pressure. Windows 10’s end of support in October 2025 means no more security patches for any version, 32-bit included. Staying on a deprecated OS with an unsupported Steam client creates an unpatched stack that’s a tempting target for attackers. Valve’s move, in reality, forces a migration that many of the affected users should have started years ago.

Your move: practical steps to stay in the game

For the small number of players staring at a January 2026 deadline, the path forward is clear: leave 32-bit Windows behind. Here’s how to do it with minimal pain.

First, check your current system architecture. Open Settings → System → About, and look under “System type.” If it says “32-bit operating system,” you’re affected. If it says “64-bit,” you’re already safe — no action needed.

Next, back up everything you care about. Steam’s cloud saves will handle most game progress automatically if you’ve enabled the feature, but not every title uses it. Manually copy save files, configuration folders, screenshots, and any mods to an external drive or cloud storage. Also export a list of installed games via Steam’s backup feature if you want a reference for reinstallation.

Then, choose your upgrade path:

  • Clean install of 64-bit Windows on the same hardware: This is the most common route. Create a Windows installation USB using Microsoft’s Media Creation Tool (download from microsoft.com), back up your data, boot from the USB, delete all partitions during setup, and install Windows 10 or 11 64-bit fresh. After installation, install drivers, Steam, and restore your saves. Note: there is no direct in-place upgrade from 32-bit to 64-bit; a clean install is mandatory.

  • Buy a new PC: If your current machine is too old or fails Windows 11’s hardware requirements (TPM 2.0, Secure Boot, compatible CPU), a new PC with Windows 11 preinstalled is the simplest and most supportable path. Prices for capable gaming PCs have never been lower, and the shift buys you years of compatibility headroom.

  • Switch to Linux with Proton: For the technically adventurous, moving to a modern Linux distribution like Ubuntu or Fedora, paired with Steam’s Proton compatibility layer, can revive even aging hardware. Proton has matured dramatically and now runs a huge chunk of the Windows catalog — including many AAA titles — at near-native performance. Valve’s Steam Deck runs Linux and Proton by default, so compatibility data is readily available via ProtonDB.com. However, some games (especially those with kernel-level anti-cheat) still don’t work, so research your library before jumping.

Once you’ve migrated, reinstall Steam and log in. The client will sync cloud saves automatically, and you can re-download any games from your library. Take the opportunity to verify that everything launches correctly, and test multiplayer titles early to catch any missing dependencies.

Looking ahead: a post-32-bit Steam

Valve’s move is the final nail in the 32-bit Windows coffin. The client will likely receive a formal support bulletin in the coming months — possibly a pop-up warning inside Steam itself — with a firm date and migration reminders. Past deprecations show Valve tends to send in-client notices weeks or months in advance, so affected users should see a direct nudge.

Beyond 2026, Steam may eventually drop Windows 10 64-bit when its share craters and Chromium again moves on. But that’s years away; for now, the platform is stable and well-supported. The 32-bit cutoff is a cleanup operation, not a paradigm shift. For 99.99% of players, it’s a non-event. For the rest, it’s a long-overdue invitation to rejoin the modern PC gaming world — before the lights go out for good.