A terabyte of photos, project files, and Steam libraries takes an evening over USB 3, most of a working day over Wi-Fi, and about half an hour over a directly connected gigabit ethernet cable. No cloud upload, no NAS purchase, no external drive shuffled between two machines. The catch has always been the software: the built-in SMB tools on Windows and macOS still assume both PCs live on the same tidy network, and consumer sync apps push everything through their servers even when the two computers sit on the same desk.
We tested seven apps that do straight PC-to-PC file transfer over ethernet. The list covers open-source picks, command-line tools, and browser-based options. Every one of them keeps the bytes inside your LAN, and none of them need a paid account for the transfer itself.
What actually matters for a direct LAN transfer
- Ignores the internet. The transfer runs over the local cable or Wi-Fi, so throughput matches your ethernet card and not your ISP.
- No server round-trip. Files should not touch a vendor’s cloud, even for signalling or discovery, if you can avoid it.
- Handles the terabyte case. Resume on interruption, chunked transfer, and no arbitrary file-size cap.
- Cross-platform. At least one Windows-Linux-macOS trio member covers the mixed setups people actually own.
- Discovery without configuration. mDNS, IP-paste, or a QR code beats copying long share paths from a Windows dialog.
Quick comparison
| App | Best for | Platforms | Free plan | Notes |
|---|---|---|---|---|
| LocalSend | Overall pick, AirDrop-style UI | Windows, macOS, Linux, iOS, Android | Free, open-source | mDNS discovery, chunked HTTPS |
| Warpinator | Linux-first setups | Linux (Flatpak), Windows, Android | Free, open-source | From the Linux Mint team |
| Snapdrop | Browser-only, no install | Any device with a browser | Free, open-source | WebRTC, LAN-scoped rooms |
| PairDrop | Snapdrop with extras | Any device with a browser | Free, open-source | Adds pairing codes and IP hints |
| Croc | Command line, large files | Windows, macOS, Linux | Free, open-source | End-to-end encrypted, resumable |
| Nitroshare | Older Windows and Linux LANs | Windows, macOS, Linux | Free, open-source | Runs as a background tray app |
| Syncthing | Continuous folder mirror | Windows, macOS, Linux, BSD | Free, open-source | For ongoing sync, not one-shots |
The apps
1. LocalSend, the pick most people install first
LocalSend is the app most PC-to-PC transfer threads land on in 2026. It runs an mDNS service so the two devices see each other automatically on the same subnet, then transfers over HTTPS with a chunked protocol that handles a 1 TB folder without a memory spike. The UI is close to Apple’s AirDrop, which is why it wins the “just send my wife the wedding photos” test.
Where it falls short: No native folder-mirror mode. If both PCs are asleep, discovery has to run again once they wake. Large single-file transfers over slow Wi-Fi can sit at the last percent for a while before flushing.
Pricing:
- Free and open-source under an MIT-style license.
- No paid tier and no telemetry.
Platforms: Windows, macOS, Linux, iOS, Android.
Download: localsend.org or GitHub releases
Bottom line: Install it on every machine you own once and stop thinking about ad-hoc transfers.
2. Warpinator, made for the Linux crowd
Warpinator started as the Linux Mint team’s answer to the fact that Nautilus removed its old peer-to-peer share. It uses gRPC over the local network, discovers peers automatically, and now ships a Windows client and an Android build alongside the Linux original. On a mixed Ubuntu / Fedora / Mint LAN it is the least-friction option because most machines already have it installed.
Where it falls short: No macOS client. The Windows build is community-maintained and lags a release behind the Linux one. Very large single-file transfers can stall on unreliable Wi-Fi.
Pricing:
- Free and open-source.
- No paid tier.
Platforms: Linux (main), Windows (community client), Android.
Download: github.com/linuxmint/warpinator or via Flathub
Bottom line: The right default on a Linux-heavy LAN, especially if any of the machines already run Mint.
3. Snapdrop, no install, works from a phone
Snapdrop loads in a browser tab and puts you in a room with every other browser on the same subnet. Drag a file onto another device’s tile and it transfers over WebRTC, which the two browsers negotiate directly without touching a server for the payload. The whole thing takes about ten seconds from opening the URL.
Where it falls short: WebRTC needs a signalling handshake through the public server, so an offline LAN with no internet has to run a self-hosted Snapdrop container to work. Bandwidth is capped by the browser’s WebRTC implementation, which is fine for a few GB but slower than native TCP.
Pricing:
- Free.
- Self-host it with a Docker image if the public instance disappears.
Platforms: Any device with a modern browser.
Download: snapdrop.net or github.com/RobinLinus/snapdrop
Bottom line: The fastest way to send a file from a locked-down work laptop to your phone without installing anything.
4. PairDrop, Snapdrop with the missing features
PairDrop is a fork of Snapdrop that keeps the browser-only workflow and adds the parts people kept asking for: persistent pairing codes so devices survive DHCP lease changes, a “temporary public room” mode when the two devices are on different networks, and support for sending whole folders instead of one file at a time. The public instance is well-maintained and easy to self-host.
Where it falls short: Still WebRTC-bound for throughput. The public room mode routes signalling through a server, so keep it off if you want the transfer to stay LAN-only.
Pricing:
- Free and open-source.
- No paid tier.
Platforms: Any device with a modern browser.
Download: pairdrop.net or github.com/schlagmichdoch/PairDrop
Bottom line: The browser-only choice when Snapdrop’s basics are not enough.
5. Croc, the terminal option for big files
Croc is a single Go binary that transfers files between any two computers with end-to-end encryption and a short human-readable code as the pairing method. It resumes interrupted transfers, uses multiple TCP streams for throughput, and works over LAN or over the internet with the same command. On a direct ethernet cable a 1 TB tarball moves at close to line speed and survives a laptop lid closing halfway through.
Where it falls short: No GUI. The pairing goes through the public relay by default, which means the connection setup touches the internet even for a LAN transfer. Pass --relay to point it at a self-hosted or LAN-local relay for a truly closed transfer.
Pricing:
- Free and open-source (MIT).
- No paid tier.
Platforms: Windows, macOS, Linux, plus a BSD build.
Download: schollz.com/software/croc or brew install croc / winget install croc
Bottom line: The best pick when the file is huge, the connection is flaky, and you already live in a terminal.
6. Nitroshare, the low-drama classic
Nitroshare has been the “just works on our office LAN” option since 2015 and still gets releases. It runs as a system-tray app, discovers peers automatically, and does straight TCP transfers. On a mixed Windows and Linux LAN of older hardware it tends to outperform newer apps because it makes no assumptions about mDNS being available.
Where it falls short: The interface looks its age. The macOS build is community-maintained. No file-verification checksum after transfer, so paranoid users add one manually.
Pricing:
- Free and open-source.
- No paid tier.
Platforms: Windows, macOS, Linux.
Download: nitroshare.net or github.com/nitroshare/nitroshare-desktop
Bottom line: The quiet default on an office LAN full of Windows 10 and Ubuntu machines.
7. Syncthing, if the transfer is an ongoing thing
Syncthing is a folder-mirror tool rather than a one-shot transfer app, but it belongs on this list because the “1 TB between two PCs” job is often really “keep this folder in sync between two PCs I use every day.” Point Syncthing at a folder on each machine, exchange device IDs, and the two computers reconcile changes over the LAN whenever they see each other. It picks the fastest available path automatically, so a direct ethernet cable takes precedence over Wi-Fi.
Where it falls short: Overkill for a single transfer. The initial index of a large folder pegs one CPU core for a while. Conflict resolution keeps both copies of a file with a suffix, which surprises new users.
Pricing:
- Free and open-source.
- No paid tier.
Platforms: Windows, macOS, Linux, BSD, Android.
Download: syncthing.net or your distro’s repos
Bottom line: The right tool when the transfer is not really a transfer, it is the beginning of a long-running mirror.
How to pick the right one
- Want the fastest install-and-forget experience for both PCs → LocalSend. Modern UI, mDNS discovery, and mobile clients on the side.
- On a Linux Mint or Ubuntu LAN → Warpinator. Ships in the default repositories on a lot of distros.
- Can’t install anything on the sending machine (locked-down work laptop) → Snapdrop or PairDrop. Browser-only, no admin rights needed.
- Moving hundreds of gigabytes over a flaky link → Croc. Terminal, resumable, and does not care if the connection drops.
- On a mixed office LAN with older Windows boxes → Nitroshare. Boring on purpose, and that is why it works.
- Want the two folders to stay identical from now on → Syncthing. Overkill for one transfer, perfect for ongoing sync.
For most home users moving a terabyte once, LocalSend plus a physical ethernet cable is the whole answer. It hits about 100 MB/s on a gigabit link with no tuning.
FAQ
How do I transfer files between two PCs over ethernet without a router?
Connect the two PCs with an ethernet cable, assign both a static IPv4 address in the same subnet (for example 192.168.42.1 and 192.168.42.2), then use any of the apps above. LocalSend and Nitroshare will discover the second machine automatically once the link is up. Croc works with just the pairing code and does not care about IP layout at all.
Is a direct PC-to-PC transfer faster than SMB?
For pure throughput on the same LAN they are close, because SMB and these apps all end up moving bytes over TCP. The practical difference is setup. SMB needs shared credentials, workgroup names, and a share configured on the sending side. LocalSend or Snapdrop pair in seconds. For a one-off transfer the setup cost dwarfs the throughput difference.
Can I use these apps over Wi-Fi instead of ethernet?
Yes, all seven work over Wi-Fi as long as both devices see the same access point. Throughput drops to whatever the slower device’s radio can do, usually 30 to 50 MB/s on Wi-Fi 5 and 80 to 120 MB/s on Wi-Fi 6. For a terabyte the ethernet cable is worth it.
Is croc safe to use on public Wi-Fi?
Yes. Croc pairs the two sides with a short code, then derives an encryption key from it and transfers over an encrypted channel. Anyone sniffing the Wi-Fi sees only ciphertext. The one caveat is that the default relay lives on schollz.com, so the pairing metadata (not the file contents) transits the internet unless you point croc at your own relay with --relay.
What about AirDrop for Windows and Linux?
LocalSend is the closest thing today and does the same job on a mixed LAN. Warpinator hits the same brief with a Linux-first bent. Neither uses Apple’s protocol, so they are not interoperable with an actual Mac in AirDrop mode, but they cover the same “move a file to that laptop across the room” workflow.
