Steam local network transfer not working? Check five gates

Start with the August client fix

Valve's August 3, 2026 stable-client notes include additional fixes for Local Network Game Transfers. That makes the current client the first checkpoint, not the last.

1. Let Steam finish its normal update on both devices.
2. Exit Steam completely on both devices, then reopen it.
3. Confirm the source and receiving device are both online.
4. Test one released game that is fully installed and current on the source.

Do not assume a client is current because its window was open during an update. A full restart gives you a clean version boundary.

Gate 1: both devices are on the same local network

“Same Wi-Fi name” is useful, but it is not always enough. A guest network, client isolation, a mesh node in isolation mode, a VPN, or separate wired and wireless segments can prevent local discovery.

• Use the same trusted home router for both devices.
• Leave guest Wi-Fi and public hotspots out of the test.
• Pause a VPN only if its provider supports that test and you can restore it immediately.
• If possible, test both devices on the same wired or normal private Wi-Fi segment before changing router settings.

If Wi-Fi itself is dropping, solve that first with the Windows 11 Wi-Fi disconnect guide. A broken network session cannot carry a reliable local game transfer.

Gate 2: the sharing setting permits the transfer

Steam's Local Network Game Transfers setting controls who may receive files from this machine. Use the narrowest choice that fits your test. A self-only setting will not serve another person's account, while a friends or broader setting changes who on the trusted LAN may request eligible game files.

Check the setting on the source computer, not only on the receiver. If you widen it for a household test, put it back afterward unless you want that ongoing sharing behavior.

Gate 3: the source computer is idle

Valve requires the source Steam client to be idle. A running game or another active download can make the machine ineligible as a host. Keep Steam open, close games normally, pause unrelated downloads, and leave the source at the desktop during the comparison.

A machine that sleeps halfway through the test also stops being a useful source. Keep it awake temporarily through normal power settings, then restore the previous setting when you finish.

Gate 4: the source copy is eligible

The source needs a released, playable, current copy of the same game. A preload, region-locked release, incomplete update, different depot state, or damaged source install can prevent a clean local copy.

• Open the game's Properties on the source and confirm no update is waiting.
• Make sure the source can launch the released game normally.
• Use a game available to the receiving account or device under Steam's rules.
• Do not move the source library or clear the whole download cache for this first test.

If the receiving drive is already nearly full, use the Windows storage accounting guide before blaming the LAN path.

Gate 5: local bytes actually move

Watch the receiving device's download page. A local-transfer message or source name is a clue, but the decisive observation is sustained local traffic and progress while internet traffic stays low. If the banner appears and progress sits at zero, or the download immediately returns to internet speed, record that exact sequence.

Test a small portion of one game. You do not need to redownload a large library to see whether the path starts. Stop after you capture the result.

Run one firewall comparison safely

Valve documents TCP port 27040 and UDP ports 27031 through 27036 for this local feature. Check that Steam is allowed on the private network profile and that a third-party firewall is not silently blocking local discovery or transfer traffic.

1. Confirm Windows labels the trusted home network as Private, not Public.
2. Review the existing Steam rule and its network scope.
3. If your security product provides a temporary, app-specific test, use it for one short comparison.
4. Restore the original rule immediately if the result does not change.
5. If it does change, replace the test with the smallest durable private-network rule the product supports.

Do not create a router port-forward. Local transfer does not need those ports exposed to the internet.

Steam Deck and launcher state matter

Valve's support guidance distinguishes supported desktop-client behavior from some Big Picture or custom-launcher states. When a handheld is involved, keep the desktop computer as the source for the cleanest comparison and follow Valve's current platform notes. Do not assume a device that can receive files is also eligible to host them in every mode.

Use the pattern to choose the next branch

It works after both clients update

The recent client regression is the best fit. Keep automatic client updates enabled and do not add firewall or library changes that the working path does not need.

It works only for your own account

The privacy setting is doing what it was designed to do. Decide whether the household needs a broader trusted-LAN option. Do not widen it simply to make the warning disappear.

The host appears, but local traffic stays at zero

Record both client versions, the source and receiving platform, game, sharing setting, host activity, and network type. This matches the recent symptom language more closely than an ordinary slow download.

No local source appears at all

Return to same-LAN visibility, guest or isolated networks, VPN state, the source's sharing setting, host activity, and private-network firewall scope. Change one condition at a time.

Local traffic starts, then the download slows

Watch source-disk read activity and receiving-disk write activity. A slow or busy drive can cap a transfer even when the LAN path is working. Do not call it a network failure until you separate transfer traffic from storage.

Build a clean support handoff

• Steam client version and restart time on both devices
• source and receiving platform, connection type, and whether either used guest Wi-Fi or a VPN
• sharing setting on the source computer
• game name, install state, and whether the source was idle
• the exact banner, zero-traffic, local-progress, or internet-fallback sequence
• private-network firewall rule and the result of one narrow comparison
• source read and receiving write behavior if local traffic begins

Remove account names, device names, IP addresses, library paths, and other private network details before posting screenshots.

Where OmniMend fits

If the host or receiving computer runs Windows, OmniMend for Windows can help keep local network, storage, process, and test evidence together. It does not run on SteamOS, change Steam's sharing policy, open firewall ports, transfer the game, or guarantee that Valve's client fix covers your case.

Use OmniMend help for product questions, or browse the help article library for related Windows diagnostics. Valve's current client and support rules remain the authority for this feature.