What Is MTP and How Does It Enable File Transfer Between Devices?

Updated

MTP (Media Transfer Protocol) is the USB protocol that lets a computer browse and copy files stored on a portable device — most commonly an Android phone — without mounting that device's storage as a regular disk drive. It's why plugging a phone into a Mac shows a file browser instead of a Finder volume, and why macOS needs a third-party app such as OpenMTP to complete the transfer. MTP applies to phones, cameras, e-readers, watches, and VR headsets that expose files this way; it does not apply to devices that present themselves as plain USB drives.

How MTP works

MTP is a request-and-response protocol. The computer (the "initiator") asks the device (the "responder") for a list of files and folders, then issues commands to read, write, rename, or delete them. The device decides what to expose and handles the actual storage operations.

That design has two practical consequences:

  • The device stays in control. It can keep using its internal storage while you browse it, and it can hide system files or lock certain folders.
  • The computer sees a file list, not a disk. There is no drive letter or mount point, so tools that expect a mounted volume — including Finder on macOS — can't work with it directly.

MTP runs over USB and is an extension of PTP (Picture Transfer Protocol), which is why many cameras and phones report themselves as PTP or MTP devices depending on the mode you pick.

MTP vs. USB mass storage

MTP USB mass storage
What the computer sees A file list served by the device A raw disk volume
Device access during transfer Device keeps working; storage stays under its control Storage is typically unmounted from the device
File system exposure Hidden — device translates requests Exposed — computer reads the file system directly
Typical use Android phones, cameras, e-readers, watches, VR headsets USB flash drives, external SSDs, older MP3 players
macOS support Not built in; needs an app Built in

The shift to MTP on Android happened largely because mass storage requires unmounting the phone's storage from Android itself, which breaks apps that are running and can corrupt data if the phone is unplugged mid-write. MTP avoids both problems.

The typical MTP workflow

  1. Connect the device over USB. Plug the cable into both the computer and the device.
  2. Unlock the device and set the USB mode. On Android, pull down the USB notification and choose File transfer (sometimes labeled MTP). The default is often "charging only," which is the single most common reason a device doesn't appear.
  3. Open an MTP-capable app on the computer. On Windows this is File Explorer. On macOS you need a third-party client — OpenMTP is one, and its documented flow is: download the build for your Mac (Apple Silicon or Intel), drag it into Applications or install via brew install openmtp --cask, connect the phone, then drag files between the two panes.
  4. Browse and copy. The device's internal memory and SD card typically appear as separate storages you can switch between.

Expected result: you see the device's folder tree and can copy files in either direction. If nothing appears, the USB mode is the first thing to check.

Why macOS needs a third-party tool

macOS has no native MTP support. Apple's own Android File Transfer app exists but is widely described as outdated and limited — the OpenMTP site specifically calls out that it can't rename files and folders on the phone, while OpenMTP can. OpenMTP also lists support for files over 4GB, multiple files in one transfer, and both Apple Silicon and Intel Macs, with macOS 10.14 (Mojave) or higher required; macOS 10.13 and earlier need OpenMTP v3.1.15 with Legacy MTP mode.

OpenMTP 3.0 introduced "Kalam," described as a new MTP kernel, which is the component that handles the protocol conversation with the device. The project reports 1.4M+ users and 7.4K GitHub stars, and describes itself as free and open source.

Devices that use MTP

The OpenMTP supported-devices list covers phones, watches, cameras, and VR headsets that connect over MTP, including Samsung, Garmin, FujiFilm, and Meta Quest VR hardware. In general, expect MTP from:

  • Android phones and tablets (Samsung, Google Pixel, Xiaomi, Redmi, OnePlus, and others)
  • Action cameras and many mirrorless/DSLR cameras
  • E-readers such as Kindle
  • Smartwatches and fitness devices such as Garmin
  • Standalone VR headsets such as Meta Quest

Common MTP problems and what causes them

  • Device doesn't show up. Usually the USB mode is still "charging only," or the phone is locked. Unlock it and switch to File transfer.
  • Transfer stalls or drops on large files. MTP is slower and less resilient than a mounted volume; very large or numerous files are where this shows most.
  • Can't rename or delete on the device. Some clients only support copy. OpenMTP explicitly supports renaming on the phone.
  • Older Macs unsupported. Check your macOS version against the app's requirements before installing.
  • Only one storage visible. Internal memory and SD card are separate MTP storages; look for a storage switcher in the app's toolbar.