Valve has released a minor but meaningful update to the Steam client that addresses a persistent issue affecting the Local Network Game Transfers feature, a tool designed to save users from the burden of repeatedly downloading large game files across multiple devices on the same network. For a period following a recent update, the functionality had been working intermittently or failing outright, causing Steam to default to downloading data from Valve’s servers even when a local transfer was possible. The fix, now live for both the desktop Steam client and the Steam Deck’s operating system, restores the ability to copy games and updates between computers and handhelds over a home network, significantly reducing internet bandwidth consumption and download times for users with multiple gaming setups.
The Local Network Game Transfers feature, formally introduced into the Steam ecosystem after extensive beta testing, allows a user to copy an already installed game from one PC or Steam Deck to another device on the same local network. Instead of fetching the entire installation from the internet—a process that can involve dozens or even hundreds of gigabytes of data—the system copies the files over a wired Ethernet or wireless connection from a source machine that already has the game installed. This is particularly useful in households with multiple gaming computers, a desktop and a laptop, or a primary gaming rig and a Steam Deck, where the same large titles like Call of Duty, Baldur’s Gate 3, or Cyberpunk 2077 are frequently shared. The reduction in internet traffic is substantial, benefiting users with data caps, slow connections, or simply a desire to avoid the wait of a full download.
A Welcome Correction After a Frustrating Regression
The problem that prompted this hotfix was not a failure of the feature from its inception, but a regression introduced in a prior update to the Steam client. According to Valve’s own patch notes published via the Steam News hub, the company identified that under certain conditions, the local transfer mechanism was breaking down. Users reported that when they initiated a transfer from a source device, the target device would either fail to recognize the available local copy or would begin the process but then abort, falling back to a full server-side download. This effectively nullified the purpose of the feature, forcing users to waste bandwidth and time despite having a perfectly good copy of the game sitting on another machine a few feet away.
In the official announcement for the update, which applies to Steam client build 1724325711 and the Steam Deck’s operating system, Valve stated: “Fixed a case where Local Network Game Transfers could fail to work.” While the phrasing is characteristically succinct, the underlying issue was disruptively widespread. For users who had grown accustomed to streaming games across their local network, the regression was a notable step backward. The update also appears to address the Steam Deck’s client specifically, ensuring that the handheld console can both send and receive transfers reliably.
How Local Network Game Transfers Actually Work
To fully appreciate why this fix matters, it is worth understanding the technical mechanism behind the feature. When a user initiates a game installation on a target device, Steam first checks the local network for any compatible source computers running the Steam client with the same game fully installed. The process relies on peer discovery over the local subnet, typically using UDP broadcasts or DNS-SD protocols. Once the source is identified, the target Steam client communicates a list of required files. The source then compresses and streams those files over the local connection, using HTTPS-like transfer protocols but applied to the local network instead of the internet.
The system is designed to be transparent: the user simply clicks “Install,” and Steam automatically decides whether a local transfer is faster than a remote download. A key strength is that it does not overwrite or repair existing files on the target unless necessary, and it can resume interrupted transfers. The bandwidth savings are enormous: a 100 GB game that would take hours to download over a typical broadband connection can be transferred between two PCs on a wired gigabit network in minutes. For Steam Deck users, this is especially beneficial, as it allows them to quickly populate their portable library from a desktop without draining their internet data cap or sitting through long download queues.
What the Fix Means for Multi-Device Households
The correction arrives at a time when multi-device gaming setups are more common than ever. With the Steam Deck establishing itself as a legitimate portable gaming platform, many users maintain a powerful desktop for high-fidelity gaming and a Steam Deck for on-the-go play. The Local Network Game Transfers feature is integral to this workflow. Without it, users were forced to either download the same 50, 100, or even 200 GB game twice—once on each device—or physically copy files using external drives, which is cumbersome and slow. The regression meant that even users who had successfully used local transfers in the past were suddenly experiencing failures, prompting frustration in community forums and support channels.
For example, a family with two gaming PCs and a Steam Deck might have Red Dead Redemption 2 (approximately 120 GB) installed on one desktop. Under the broken behavior, attempting to install the same game on the second PC or the Deck would trigger a full download from the internet, consuming up to 120 GB of data per transfer. For households with data caps of 1 TB per month, even a single such transfer could consume over 10 percent of the monthly allowance. The fix eliminates this unnecessary consumption, restoring the intended efficiency.
The Broader Importance of Local Network Transfers in Modern Gaming
The significance of this feature extends beyond convenience. As game file sizes continue to balloon—with many AAA titles exceeding 150 GB and some approaching 300 GB with high-resolution texture packs—the infrastructure of internet delivery faces increasing strain. Not all users have access to gigabit fiber connections. In regions with slower DSL, satellite internet, or mobile hotspots, downloading a single game can take an entire day or more and might exceed monthly data allowances. Local Network Game Transfers are a practical workaround that leverages the high-speed local infrastructure users already own to mitigate these limitations.
Furthermore, the feature supports the growing trend of households with multiple gamers. Whereas a decade ago a single gaming PC was the norm, it is now common to find two or three high-performance computers in one home, alongside handheld devices like the Steam Deck or the ASUS ROG Ally (which also supports Steam). Valve’s implementation of local transfers is one of the few cross-platform solutions that works seamlessly across these devices, provided they are on the same Steam account and local network. The failure of the feature thus had a disproportionate impact on these power users, who rely on it as a core part of their gaming logistics.
Technical Context: Why the Regression May Have Occurred
While Valve has not disclosed the exact root cause of the bug, it is possible to infer from the nature of the fix that the issue was related to changes in the Steam client’s networking stack. Over the past year, Valve has been rolling out a new WebSocket-based connection system for its chat and overlay features, as well as improvements to the download scheduler. It is plausible that a cross-functional dependency was broken during these modifications, causing the local transfer discovery or handshake process to fail. The fact that the fix applies to both the desktop client and the Steam Deck’s operating system suggests the bug existed in a shared component of the Steam runtime, rather than a device-specific driver or interface.
Users who experienced the problem reported that the Steam client on the target device would show a message indicating it was “Downloading from [device name]” but would then stall indefinitely or switch to a remote download without warning. This pattern is consistent with a failure in the file manifest negotiation, where the target device is unable to verify the integrity of the source files or cannot maintain the connection. Valve’s patch likely addresses a timeout parameter, a certificate validation issue, or a packet handling error in the local transfer protocol.
How to Verify That the Fix Is Applied
For users eager to confirm that the Local Network Game Transfers feature is working correctly again, the process is straightforward. First, ensure that the Steam client on all devices within the local network is updated to the latest version. On the desktop, this can be done by navigating to Steam > Check for Steam Client Updates. On the Steam Deck, updates are handled through the system settings under Settings > System > Software Updates. The current stable build includes the fix.
Next, verify that local network transfers are enabled in the settings. On the desktop, go to Steam > Settings > Downloads and ensure the “Allow local network game transfers” checkbox is ticked. On the Steam Deck, the same option exists under Settings > Downloads. Users can also set preferences for which devices are authorized to send or receive transfers, as well as limit transfers to only within the same network subnet or to allow them over the internet (though the latter is used for peer-to-peer cloud syncing, not direct local transfer).
To test the functionality, simply attempt to install a game on a target device that is already installed on a source device on the same network. The Steam download window should indicate that the data is coming from the local device by name, rather than showing a typical internet download speed. If the feature is working, the transfer will be significantly faster and will consume no internet bandwidth.
What This Means for Steam Deck Owners Specifically
The Steam Deck community was particularly affected by the regression, given how central the handheld is to the multi-device ecosystem. Many Steam Deck owners use their desktop as a primary library hub and periodically sync games to the Deck for travel or couch play. The Local Network Game Transfers feature is arguably more critical for the Deck than for desktop-to-desktop transfers, because the Deck’s storage is more limited and its wireless hardware can be slower than a wired desktop connection. The fix ensures that Deck owners can efficiently manage their library without relying on cloud saves alone, which do not transfer the game installation files themselves.
Valve’s commitment to maintaining feature parity between the desktop client and the Steam Deck’s SteamOS has been a significant factor in the Deck’s success. This latest fix reinforces that commitment. The company has been iterating on SteamOS and the client in tandem, and the simultaneous release of the fix for both platforms demonstrates an integrated development approach. For users who were considering purchasing a Steam Deck but were concerned about the logistics of managing game installations across devices, the reliable restoration of this feature removes a notable friction point.
Future-Proofing the Local Transfer Ecosystem
As Valve continues to expand the Steam ecosystem with new hardware and client features, the reliability of local network transfers will only grow in importance. The company is reportedly working on a next-generation Steam Deck, and there have been persistent rumors of a Steam console or set-top box. In a future where a household might have multiple Steam machines, a Steam Deck, and potentially a Steam-branded living room device, a robust and bug-free local transfer system is essential. The current fix, while minor in scope, represents an important piece of that long-term infrastructure.
Moreover, the feature’s utility is not confined to home users. Small gaming cafes, LAN centers, and esports venues that use Steam for game distribution can benefit enormously from being able to update multiple machines from a single local source. The failure of the feature in such environments would have caused significant operational headaches, as each machine would need to download updates individually, potentially saturating the venue’s internet connection. The fix ensures that these commercial and semi-commercial users can continue to rely on Steam’s local transfer capabilities.
A Small Update With Outsize Impact
In the grand scheme of Steam’s feature set, the Local Network Game Transfers fix is a modest patch. It does not introduce new functionality, change the user interface, or affect gameplay. But for the users who depend on it—and there are many—its impact is substantial. The update restores a level of convenience and efficiency that had been lost, and it does so without requiring any action from the user beyond updating the client. Valve has once again demonstrated its responsiveness to community-reported issues, a trait that has earned the company considerable goodwill over its three-decade history.
The broader lesson is that even mature platforms like Steam are subject to regressions that can disrupt established workflows. The fact that Valve identified and addressed this problem relatively quickly—within weeks of widespread reports—speaks to the company’s development agility and its prioritization of user experience. For users who have grown accustomed to the friction-free experience of local transfers, the return to normal operation is a quiet but welcome relief.
