I've watched people email themselves files from their laptop to their phone. Then open the email on the phone. Then save the attachment. Then delete the email thread. It's 2024.
Transferring files from PC to iPhone wirelessly should take 30 seconds. It doesn't, because Apple's ecosystem assumes you own a Mac. If you're running Windows, the official paths are either iTunes (deprecated, bloated) or iCloud (slow, limited free storage). Neither scales well for developers or anyone moving bulk data.
I'll show you three methods I actually use, with benchmarks and trade-offs. The best one depends on what you're moving and how often.
Why AirDrop Doesn't Work (And What Does)
AirDrop is Apple's drag-and-drop wireless transfer. It works between Mac and iPhone instantly. It does not work between Windows and iPhone. Full stop.
What does work: a handful of third-party tools that replicate AirDrop's simplicity. The most reliable is Snapdrop (web-based) or LocalSend (native app). Both use local network discovery and direct peer-to-peer transfer. No cloud account needed.
LocalSend is what I'd reach for first. It's open-source, runs on Windows and iOS, and transfers files over your LAN at gigabit speeds (if your network supports it). Install it on both devices, launch it, tap send, pick files, done.
Real numbers: transferring a 500 MB video file from Windows to iPhone over a 5 GHz WiFi network takes about 8–12 seconds with LocalSend. Over AirDrop (Mac to iPhone), the same file takes 5–7 seconds. Close enough.
Here's the catch: both devices must be on the same WiFi network, and both apps must be running. If you're at a coffee shop on a public network, neither method works. If your home WiFi is temperamental, you'll see stalls.
Cloud Sync: The Slow Tax
iCloud Drive is the default. Upload from Windows, download on iPhone. It works. It's also glacial and limited.
I tested uploading a 100 MB folder (mixed documents and images) to iCloud Drive on Windows:
- Initial upload: 45 seconds (iCloud Drive app, Windows 11, Gigabit connection).
- Visible on iPhone: 2 minutes 10 seconds later.
- Full sync completion: 3 minutes 40 seconds.
The delay isn't just latency. iCloud Drive queues, re-encrypts, and syncs metadata separately. For a single file, it's fine. For batch transfers, it's painful.
OneDrive (Microsoft's cloud storage) is faster on Windows—it's native to the OS—but slower on iPhone because the OneDrive iOS app refreshes less frequently than iCloud Drive does. I measured a 50 MB file taking 90 seconds from Windows upload to iPhone visibility.
Dropbox sits in the middle: about 60 seconds for the same test. All three require a free account and enough cloud storage. All three are fine for occasional use but terrible for large transfers (videos, project files, backups).
If you're already paying for cloud storage (Google One, Microsoft 365, iCloud+), use it. Otherwise, skip this section and go self-hosted.
Self-Hosted: The Fast Path
This is where it gets interesting. If you have a NAS, a spare Raspberry Pi, or a home server, you can run a file server on your local network and access it from iPhone without uploading anything to the cloud.
The simplest setup: Synology NAS with the built-in File Station app. Connect to your home WiFi, open the app, browse folders, tap a file to download. No account needed if you're on the same network. Real-world transfer speed matches your WiFi bandwidth—I see 40–60 MB/s on a 5 GHz network.
If you don't have a NAS, use a Raspberry Pi or an old laptop running Nextcloud or Samba. Nextcloud is easier for non-technical users; Samba is faster and lighter on resources.
Here's a minimal Samba config for Windows-to-iPhone file sharing:
[global]
workgroup = WORKGROUP
server string = FileShare
netbios name = FILESERVER
security = user
map to guest = Bad User
guest account = nobody
[shared]
path = /mnt/storage/shared
browseable = yes
writable = yes
guest ok = yes
read only = no
On iPhone, use the Files app (built-in) or SMB Client (free third-party app). Connect to your Samba server by IP address, browse folders, download files. No sign-up. No cloud storage tax.
Transfer speed depends on your router and WiFi. On a modern WiFi 6 setup, I see 80–120 MB/s for local transfers. A 1 GB file takes 10–15 seconds.
The trade-off: you need hardware running 24/7, or you need to turn on your PC every time you want to grab a file. For developers with always-on infrastructure, this is zero friction. For casual users, it's overkill.
The Comparison
For a deeper look at how caching layers interact with self-hosted setups, the comparison on wpcompass.io is worth a read if your server also runs WordPress workloads.
| Method | Speed | Setup | Cost | Best For |
|---|---|---|---|---|
| LocalSend | 8–12 sec (500 MB) | 2 min | Free | Ad-hoc transfers, no account |
| iCloud Drive | 3–4 min (100 MB) | Already set up | Free tier or $2.99/month | Light, infrequent use |
| OneDrive | 90 sec (50 MB) | Already set up | Free tier or $70/year | Microsoft ecosystem |
| Dropbox | 60 sec (50 MB) | Free account | Free tier or $120/year | Existing Dropbox users |
| Samba (self-hosted) | 10–15 sec (1 GB) | 30 min | $0–$100 (hardware) | Bulk transfers, privacy |
What I'd Actually Do
For a one-off file: LocalSend. Install it, transfer, forget it. No account, no cloud, no waiting.
For regular work files (documents, spreadsheets, photos from projects): Nextcloud on a Raspberry Pi. One-time setup, then it's like having your own personal iCloud—fast, private, and under your control. Costs £30 for the Pi, nothing per month.
For everything else (casual documents, notes, the odd video): iCloud Drive. It's slow, but it's already there, and you don't have to think about it.
Avoid iTunes and anything that requires a USB cable. Avoid uploading gigabytes to cloud storage you don't already pay for. And if you're moving files between PC and iPhone more than once a week, set up Samba or Nextcloud. The 30-minute investment pays for itself in a month.