Can an Android phone be an external drive for your Mac?

Not on its own. Android phones stopped offering USB mass storage, the mode that makes a device look like a USB stick, around 2011. Since then a phone offers its files over MTP or adb, and macOS understands neither, so a phone you plug in appears nowhere until an app is running.

With the right app, though, a phone can appear in Finder as a volume, and for everyday work it then behaves much like an external drive: you copy to it, open files on it, and eject it. Some things still differ. Time Machine cannot back up to it, symbolic links cannot be created on it, and file permissions do not stick.

What happened to USB mass storage

Early Android phones did show up as a USB drive. Plug one in, tap a button, and its SD card appeared on the computer like a memory stick. The catch was in how that works. USB mass storage hands the computer the raw blocks of the storage, so while the computer had the card, the phone had to let go of it, and apps on the phone lost their files until you unplugged.

That was tolerable while photos and music lived on a separate card. Android 3.0, Honeycomb, changed the design in 2011: apps and media began to share one pool of internal storage, so neither ran out while the other had room to spare. The cost was that the phone could never hand its storage to a computer, because its own apps and their data were on it. As Android engineer Dan Morrill put it in November 2011, when the Galaxy Nexus arrived without mass storage, "It isn't physically possible to support UMS on devices that don't have a dedicated partition for storage."

Phones with a removable card kept mass storage for the card for a few more years. It has since gone altogether. Today the phone's USB menu, under Use USB for, offers choices such as File Transfer, PTP, USB tethering, MIDI and No data transfer. None of them is a disk.

MTP since then

In place of mass storage, Android adopted MTP, the Media Transfer Protocol. The phone keeps its storage and hands files to the computer one request at a time. Windows has MTP built in and shows the phone in File Explorer almost as if it were a disk. macOS has no MTP support at all; Image Capture speaks only PTP, the camera protocol, and imports photos and videos. That is why Mac users needed Google's Android File Transfer, which Google no longer offers. MTP explained goes into why a Mac cannot mount it on its own.

The options today

An app's own window

OpenMTP is free, open source, and needs only the phone's File Transfer mode. You browse the phone in one pane and the Mac in the other and drag between them. It is fine for moving files, but the phone never becomes a place other apps can reach: to edit a photo, you copy it out, edit it, and copy it back.

A volume in Finder

SideMount mounts the phone as a volume in Finder. It speaks adb, the protocol of Android's developer tools, over the cable itself, so the phone needs USB debugging turned on once and nothing installed. Once mounted, Finder, Terminal, rsync, Photoshop, Lightroom and VLC all see the phone like any drive. Internal storage is the volume's root, and each SD card is a folder at the top named "SD Card". Several phones can be mounted at once, each its own volume. It needs macOS 26 or later; download it to try it free for seven days.

It is not the only app that does this. MacDroid, paid beyond a free tier that copies only from the phone, mounts phones in Finder over MTP or adb. FreeDroid and mtpfs are free and very new. The best Android file transfer apps for Mac compares them.

A phone on Android 11 or later can also be paired once over Wi-Fi with Android's wireless debugging, and then it mounts whenever it is on the same network. That is far slower than the cable, so keep it for small transfers.

Take the card out

If your phone has a microSD slot, the card in a card reader is a genuine external drive, with none of the limits below. The Mac will leave ._ files beside everything you copy to it, though, and a FAT32 card cannot hold a file of 4 GB or more.

Storing Mac files on the phone

A phone with spare space makes a handy carrier for documents, photos, video and archives, and through a Finder volume they copy like they would to any drive. It is still a phone's storage, not a Mac disk, so expect these differences with SideMount:

• Permissions and ownership do not stick. Requests to change them are accepted and ignored, so ordinary copies work, but a file on the phone has whatever permissions Android gives it, not the ones it had on the Mac.
• Symbolic links cannot be created. Existing ones on the phone can be read. A folder that contains links, as app bundles and many code projects do, will not copy whole. Put it in a disk image or a tar archive first; to the phone that is one ordinary file.
• Finder tags last until you eject. They are kept on the Mac, in memory, so no ._ or .DS_Store files land on the phone, and they are gone after an eject.
• Spotlight does not index the phone. Finder can browse it, but a Spotlight search will not find files there.
• Moving between internal storage and the SD card copies on the phone. It works, but Finder shows no progress while it runs.
• Eject before you unplug. A forced unmount can leave macOS's file system service stuck until the Mac restarts.

Time Machine cannot use it

Time Machine backs up to a disk formatted as APFS or Mac OS Extended, connected directly or as a partition, to a network share that supports Time Machine, or to an AirPort Time Capsule. A disk in any other format has to be erased and reformatted first. A phone is none of those and cannot be erased into one, so it cannot be a Time Machine disk, whichever app mounts it. You can copy files to it by hand, but it is not a backup system. Backing up the other way, from the phone to the Mac, is covered in backing up an Android phone to a Mac.

Questions