Valve ended Steam support for Windows 7, 8, and 8.1 on January 1, saying the app used a now-defunct embedded Chrome version; <1% of Steam users have those OSes
Context & Ripple Effects
Steam’s cutoff follows the broader retirement of the legacy Windows stack: Microsoft had ended its remaining paid security support, while Google had already set an end date for Chrome support on Windows 7 and 8.1. Valve says its embedded Chrome dependency can no longer be maintained on those systems.
The move also extends Valve’s demonstrated willingness to retire low-usage platform support, after its SteamVR support withdrawal from macOS. With fewer than 1% of Steam users affected, the maintenance burden—not the size of the installed base—appears decisive.
First-order effects
- Steam users still on Windows 7, 8, or 8.1 lose client support and must move to a supported operating system to retain an updated Steam experience.
- Valve can stop carrying compatibility work for an obsolete embedded Chrome version and concentrate desktop-client maintenance on supported platforms.
Second-order effects
- Games and Steam-adjacent tools that depend on the current client have less reason to preserve testing paths for the retired Windows releases, reinforcing upgrade pressure on the remaining users.
- The decision aligns Steam’s platform floor with the browser and operating-system support lifecycle, reducing the chance that an unsupported browser component becomes a distinct client-maintenance problem.
Third-order effects
- PC gaming distribution is becoming more tightly coupled to the support lifecycles of embedded web components and underlying operating systems; small legacy cohorts are increasingly unlikely to justify separate support.
- If this pattern persists, storefront operators will treat platform retirement as routine product maintenance, shifting the long-tail cost of legacy compatibility toward users and specialized third-party workarounds.
The trend: Consumer software platforms are narrowing supported operating-system ranges as browser dependencies and security maintenance make legacy compatibility disproportionately costly.