Transfer Files from Windows to Steam Deck with Warpinator

You can use Warpinator to send photos, videos, documents, save-file backups, or large folders from a Windows PC to a Steam Deck. Keep Warpinator running on the Steam Deck and a compatible client running on Windows, then send files through the same Local Area Network (LAN). You do not need to upload them to cloud storage or copy them to a USB drive first.

The complete process is: open Desktop Mode on the Steam Deck, install Warpinator through Discover, prepare the Windows client, match the Group Code on both devices, then send and accept the files. After the transfer, open the destination folder and verify the received files.

This guide is for a Steam Deck running SteamOS. If Windows is installed on your Steam Deck, the Discover and Flatpak installation steps do not apply.

Before Starting: SteamOS, Windows Client, and Local Network Checklist

Prepare the following items before starting:

Requirement	What to Check
Steam Deck running SteamOS	Confirm that you can open Desktop Mode.
Windows PC	Check whether it meets the requirements of the selected Windows client.
Local network	Confirm that direct network communication between both devices is possible.
Internet connection	It may be required for application downloads and installation.
Destination storage	Check whether sufficient free space is available for the incoming files.
Power and sleep settings	Check whether either device will enter sleep or suspend during the transfer.

Even if both devices are connected to the same router, communication between them may be blocked when one device uses Guest Wi-Fi. A PC connected through Ethernet and a Steam Deck connected through Wi-Fi can also communicate, provided the router permits traffic between wired and wireless clients.

Before sending a file, check whether the source file is available locally. If OneDrive or another cloud folder contains only a placeholder, download the complete file first.

For a large transfer, connect the Steam Deck to power and check the automatic sleep settings on both devices. Screen dimming and system suspend are different states; suspend can interrupt the connection.

Winpinator or Warpinator for Windows: Which Client Should You Use?

The Difference Between Linux Mint Warpinator and Unofficial Windows Clients

The original Warpinator is a local-network file-sharing application developed by Linux Mint. Winpinator and Warpinator for Windows are separate unofficial Windows implementations. The Linux Mint Warpinator project lists both Windows projects separately.

Although their names are similar, they are not the same application. The location of Preferences, Connection, or Send Files may differ between clients.

This guide uses Winpinator as the main Windows workflow. If you already use Warpinator for Windows, find the equivalent option for each task. Do not assume that its menu locations match Winpinator exactly. Our Warpinator for Windows setup guide provides additional information about identifying a Windows client.

Verify the Project Repository, Release Notes, and Installer Source

Start from the original project link before downloading a Windows installer. You can follow the Winpinator project link listed in the Linux Mint repository. The alternative Windows implementation has its own Warpinator for Windows repository.

When downloading, check:

Which project provides the installer.
What its release notes say about your Windows version.
Whether the installer architecture matches your PC.
Whether the download link points to a project-maintained release location.

Do not install a particular version only because an old tutorial mentions its version number. Similarly, if Windows displays a security warning, do not ignore it without verification.

How to Follow the Client Name, Version, and Interface in This Guide

Recording the client name and version at the beginning makes troubleshooting easier. A short note is sufficient:

Steam Deck: SteamOS version
Linux app: Warpinator version
Windows app: Winpinator version
Connection: PC Ethernet / Steam Deck Wi-Fi

The following instructions describe the main task performed at each stage. If your version changes a button label or menu location, follow the current application interface.

Step 1: Open Desktop Mode and Install Warpinator on Steam Deck

Steam Menu → Power → Switch to Desktop

Press the Steam button on the Steam Deck. Select Power → Switch to Desktop.

Wait for the desktop environment to appear. You will use Discover Software Center, Dolphin File Manager, and Warpinator from this environment.

Find Warpinator in Discover Software Center and Verify the Flathub Source

Open Discover from the desktop taskbar or application menu. Enter Warpinator in the search field.

Open the application details and check the name, project information, and package source. Warpinator’s Flathub application ID is:

org.x.Warpinator

You can compare the details with the Warpinator Flathub listing to identify the application. Then select Install.

Search with the On-Screen Keyboard and Launch the Installed Application

Place the cursor in the search field and use Steam + X to open the on-screen keyboard when required. You can also use an external keyboard.

After installation, launch Warpinator through Discover or the application menu. Allow the application to finish its initialisation.

Where to Check the Application Version and Flatpak Package Information

If Warpinator provides an About or application-information option, open it to check the version. Installed application details in Discover may also show package information.

Knowing the application version and Flatpak source is more useful for troubleshooting than only knowing that Warpinator is installed.

Step 2: Install the Compatible Windows Client and Prepare Network Access

Install the Selected Windows Client and Launch It

Install Winpinator using the project’s installer. Open the application after installation.

Do not create a large transfer queue immediately. Prepare the network connection, Group Code, and receiving location first.

Check Windows Firewall Application Permissions on a Trusted Home Network

If Windows Firewall displays a permission prompt, check the application name and publisher information. On your own trusted home network, start with the required Private network permission.

If you previously dismissed the prompt, check the application entry under Windows Security → Firewall & network protection → Allow an app through firewall. The wording may vary by Windows version.

Do not disable the entire firewall only to make a transfer work. Marking public Wi-Fi as a trusted Private network is also not an appropriate solution.

Identify the Active Wi-Fi, Ethernet, or Virtual Network Adapter

A Windows PC may have several network adapters:

Ethernet adapter
Wi-Fi adapter
VPN adapter
Hyper-V or another virtual network adapter

If Winpinator provides a network-interface selection option in its connection settings, select the adapter connected to the Steam Deck’s local network. If the PC uses Ethernet, selecting a Wi-Fi or VPN interface may cause a connection failure.

Step 3: Connect Steam Deck and Windows PC to the Same LAN

What to Check When the PC Uses Ethernet and Steam Deck Uses Wi-Fi

Both devices do not need the same connection type. The PC can connect to the router through Ethernet while the Steam Deck connects to that router through Wi-Fi.

However, problems can occur if the router blocks wired-to-wireless communication or the Steam Deck uses a Guest network.

Check the Local IPv4 Address, Subnet Mask, and Network Interface

On Windows, open Settings → Network & internet → Properties of the active connection to view the IPv4 address. You can also run ipconfig in Command Prompt when required.

In Steam Deck Desktop Mode, open the network connection details to view its local address.

Example:

Windows PC: 192.168.1.20
Steam Deck: 192.168.1.35
Subnet mask: 255.255.255.0

This is an example of a common same-subnet configuration. Matching only the first few numbers of the IP addresses is not a sufficient test for every network. The subnet mask and router configuration also matter.

Why Guest Wi-Fi, AP Isolation, and VLANs Can Block Device Discovery

A Guest Wi-Fi connection may provide internet access while blocking access to other local devices. The router may call this feature AP Isolation, Client Isolation, or another similar name.

Similarly, devices may not appear in the application if discovery traffic cannot pass between separate VLANs or subnets. For the first transfer, keep both devices on a familiar, trusted home LAN to reduce unnecessary configuration problems.

Select the Correct Local Interface When VPNs or Virtual Adapters Are Present

If a VPN is running, check whether its settings permit local-network access. Some VPN configurations also restrict LAN traffic.

First inspect the application’s selected interface and the VPN’s LAN setting. If you use a managed work PC, follow the organisation’s network policy.

Step 4: Match the Group Code and Check Device Discovery and Connection

Set the Same Group Code on Both Clients

Open Warpinator preferences on Steam Deck and connection preferences in the Windows client. Enter the same Group Code on both devices.

If you change the code on one device while leaving the old code on the other, they cannot communicate as members of the same group. Keep your code private. You do not need to copy a publicly available example code and use it permanently.

Identify the Correct Steam Deck Using Its Device Name and Local IP

Keep both applications running and check whether the other device appears in the peer list. Compare its device name and displayed local IP address to confirm that it is your Steam Deck.

If several Warpinator users are on the network, do not send files based only on a familiar-looking device name.

The Difference Between Device Listed, Connected, and Ready to Receive

A device appearing in the peer list means discovery has occurred. It does not necessarily mean the transfer connection is completely ready.

Separate these three stages:

Device listed: the other device has been detected.
Connection established: both clients have communicated successfully.
Transfer accepted: the receiver has accepted a particular incoming transfer.

Status labels may differ between clients. If a file remains pending, check whether confirmation is required on the receiving device.

Send a Small Test File Before a Large Folder

Send a basic .txt file or a small .jpg first. Accept it on Steam Deck and open it before sending a large folder.

A successful small test indicates that the basic installation, network connection, receiver approval, and destination write access are working.

Step 5: Send Files and Folders from Windows to Steam Deck

Select Steam Deck in the Windows Client and Use Send Files

Open the Steam Deck entry in Winpinator’s device list. Select the source file using Send Files, the file-selection control, or the equivalent option in your version.

If the source is a cloud placeholder, open it in Windows first and confirm that the complete content is available locally.

Select the Appropriate Option for Multiple Files and Folder Transfers

Use the file picker’s multiple-selection controls to send several files. To transfer a complete directory, use a separate Send Folder or folder-selection option if the client provides one.

If the file picker does not let you select a folder, do not immediately conclude that the application cannot send folders. Check whether a separate folder-transfer control is available.

Verify and Accept the Incoming Transfer Request on Steam Deck

Return to the Warpinator window on Steam Deck. Check the sender, file name, and file size before accepting the incoming request.

Do not accept an unexpected request that you did not initiate.

Understand Transfer Progress, Pending Approval, and Completed Status

Watch the transfer queue. If it shows Waiting, Pending, or an approval-related status, check the receiving device.

Do not close the application, put the PC to sleep, or leave Steam Deck Desktop Mode before the transfer completes. The applications may not need to remain in the foreground, but they must remain running and connected.

Step 6: Where Are Received Files Stored on Steam Deck?

Check the Receive Location in Warpinator Preferences

Find Location for received files or the equivalent setting in Warpinator preferences. The configured path is the first destination you should check.

Do not assume that a default path mentioned in another tutorial is unchanged on your installation.

Open the Destination Folder with Dolphin File Manager

Open Dolphin File Manager on Steam Deck and navigate to the configured receive location.

If you know the path, use Dolphin’s location bar. You can also use Warpinator’s shortcut for opening received files if your version provides one.

Change the Receive Folder When Required and Test Again

If the current destination is inconvenient, select another writable folder in preferences. Check whether an application restart is required for the change to take effect.

Send another small file and confirm that it arrives in the new location.

Verify the File Name, File Size, and File Contents

Do not depend only on the Completed status:

Compare the file name and extension.
Compare the source file size in Windows with the received file size on Steam Deck.
Open the received file and check whether it is usable.
For an important folder, inspect several subfolders and sample files.

For a particularly important large archive, you can compare SHA-256 checksums on both devices to check file integrity. Do not delete the source file before verifying the received copy.

How to Store Received Files on a microSD Card

Receive Files on Internal Storage First, Then Copy Them with Dolphin

For the first attempt, a simple method is to receive files in a writable internal-storage folder. Then use Dolphin to copy them to the required folder on the mounted microSD card.

This separates the network-transfer test from the microSD permission test. However, internal storage must have sufficient space for the temporary copy.

Check the Mount Path and Write Permission Before Receiving Directly to microSD

To receive files directly on microSD, open the card in Dolphin and check its current mount path. Do not copy another guide’s path without checking it. The path may differ according to the card label and system configuration.

Check whether files can be written to the destination folder. The card being mounted and Warpinator having write access are separate conditions.

What to Check When the Flatpak Sandbox Causes Permission Denied

A Flatpak application’s filesystem access may be restricted. If Dolphin can write to a folder but Warpinator cannot, inspect the application’s permissions.

First, select the destination folder again. If required, use a permission-management tool to inspect access to that specific destination. Do not begin by granting access to the entire home directory or host filesystem. The Flathub troubleshooting documentation also advises against broad filesystem access as a general fix.

Check Free Space and Perform a Small Write Test Before a Large Transfer

Check whether the microSD card has sufficient free space. Then send a small file directly to the selected destination.

If the received file opens correctly, start the larger batch. After copying files from internal storage to microSD, verify the final copy before removing unnecessary temporary files.

How to Send Files Back from Steam Deck to Windows PC

Select the Windows Device in Warpinator and Send the Files

Select the Windows PC in Warpinator on Steam Deck. Use the file-selection option to send a screenshot, document, or another file.

Keep the Windows client running and connected to the network.

Accept the Transfer in Windows and Open the Receive Folder

Accept the incoming request on Windows. Then open the receive location configured in the Windows client.

The Steam Deck destination folder and the Windows destination folder are separate settings. Changing one does not change the other.

Transfer Not Working? Troubleshoot According to the Symptom

Symptom	Check First	Next Action
Steam Deck is missing from the device list	Both applications are running, both devices are on a reachable LAN, and the Group Code matches.	Check the Guest network, selected interface, and device-discovery restrictions.
The device appears but shows Host Unreachable	The active network adapter and local IP address.	Inspect application-specific firewall permissions and connection settings.
The file remains pending	Receiver confirmation.	Accept the incoming transfer request.
Permission Denied	The receive path and destination write access.	Select a writable folder and send a small test file.
The transfer stops before completion	Sleep settings, Wi-Fi connectivity, and available storage.	Correct the cause, check the failed item, and resend it when required.

Steam Deck Is Not Detected: Check Device Discovery and the Local Network

First, confirm that both applications are running and that their Group Codes match. Then check whether Steam Deck is connected to Guest Wi-Fi.

After changing networks, reopen both applications. Avoid changing several settings at once because it becomes difficult to identify which change affected the result. Follow the Warpinator device-discovery troubleshooting guide for additional checks.

The Device Appears but Shows Host Unreachable: Check the Interface, IP, and Firewall

If the peer appears, discovery has worked at least partially. Check whether the Windows client is using an incorrect VPN or virtual network adapter.

Inspect the active local IP address, selected interface, and application firewall rule. Internet-facing router port forwarding is not an appropriate first step for this local connection problem. The Warpinator connection troubleshooting guide covers further connection-stage checks.

The Transfer Does Not Start: Check Receiver Approval and Destination Permissions

Look for an incoming request waiting for approval. If the transfer still fails after acceptance, check whether the destination folder is writable.

To separate a network problem from a storage problem, send a small file to a known writable internal-storage folder.

The Transfer Stops Halfway: Check Sleep, Wi-Fi Connectivity, and Free Space

Check whether Windows entered sleep or Steam Deck entered suspend. Also inspect Wi-Fi reconnections, router interruptions, and available destination storage.

Do not assume that an interrupted transfer will automatically resume correctly. Inspect the failed item’s status and received file, then resend it when required.

What to Check When Large-File Transfer Speed Is Low

Wi-Fi Signal, Wireless Band, and Router Congestion

Distance from the router, walls, and other traffic on the wireless network may reduce transfer speed. If supported, compare the connection using 5 GHz or another suitable wireless band with a strong signal.

A higher-frequency band will not always be faster. When the signal is weak, connection stability becomes more important.

Ethernet Link Speed and Source or Destination Storage Limits

Even when the PC uses Ethernet, its negotiated link speed may be low. Check the router port, cable, and adapter capabilities.

A slow microSD card or a busy source drive may also limit the transfer rate. A fast network does not guarantee that the destination can write data at the same speed.

MB/s vs Mbps: Read the Transfer Rate Correctly

Mbps means megabits per second. MB/s means megabytes per second.

Approximate unit conversion:

80 Mbps ÷ 8 = 10 MB/s

This is a unit conversion, not a guaranteed file-transfer speed. Protocol overhead, signal quality, and storage performance can reduce the actual result. Your broadband package speed is also not a direct measurement of LAN transfer speed.

Why Many Small Files and One Large File Can Transfer Differently

Sending thousands of small files requires more file-creation, metadata, and storage operations. A single large file with the same total size may transfer faster.

Creating an archive may help when transferring many small files, but include compression time, extraction time, and additional storage requirements in the comparison. Do not expect a particular speed without testing your own setup. See the Warpinator transfer-speed and network optimisation guide for more bottleneck checks.

The Difference Between Steam Game Installations, Save Files, and Mod Transfers

When to Use Steam Local Network Game Transfers for Installed Games

If your purpose is to copy installed Steam game content from another PC to Steam Deck, check Steam Local Network Game Transfers first. It is separate from a general document-sharing workflow.

Valve specifies its own eligibility and connection requirements. This feature is not a general method for transferring save files, local configuration files, or Steam Workshop content. Read the Steam Local Network Game Transfers requirements before using it.

Back Up Save Files and Configuration Files and Close the Game First

Close the game on both devices before sending save files. Keep a backup of the existing destination save.

The same game may use different save paths on Windows and SteamOS. Some Windows games use Proton compatibility directories on Steam Deck. Do not overwrite a folder without checking the game-specific path and save-format compatibility.

If Steam Cloud is enabled, replacing local files may produce a synchronisation conflict. Decide which copy you want to keep before resolving it.

Why Copying Mods or Non-Steam Files Does Not Complete Installation

Warpinator copies files. It does not automatically install dependencies, configure Proton compatibility, set up a mod loader, or correct executable permissions.

Sending a Windows game folder does not mean that the game will immediately run on Steam Deck. The relevant game or application’s setup instructions may still be required.

The Difference Between File Transfer and Automatic Folder Synchronisation

If you send a folder today and later change it on Windows, do not assume that the changes will automatically appear on Steam Deck.

Warpinator’s manual send workflow and continuous folder synchronisation are different tasks. Keeping changes matched regularly across both devices requires a dedicated synchronisation workflow.

Frequently Asked Questions

Does Warpinator Need an Internet Connection to Transfer Files?

Internet access may be required to install or update the applications. However, broadband is not necessary for the transfer when the required files are available locally and a working LAN connection exists between the devices.

This differs from the requirements of Steam Local Network Game Transfers. Our guide to using Warpinator without internet explains the difference between local connectivity and internet access.

Can Files Transfer When the PC Uses Ethernet and Steam Deck Uses Wi-Fi?

Yes, provided the router permits communication between wired and wireless devices. Guest networks, VLAN separation, or client isolation may prevent it.

Do Both Devices Need to Use the Same Steam Account?

No. A normal Warpinator file transfer does not require the same Steam account. Compatible clients, a reachable local network, and a matching Group Code are the important requirements.

Can I Send a Large Folder Without a USB-C Cable?

Yes. Use the compatible client’s folder-transfer option to send it through the LAN. Transfer time depends on the file structure, connection quality, and storage performance.

Where Should I Look for Files After the Transfer?

Check the receive location in the receiving device’s Warpinator or Windows-client preferences. On Steam Deck, open that folder with Dolphin File Manager.

How Can I Confirm That the Transfer Has Finished Before Returning to Gaming Mode?

Confirm that the queue contains no active or pending transfers. Then open the received files from the destination folder. Return to Gaming Mode after confirming that all required items are present and usable.