Transfer Files Between Windows & Linux

Yes, Winpinator is safe. The entire source code is publicly available on GitHub under the GPLv3 license, which means anyone can audit it for security issues. The installer has been scanned on VirusTotal with clean results across major antivirus engines.

One thing that catches people off guard: Windows Defender SmartScreen will likely block the installer the first time you run it. This happens because the .exe is not digitally signed with an expensive code-signing certificate, and it has a relatively low download count in Microsoft’s reputation database. The software itself is clean. To proceed, click “More info” and then “Run anyway.”

Winpinator transfers files only over your local network. No data passes through external servers or leaves your LAN. The application uses libsodium and OpenSSL for encrypted transfers, and a shared group code acts as a pairing secret between devices.

• Source code: fully open on GitHub (350+ stars)
• No ads, no telemetry, no tracking, no bundled software
• Transferred files get Windows “Zone Information” tagging for added security
• LAN-only operation — nothing goes through the internet

Pro tip: If Windows Defender flags the installer, right-click the downloaded file, go to Properties, and check “Unblock” before running it. This avoids the SmartScreen popup entirely.

For verified download links, see our download section.

The official Winpinator download comes from two sources: the developer’s website at winpinator.swisz.cz and the GitHub releases page at github.com/swiszczoo/winpinator/releases. Both host the same v0.1.2 installer files.

Be careful with search results. Several third-party download sites repackage the installer or wrap it with their own bundlers. A common mistake is downloading from sites like “warpinator.com,” which is not affiliated with the original Linux Mint Warpinator project. The safest approach is to get the file directly from GitHub releases, where you can verify the file hash against the published checksums. Winpinator is also available on Chocolatey (choco install winpinator) for users who prefer package managers.

• GitHub releases: github.com/swiszczoo/winpinator/releases (primary source)
• Developer site: winpinator.swisz.cz (SSL certificate was expired but has been addressed)
• Chocolatey: choco install winpinator for automated install
• Installer size: approximately 15-20 MB for both 32-bit and 64-bit versions

Pro tip: Using Chocolatey handles installation and future updates with a single command, and the package is community-maintained with checksum verification built in.

Grab the latest version from our download section, which links directly to the official sources.

Yes, Winpinator contains no malware, spyware, or adware. It is a genuine open-source project with every line of code visible on GitHub for public review. The repository has 350+ stars and 140+ commits from the developer Lukasz Swiszcz.

The application collects zero user data. There are no analytics calls, no crash reporting services, and no network requests beyond your local LAN. Winpinator does not even require an internet connection to function — it works entirely over your local router or hotspot. Transfer history is stored in a local SQLite database on your machine, not in the cloud.

Some antivirus programs may flag the installer as “PUA” (Potentially Unwanted Application) due to the NSIS installer format and lack of a code-signing certificate. This is a false positive. You can verify this by uploading the installer to VirusTotal yourself, where the detection rate from reputable engines sits at 0/70+.

Pro tip: After transferring files, Windows may block them with a “security zone” marker. Right-click the received file, open Properties, and click “Unblock” if you see that checkbox at the bottom of the General tab.

Check our features overview for more on the security architecture.

Yes, Winpinator works on Windows 11 without issues. It also supports Windows 10, Windows 8.1, and Windows 8. Windows 7 works with the Universal C Runtime (UCRT) update installed, though toast notifications are unavailable on that older OS.

Winpinator v0.1.2 ships as both 32-bit and 64-bit installers. On a modern Windows 11 machine, go with the 64-bit version. The system requirements are minimal: 128 MB of RAM, about 50 MB of disk space, and a 1024×768 display. The installer automatically checks for and installs the Visual C++ Redistributable if your system needs it.

On the other end, you need a Linux device running Warpinator. This covers Linux Mint (where Warpinator comes preinstalled), Ubuntu, Fedora, and any distro that can install Warpinator via Flatpak or native packages. Steam Deck users with SteamOS are fully supported too — Warpinator is one of the most popular file transfer tools in the Steam Deck community.

• Windows 11 (all versions): fully supported
• Windows 10 (version 1607+): fully supported
• Windows 8/8.1: supported
• Windows 7: works with UCRT update, no toast notifications

Pro tip: If you are using Windows 11 with a VPN active, Winpinator may pick the wrong network interface. Go to Preferences and manually select your Wi-Fi or Ethernet adapter instead of leaving it on “Automatic.”

See full hardware and software specs on our system requirements page.

Winpinator runs on almost any Windows PC from the last 15 years. The minimum requirements are low: 128 MB of RAM, 50 MB of free disk space, and a screen resolution of at least 1024×768. You need Windows 8 or later for full functionality.

The application is built in C++ with wxWidgets for the UI, so it runs natively without .NET or Java. The installer bundles its dependencies (gRPC, protobuf, libsodium, OpenSSL, zlib) and checks for the Visual C++ Redistributable automatically. Both 32-bit and 64-bit builds are available, so older machines with x86-only CPUs are covered.

The bigger factor is your network. For practical file transfers, you want:

• Both devices connected to the same Wi-Fi network or LAN
• 5 GHz Wi-Fi band for speeds around 20-35 MB/s (2.4 GHz gives roughly 6-10 MB/s)
• Ethernet on at least one device pushes speeds to 35-60 MB/s on Wi-Fi 6
• Firewall rules allowing UDP port 5353 (mDNS) and TCP ports 42000-42001 (transfer and registration)

Pro tip: If you are transferring large files (10+ GB), plug one device into Ethernet via cable. Even connecting just the Windows PC to your router with an Ethernet cable while the Linux machine stays on Wi-Fi can double or triple your transfer speeds.

Full specs are listed in our system requirements table.

Yes, Winpinator pairs with the Steam Deck through Warpinator, which runs on the Deck’s SteamOS (Arch Linux). Many Steam Deck owners call this combination a “godsend” for moving game files, ROMs, and media from their Windows PC to the Deck wirelessly.

To set this up, switch your Steam Deck to Desktop Mode, open the Discover store (or use flatpak install flathub org.x.Warpinator), and install Warpinator. On your Windows PC, install Winpinator. Make sure both devices sit on the same Wi-Fi network, and that the group code matches in both apps (the default is “Warpinator”).

A few things to know about Steam Deck transfers specifically:

• Files land in the ~/Warpinator folder on the Deck by default — not your Steam library
• If you are transferring games, you still need to move them to the correct Steam library folder and let Steam “discover” them
• The Flatpak version of Warpinator may not have permission to write to your SD card. Use Flatseal to grant filesystem access
• Typical transfer speed on Steam Deck Wi-Fi: 15-25 MB/s, depending on distance from router

Pro tip: Before your first transfer, open Warpinator on the Steam Deck, go to Preferences, and change the save location to your SD card or Steam library path directly. This saves you from manually moving files after each transfer.

Read our getting started guide for the full setup walkthrough.

Yes, Winpinator is 100% free with no paid tiers, no premium features locked behind a paywall, and no in-app purchases. The software is released under the GNU General Public License v3.0, which means it will remain free and open-source permanently.

There is no registration, no account creation, and no email required to download or use Winpinator. The application has no ads and collects no user data. It works entirely offline on your local network — you do not even need an active internet connection after downloading the installer.

Because Winpinator transfers happen over your local router, they do not count against your ISP data cap. The traffic never leaves your home network. You could transfer 500 GB of files and your ISP would not see a single byte of it. This is a common question from users with metered internet plans.

For context, the original Warpinator on Linux is also free and maintained by the Linux Mint team. Winpinator is a third-party port written by developer Lukasz Swiszcz, who built it from scratch in C++ to bring the same functionality to Windows.

Pro tip: You can even use Winpinator on a mobile hotspot with cellular data disabled. As long as both devices connect to the same hotspot, transfers work without using any mobile data.

Head to our download section to get started for free.

Winpinator uses the GNU General Public License version 3.0 (GPLv3). This is a copyleft license, meaning the source code must remain open and any modifications or forks also need to be released under the same license.

For everyday users, the GPLv3 license means you can download, install, use, copy, and distribute Winpinator freely. There are no usage restrictions for personal, educational, or commercial use. You can install it on as many computers as you want without any licensing fees or activation keys.

If you are a developer or IT administrator, the GPLv3 also gives you the right to modify the source code. The full C++ codebase, including the wxWidgets UI code, gRPC networking layer, and mDNS discovery system, is available at github.com/swiszczoo/winpinator. The project has about 140 commits and uses C++14 with CMake as the build system.

• Personal use: unlimited, free
• Business/enterprise use: permitted, no license fees
• Redistribution: allowed if you include the GPLv3 license text
• Modification: allowed, but modified versions must also be GPLv3

Pro tip: If you want to build Winpinator from source, the GitHub repository includes detailed build instructions using MSYS2/MinGW64 and vcpkg for dependency management.

Learn more about what Winpinator offers on our features page.

Installing Winpinator takes about two minutes. Download the 64-bit installer (or 32-bit for older machines) from the official GitHub releases page, run the setup file, and follow the NSIS installer prompts.

Here is the full process:

1. Download the installer from our download section (approximately 15-20 MB)
2. Double-click the downloaded .exe file. Windows SmartScreen may show a warning — click “More info” then “Run anyway”
3. Choose your installation directory (the default C:\Program Files\Winpinator works fine)
4. The installer checks for the Visual C++ Redistributable and installs it if missing
5. Click “Install” and wait a few seconds for the files to copy
6. Launch Winpinator from the Start menu or desktop shortcut

After the first launch, open Preferences and do two things: select your active network interface (Wi-Fi or Ethernet) instead of “Automatic,” and confirm that the group code matches the one set in Warpinator on your Linux device. The default group code is “Warpinator” on both sides.

Winpinator automatically adds itself to the Windows Explorer “Send to” context menu. You can right-click any file in Explorer and choose “Send to > Winpinator” to start a transfer.

Pro tip: If you use Chocolatey, you can skip the manual download entirely: run choco install winpinator in an elevated terminal and it handles everything, including the Visual C++ dependency.

For a more detailed walkthrough, check our getting started guide.

Both devices need to be on the same local network, and the group code must match. That is really the only requirement. No port forwarding, no account creation, no cloud service involved.

The setup works like this: Winpinator on Windows uses mDNS (multicast DNS) to discover Warpinator instances on the same network. When both apps have the same group code and are on the same subnet, they find each other automatically within a few seconds. You will see the Linux device appear in the Winpinator window with a green “Online” status indicator.

1. Install Winpinator on Windows and Warpinator on Linux (from your distro’s package manager or Flatpak)
2. Connect both devices to the same Wi-Fi network
3. Open Winpinator, go to Preferences > Connections, and check the group code (default: “Warpinator”)
4. On the Linux side, open Warpinator preferences and confirm the same group code
5. In Winpinator, manually select your Wi-Fi or Ethernet adapter under the network interface dropdown — do not leave it on “Automatic”
6. Both devices should appear in each other’s device list within 10-15 seconds

If devices do not appear, the most likely causes are: different subnets (some routers isolate 2.4 GHz and 5 GHz bands), a firewall blocking UDP port 5353, or the network interface set to the wrong adapter.

Pro tip: If automatic discovery fails, try restarting both applications. Winpinator supports both v1 and v2 Warpinator registration protocols, so it should work with any recent version of Warpinator.

Read the full connection guide in our getting started section.

Most installation problems come down to three things: SmartScreen blocking, a missing Visual C++ Redistributable, or a previous Winpinator instance still running in the background.

The SmartScreen issue is the most common. Because Winpinator’s installer is not code-signed, Windows treats it as an “unrecognized app.” Click “More info” on the blue SmartScreen window, then “Run anyway.” If your organization’s group policy blocks unsigned executables entirely, ask your IT administrator to whitelist the installer or use the Chocolatey package instead.

For the Visual C++ issue: Winpinator v0.1.2 checks for the correct redistributable version and installs it automatically. Earlier versions (v0.1.0 and v0.1.1) had a bug where the version check failed and showed an error dialog. If you are on an older version, update to v0.1.2 or manually install the Visual C++ 2015-2022 Redistributable from Microsoft’s website.

1. SmartScreen block: “More info” then “Run anyway,” or right-click the file > Properties > Unblock
2. Visual C++ missing: download the latest VC++ Redistributable from microsoft.com/en-us/download
3. Installer hangs: check Task Manager for an existing winpinator.exe process and end it before reinstalling
4. Antivirus quarantine: add an exclusion for the installer file in your antivirus settings

Pro tip: If the installer fails repeatedly, try running it as Administrator (right-click > “Run as administrator”). Some systems require elevated permissions to install the Visual C++ runtime.

See our system requirements for supported Windows versions and dependencies.

Device discovery failures are the most reported issue with Winpinator, and the fix is almost always the same: manually select the correct network interface instead of using “Automatic.”

When Winpinator is set to “Automatic” for the network interface, it sometimes picks the wrong adapter — a VPN tunnel, a Docker bridge, or a disabled Wi-Fi adapter. This sends mDNS discovery packets to the wrong network, so the Linux device never sees them. Go to Preferences in Winpinator and explicitly choose your active Wi-Fi or Ethernet adapter from the dropdown.

If that does not fix it, work through this checklist:

1. Confirm both devices are on the same Wi-Fi network (some routers separate 2.4 GHz and 5 GHz into different subnets)
2. Check that the group code matches exactly on both sides (it is case-sensitive)
3. Open Windows Firewall and allow Winpinator through, or manually open UDP 5353 and TCP 42000-42001
4. Restart both Winpinator and Warpinator — close fully (the X button minimizes to tray; use “Exit and stop the service” instead)
5. Disable any active VPN on the Windows machine
6. If using Warpinator via Flatpak, make sure it has network permissions (check with Flatseal)

Pro tip: If devices still cannot find each other after trying everything above, try incrementing the port numbers by +1 on both devices (from 42000 to 42001, and 42001 to 42002). This resolves a known issue where a Warpinator update changed the registration protocol.

More connection advice in our getting started guide.

Transfer failures usually come from unstable Wi-Fi or a Warpinator version mismatch between the Windows and Linux sides. Unfortunately, Winpinator does not support resuming interrupted transfers — if a transfer fails, it restarts from scratch.

Unstable Wi-Fi is the most common cause. If you are far from your router or on a congested 2.4 GHz band, large transfers (1 GB+) can time out mid-transfer. Switching to 5 GHz Wi-Fi or connecting one device via Ethernet cable makes a dramatic difference. Users on Reddit report going from constant failures on 2.4 GHz to flawless 30+ MB/s transfers after switching.

The version mismatch issue happens when Warpinator updates on the Linux side and changes its registration protocol. Winpinator v0.1.2 supports both v1 and v2 protocols, but some edge cases still cause “Waiting for two-way connection” errors that eventually time out.

• Switch to 5 GHz Wi-Fi or connect one device via Ethernet
• Move closer to your router if on wireless
• Close background applications using heavy bandwidth (streaming, downloads)
• Try incrementing ports by +1 on both devices if you see “connection failed” errors
• For very large files (10+ GB), consider splitting them into smaller archives first

Pro tip: Enable compression in Winpinator’s preferences (Preferences > Transfers > Use compression). This helps significantly with text files, documents, and uncompressed data, though it adds overhead for already-compressed formats like .mp4 or .zip.

Check our features page for details on transfer protocols and compression support.

If Winpinator refuses to start, the most likely cause is a previous instance still running silently in the system tray, or a corrupted network interface setting in the configuration.

Winpinator has an unusual close behavior: clicking the X button does not actually quit the program. It minimizes to the system tray and keeps running in the background. If you try to launch it again while the old instance is still there, nothing visible happens. Open Task Manager (Ctrl+Shift+Esc), find winpinator.exe in the process list, and end it. Then relaunch.

A more serious crash scenario involves the network interface setting. If you previously selected a network adapter that has since been removed or disabled (unplugging a USB Wi-Fi dongle, for example), Winpinator crashes immediately on startup before you can reach the preferences to fix it. This is a known bug (GitHub Issue #26).

1. Open Task Manager and kill any running winpinator.exe processes
2. Try launching Winpinator again
3. If it still crashes instantly, open Registry Editor (regedit), navigate to HKEY_CURRENT_USER\Software\Winpinator, and delete the network interface key
4. If the registry approach feels too risky, uninstall and reinstall Winpinator — this resets all settings
5. Make sure the Visual C++ Redistributable 2015-2022 is installed

Pro tip: To properly exit Winpinator instead of minimizing it, right-click the system tray icon and select “Exit and stop the service.” A community feature request (GitHub Issue #36) asks for the X button to actually close the app, but this has not been implemented.

View the minimum software dependencies on our system requirements page.

Winpinator does not have a built-in auto-updater. To update, you need to download the latest installer from the GitHub releases page and run it over your existing installation.

The current version is v0.1.2, released on February 18, 2022. This version fixed a bug with the Visual C++ Redistributable version check and resolved an issue where an error dialog appeared when the app could not find account pictures on the system. Settings are now saved immediately instead of on exit.

If you installed via Chocolatey, updating is simpler: run choco upgrade winpinator in an elevated terminal. Chocolatey checks for the latest package version and handles the update automatically.

1. Check the current version: open Winpinator, go to Help > About
2. Visit github.com/swiszczoo/winpinator/releases to see if a newer version exists
3. Download the new installer (64-bit or 32-bit matching your current install)
4. Run the installer — it overwrites the old version while preserving your settings and transfer history

Pro tip: Star the GitHub repository to get notified of new releases. Click the “Watch” dropdown and select “Releases only” to avoid noise from issues and pull requests.

Download the current version from our download section.

Honestly, no. Winpinator’s last release was v0.1.2 in February 2022, and the GitHub repository has had no code commits since April 2022. The project appears effectively inactive, with 22 open issues that remain unresolved.

That said, v0.1.2 still works with current versions of Warpinator on Linux for most users. The gRPC protocol and mDNS discovery it uses have not changed fundamentally, so basic file transfers continue to function on Windows 10 and 11. The developer (Lukasz Swiszcz) has not announced end-of-life, but the lack of activity speaks for itself.

If you need a more actively maintained option, there is a separate project called “Warpinator for Windows” by slowscript (github.com/slowscript/warpinator-windows), built in C#/.NET. It released v1.1 more recently and some users report more reliable connections. The original Warpinator on Linux, maintained by the Linux Mint team, continues to receive regular updates (versions 1.6.x and beyond).

• Last Winpinator release: v0.1.2 (February 18, 2022)
• Last GitHub commit: April 2022
• Open issues: 22, mostly unresolved
• Alternative: slowscript/warpinator-windows (C#/.NET, more recent updates)

Pro tip: Despite being unmaintained, Winpinator v0.1.2 remains lightweight and functional. If it works for your use case, there is no pressing reason to switch — just be aware that new bugs or compatibility issues will not be fixed upstream.

Compare options on our features page.

It depends on what you need. Winpinator does one thing well: transferring files between Windows and Linux over a local network with zero configuration. LocalSend is more reliable and works across more platforms. KDE Connect does far more than file transfers.

Winpinator is the simplest option for someone who just wants to move files between a Windows PC and a Linux machine (or Steam Deck). It uses the Warpinator protocol, finds devices automatically on your LAN, and supports drag-and-drop. The downside is that discovery can be finicky, there is no transfer resume, and the project is no longer actively maintained.

LocalSend has become the go-to recommendation on Reddit for cross-platform file sharing. It works on Windows, macOS, Linux, Android, and iOS. It uses its own protocol, requires zero setup, and handles large transfers without the connection drops that sometimes affect Winpinator. It is also open-source and actively maintained.

KDE Connect is a full device integration suite. Beyond file transfers, it syncs clipboard content, mirrors phone notifications on your desktop, lets you use your phone as a remote input device, and controls media playback across devices. It works on Windows, Linux, and Android. If you only need file transfers, KDE Connect is overkill.

• Winpinator: best for simple Windows-to-Linux transfers with Warpinator protocol compatibility
• LocalSend: best for reliable, multi-platform file sharing with zero setup
• KDE Connect: best if you want full device integration beyond just files
• Syncthing: best for continuous folder synchronization (not one-off transfers)
• SMB/Samba: best for ongoing network drive access, but more complex to configure

Pro tip: You can run Winpinator and LocalSend side by side. Use Winpinator when connecting with an existing Warpinator setup on Linux, and LocalSend for everything else, including transfers to phones and Macs.

See what makes Winpinator unique on our features page.

No. Winpinator transfers files exclusively over your local network (LAN). The data travels between devices through your router but never reaches the internet. Your ISP cannot see the traffic and it does not count against any data cap or bandwidth limit.

This is a common question, especially from Steam Deck users transferring large game files (sometimes 50-100 GB). All that data stays inside your home network. Think of it like copying files between two computers plugged into the same router — the router handles the traffic internally, and the WAN port is not involved.

You can even use Winpinator on a phone hotspot with mobile data turned off. Create a hotspot on your phone, connect both your Windows PC and Linux device to that hotspot, and transfers will work. The hotspot acts as a local router. As long as you keep mobile data disabled, nothing goes through your cellular plan.

Transfer speeds depend on your local network hardware, not your internet plan:

• 2.4 GHz Wi-Fi: 6-10 MB/s
• 5 GHz Wi-Fi (802.11ac): 20-35 MB/s
• Wi-Fi 6 with one device on Ethernet: 35-60 MB/s
• Both devices on Ethernet (if both are near your router): 80-100+ MB/s

Pro tip: Your internet connection speed (e.g., 100 Mbps fiber) has absolutely nothing to do with Winpinator transfer speeds. A 10 Mbps internet plan with a good AC router will give you faster local transfers than a 1 Gbps plan with a cheap 2.4 GHz router.

Learn about transfer protocols on our features page.

No, Winpinator only works on local networks. It uses mDNS for device discovery, which is limited to your local subnet by design. There is no built-in support for transfers between devices on different networks or over the internet.

This is an intentional design choice inherited from Warpinator. The idea is quick, simple file sharing between devices in the same room or building — no accounts, no cloud storage, no servers. For transfers between different locations, you need a different tool.

If you want Warpinator-like simplicity over the internet, here are your options:

• Tailscale + SMB: install Tailscale on both devices to create a virtual LAN, then share files via SMB or even Winpinator (since Tailscale makes remote devices appear “local”)
• Syncthing: encrypted, peer-to-peer folder sync that works across the internet without port forwarding
• Croc / Magic Wormhole: command-line tools for one-off encrypted file transfers using relay servers
• Cloud storage (Google Drive, Dropbox): upload from one device, download on the other — simple but speed depends on your internet connection

Some users on Reddit have reported getting Winpinator to work over a VPN by putting both devices on the same virtual subnet. This is technically possible with Tailscale, ZeroTier, or WireGuard, but it is not an officially supported configuration and may require manual port forwarding.

Pro tip: If you regularly need to transfer files between a home PC and a remote Linux server, Syncthing is probably the best option. It runs in the background, syncs folders automatically, handles connection drops gracefully, and encrypts everything end-to-end.

For local network transfers, see our download section to get Winpinator.

Winpinator uses three network ports by default: UDP 5353 for mDNS device discovery, TCP 42000 for file transfers, and TCP 42001 for device registration. All three need to be open in your firewall for the application to work.

On most home networks, Winpinator’s installer creates the necessary Windows Firewall rules automatically. If it does not, or if you are using a third-party firewall (Norton, Kaspersky, etc.), you need to add the rules manually. In Windows Defender Firewall, go to “Allow an app through firewall” and make sure Winpinator is checked for both Private and Public networks.

If you need to add rules manually or change the port numbers:

1. Open Winpinator and go to Preferences > Connections
2. You will see the port number fields — the defaults are 42000 (transfer) and 42001 (registration)
3. If those ports conflict with another application, change them — but you must set the same port numbers in Warpinator on the Linux side
4. In Windows Firewall > Advanced Settings > Inbound Rules, create new rules for TCP 42000-42001 and UDP 5353 if they do not already exist
5. On Linux, check that your firewall (ufw, firewalld) allows the same ports

Corporate and university networks often block mDNS traffic on port 5353, which prevents device discovery entirely. If you are on a managed network and cannot change firewall rules, Winpinator will not work — consider using Syncthing or SMB shares instead.

Pro tip: If discovery breaks after a Warpinator update on the Linux side, try incrementing all port numbers by +1 on both devices (42001/42002 instead of 42000/42001). This fixes a known protocol version conflict between older Winpinator and newer Warpinator versions.

See all connection requirements in our system requirements section.