How to Transfer Files Between Mac and Windows
One file, two computers, forty wasted minutes. Where each transfer method stops working, and the format trap that catches almost everyone the first time.
The file is on the wrong computer. It happens about once a month: a folder of photos on the MacBook that needs to be on the Windows desktop, or a spreadsheet someone sent to the PC that you want back on the laptop before a call. AirDrop doesn't see the PC. The USB stick turns out to be read-only on one side. Forty minutes disappear into a job that should take two.
None of these routes is difficult. The trouble is that three of them stop working for reasons nobody explains in advance.
AirDrop does not cross the fence
AirDrop is the reflex, and on Apple hardware it earns that. Two Macs, or a Mac and an iPhone, find each other in the share sheet and the file is across in seconds. It's never worked with Windows and it never will. Apple built it on its own discovery and transfer stack, and no PC will appear in that window no matter how close it sits to the router.
The same is true in reverse. Nearby Sharing on the PC won't offer the Mac.
Cloud drives work, and they upload
Dropbox, OneDrive, Google Drive and iCloud Drive all solve this, which is why they became the default answer. Install the client on both machines, drop the file into a synced folder, wait, and it appears on the other side. For a document that already lives in a cloud account, this is the least work.
The cost sits in the middle of that sentence. The file goes to a server first, then comes back down. That means an internet connection at both ends, your upload speed rather than your local network speed, and a copy of the file in someone else's storage. A gigabyte of photos on a home connection with a slow upstream is a twenty-minute wait for a transfer that should have taken thirty seconds over the local Wi-Fi. If the file is one you'd rather not hand to a third party, the cloud route is the wrong shape entirely.
The USB stick, and the format trap
The oldest method still works, and it fails for a reason that catches almost everyone once: the format of the stick.
Most drives ship as exFAT or FAT32, which both systems read and write, and that's why they work straight out of the box. A drive formatted as NTFS is the Windows default on internal disks, and on a Mac it mounts in read-only mode. You can see the files and copy them off. Every attempt to write back fails or gets ignored without a message. A drive formatted as APFS or Mac OS Extended does the opposite: Windows won't mount it at all without extra software.
The fix is to reformat the stick as exFAT, which erases it, so do that before it holds the only copy of anything. After that the stick is genuinely universal. The trade-off is that you're carrying a piece of plastic between two desks, and it's easy to leave in a pocket.
A folder shared over your own network
macOS and Windows both speak SMB, the protocol behind Windows file sharing, so each can read a folder shared by the other. It's the native answer and it costs nothing.
On the Windows side: right-click a folder, open Properties, go to the Sharing tab, and share it. Note the computer name and the folder name, and make sure the Windows account has a password, because Windows refuses a blank-password share over the network by default.
On the Mac side: open Finder, press Command-K, and type the address as smb:// followed by the Windows computer's name or IP address. Enter the Windows username and password when asked, and the share mounts like any other volume.
Going the other way, from the Mac to the PC: open System Settings, go to General, then Sharing, and switch on File Sharing. Add the folder you want to expose. On the PC, open File Explorer and type the Mac's address as a double backslash followed by its name or IP address.
It works, and when it works it's invisible. The annoyance is everything around it. A share that disappears after a Windows update, a Mac that changes IP address when it rejoins the network, firewall prompts you have to accept on the right machine, credentials that need re-entering. For two machines you use every day, setting it up once is worth it. For the occasional transfer, it's more setup than the job deserves.
A transfer that never leaves your network
FileShipper is built for this job, and it's one of the free apps on the menu. Install it on both machines, open it, and each computer appears on the other as a bubble on an AirDrop-style radar. Tap the bubble, pick the files, and they move directly from one machine to the other over your local network. Nothing is uploaded, nothing passes through a server, and the transfer runs at Wi-Fi or Ethernet speed rather than your internet speed.
The part worth knowing is how it handles phones. There's no app to install on an iPhone or an Android. FileShipper shows a QR code, the phone scans it, and a plain browser page opens where you can send files to the computer or pull files back off it. That covers the third device most people own, without an App Store trip or an account.
It ships for macOS and for Windows, including both the x64 and ARM builds, so a Mac and a PC on the same Wi-Fi find each other with no configuration. Leave it open on your home network, or put a PIN on it when you're on a shared one. Received files land in a folder you choose and appear under a Received Files list with one-click access to Finder or Explorer. If the Wi-Fi name changes, the address and QR code refresh themselves, so nothing needs restarting.
When there's a person at the other end
Sometimes the file is going to a colleague two desks away rather than to your own second computer, and what you want is a chat window rather than a share.
ChatCafe runs on the same local-network idea. Everyone running it on the same Wi-Fi shows up in a sidebar, you click a name, and you can send text, images pasted straight from the clipboard, or whole folders of files. There's no upload step and no limit beyond what the other disk can hold, because the bytes go straight from your device to theirs. It covers the case where one person is on a Mac and the other on a PC, and it comes with a set of board games for the quiet moments.
Three things that break a perfectly good transfer
The mechanics are the easy part. These catch people after the file has already moved.
Filenames
Windows doesn't allow the characters \ / : * ? " < > | in a file name. macOS does. A file called Q3 report: final/final.docx copies without complaint on the Mac and gets rejected, renamed, or mangled on the way into Windows. When a batch of files refuses to copy and the reason isn't obvious, read the names first.
File formats
The office and image formats travel cleanly. A .docx written in DocCafe opens in Word, a .xlsx opens in Excel, a .pdf opens anywhere, and a folder of .md files opens in any text editor. Where people get caught is in the app-specific formats, the layered photo project or the video timeline that only its own program can open. Move the export, not the project.
Line endings
This one stays invisible until it doesn't. Text files written on Windows end their lines with two characters, and files written on a Mac end them with one. Modern editors cope with both, but older scripts and build tools sometimes don't, which is how a shell script that ran fine on the Mac throws an error the moment it lands on the PC. Most editors let you choose the line ending when you save.
Pick a route and stop thinking about it
For a one-off file to someone in the same building, a chat app is enough. For a folder moving between your own two computers on a regular basis, a shared folder or a local transfer tool saves the most time. For the phone in between, FileShipper covers it without asking you to install anything on the phone.
None of these routes needs a cloud storage subscription, and none of them leaves a copy of your file on someone else's disk. That matters more for some files than others, and it's worth noticing that the fastest route and the private one are often the same. If you run a mixed setup day to day, the two-machine workflow is worth reading next, and so is the Windows shelf that turned this from a workaround into a settled habit.
getapps.cafe includes FileShipper, ChatCafe and 125 other native apps for macOS and Windows, all included in one membership from $4.99 a month billed yearly or $9.99 monthly. There's a seven-day trial at getapps.cafe/membership, which adds a card when it starts and charges nothing until it ends.