Android to Mac: why the cable does nothing, and what to use instead
Plug an Android phone into a Mac and, by default, nothing happens at all. No drive on the desktop, no dialog, no error. This is not a fault — macOS simply does not implement the protocol Android uses.
Why nothing appears
Android exposes storage over MTP (Media Transfer Protocol), the same protocol Windows supports natively. macOS does not implement MTP at all. The phone charges, the Mac ignores it, and there is no message explaining why — which is what makes this so confusing the first time.
Google's answer for years was Android File Transfer, a small Mac app whose only job was to speak MTP. It was never good — a bare window, a 4 GB per-file ceiling, frequent "Could not connect to device" errors — and it went years without meaningful updates before being wound down. On current macOS versions it commonly fails outright.
What works, ranked
- Nothing at all — send it over the network. A transfer service, or the phone's own share sheet into anything cloud-backed. No cable, no drivers, no protocol mismatch, and it works when the Mac is not yours. For a handful of files this is genuinely the shortest path, and it is why most people quietly stopped using cables for this.
- Google Drive or Photos. Already signed in on the phone, opens in any browser on the Mac. The obvious route for photos in particular; the constraint is your 15 GB shared allowance.
- OpenMTP. A free, open-source Mac client that speaks MTP properly. Currently the best cable-based option: it handles large files, does not choke on big folders, and is actively maintained — which is more than the official app managed.
- An SD card or USB-C drive. If the phone has a card slot or you have a USB-C stick, this sidesteps the protocol question entirely. Fastest by far for tens of gigabytes, and the only route that does not depend on a network or an app.
- Bluetooth. It works, and it is slow enough that it is only sensible for a single small file. Fine for a contact card, not for a video.
If you are going to use a cable anyway
- Check the cable first. Many USB-C cables sold with chargers are power-only and carry no data at all. If nothing appears in any app, swap the cable before debugging anything else — this is the cause more often than people expect.
- Switch the USB mode on the phone. Pull down the notification shade after connecting and change Charging this device to File transfer. Android defaults to charging, and in file-transfer terms the phone is invisible until you change it.
- Unlock the phone and keep it unlocked. Storage is not exposed while the screen is locked, and a long copy that outlives the screen timeout will fail partway.
A note on file names
Android allows characters in file names that macOS handles differently, and a folder synced between the two can produce duplicates that look identical — macOS is case-insensitive by default, so Photo.jpg and photo.jpg cannot coexist in a folder that Android was perfectly happy to keep. When a copy fails on one specific file out of hundreds, this is usually why.
More guides
Six ways to get a file from your phone to a computer — and where each one breaks
Cable, cloud drive, email, messaging apps, local network and transfer services compared: size ceilings, what each one costs you in privacy, and the specific situation where each method falls apart.
Email attachment size limits — and why your file is bigger than you think
The attachment ceiling for Gmail, Outlook, Yahoo, iCloud, Proton and Zoho, why encoding makes your file about 33% larger in transit, and the four ways past the limit.
What end-to-end encryption actually protects — and what it does not
The difference between HTTPS, encryption at rest and true end-to-end encryption, why the key matters more than the cipher, and the four things E2EE will never save you from.
Try SendMyFile
Encrypt a file in your browser and hand it over with a 9-digit code. No account, and it deletes itself.
Try SendMyFile