Copying files between a Mac and an iPhone

There are five ways to move a file between a Mac and an iPhone, they behave differently, and the usual advice picks one and stops. That is why the operation often appears to succeed and then the file cannot be found. The question that actually decides the route is not speed and not cable versus wireless. It is whether the file needs to land somewhere in a filesystem that can be browsed afterwards, or whether it only needs to be handed to one specific app.

The question that picks the route

On a Mac, a file has a path. It sits in a folder, it can be found by searching, and any application can open it. On an iPhone that is only partly true. Some files live in the Files app, which does have a browsable structure. Others live inside an application's own storage, reachable only through that application, and invisible to everything else on the device.

Every route below lands on one side of that line. Getting this wrong is what produces the two most common complaints. A document sent by AirDrop arrives and then cannot be located, because the receiving app claimed it. A file copied over the cable into an app's Documents area never appears in the Files app, because it was never in the shared filesystem in the first place.

Deciding first whether the destination is a folder or an app removes most of the guesswork, and it changes which of the five is correct.

The cable route, which is Finder rather than iTunes

Since macOS Catalina, the device appears in the Finder sidebar and iTunes is no longer involved.

With macOS Catalina or later, you can use the Finder to share files between your iOS and iPadOS devices and your Mac. Source: support.apple.com

Connect the device with a USB cable, select it in the Finder sidebar, then open the Files tab. What appears there is a list of applications that support File Sharing, each expandable to show the documents it holds. Dragging a file onto an app copies it into that app. Dragging one out copies it to the Mac.

Three properties of this route are worth knowing before relying on it.

It is per application, not per device. If the Files section does not appear at all, no installed app on that device supports File Sharing. There is no general purpose folder on the iPhone reachable this way.

Shared files are included when the device is backed up, whether the backup goes to iCloud or to the computer. That is convenient and it also means they count toward backup size.

Deleting the app deletes its shared files, from the device and from the backups. Apple's own guidance is to copy those files to the computer before removing an app that holds them. This is the failure mode that costs people work, because deleting an app rarely feels like deleting documents.

AirDrop, and the conditions that make it appear

AirDrop is the fastest route for one file and it is the one most affected by settings on both sides.

Both devices need Wi-Fi and Bluetooth turned on, they need to be near each other, and Personal Hotspot has to be off on both. That last condition is the usual reason a device that should be visible is not.

On iOS 17 or later, holding two devices together starts an AirDrop transfer directly. For a person who is not in the contacts list, the receiving side opens Control Center, holds the connectivity controls, taps AirDrop, and chooses Everyone for 10 Minutes. That setting expires: since iOS 16.2 it reverts to Contacts Only after ten minutes when signed in to an Apple Account, and to Receiving Off when not.

On iOS 26.2 and later there is an additional step for people not in the contacts list. The devices are prompted to use an AirDrop code, which the receiving side generates and the sending side enters, and the person is then added to contacts temporarily for 30 days.

On the Mac, files received by AirDrop go to the Downloads folder, which makes the Mac the easy direction. Sending to the iPhone is the direction where the file disappears into whichever app handles that file type.

iCloud Drive, which is the only one that is not a copy

iCloud Drive is different in kind from the other four. Nothing is copied. The same file is visible from the Mac's Finder and from the Files app on the iPhone, and a change made on one side is the change on the other.

That makes it the right answer for a document being worked on across both devices, and the wrong answer for handing over a finished file, because deleting it later deletes it in both places. It is also the route that depends on storage, since everything placed in it consumes the iCloud allowance for the account.

The practical detail people miss is that the Desktop and Documents folders can be synced into iCloud Drive as a whole, which is set in System Settings under the Apple Account. Turning that on changes where those two folders actually live, and turning it off later moves files in ways that are worth understanding before making the change rather than after.

iPhone Mirroring, which arrived last

Recent macOS versions can display and control the iPhone in a window on the Mac, and Apple's documentation lists copying items between devices and dragging and dropping items between them as supported operations.

This is the route that most resembles working with two folders side by side, because a file dragged out of the mirrored phone lands on the Mac desktop like any other file. It requires the Mac and the iPhone to be signed in to the same Apple Account and to be near each other, and the phone stays locked while it is being used from the Mac.

Photos are a separate case

Photos and videos taken by the camera do not appear in the Files tab when the phone is connected, and that surprises people who expect the cable to expose everything. They live in the photo library, which is a database rather than a folder, and they come off the device by a different door.

Two applications on the Mac open that door. Photos can import from a connected device, filing everything into its own library. Image Capture, which ships in the Applications folder, does the plainer job: it lists what is on the device, lets a destination folder be chosen, and writes the selected items there as ordinary files. For anyone who wants photographs as files in a directory rather than as entries in a library, Image Capture is the route, and it is the one most people never open.

The format is worth checking before a large import. Recent iPhones record in HEIF and HEVC, which are efficient and are not accepted everywhere. On the phone, Settings has a Photos section with a transfer option that decides whether images are converted to a more compatible format on the way out or handed over exactly as recorded. Choosing to keep originals and then discovering that a client cannot open them is a common and entirely avoidable detour.

There is a third behavior that catches people using iCloud Photos. When the library is synced and storage is being optimized, the copy on the phone may be a smaller version, with the full resolution original held in iCloud. An import in that state can produce files that look right until they are printed. Turning off optimization, or pulling the originals from iCloud on the Mac instead, avoids it.

Which route for which job

Route	Needs a cable	Lands in	Best for
Finder File Sharing	Yes	One specific app's documents	Files an app must own, large transfers
AirDrop	No	Downloads on the Mac, an app on the phone	One file, once, quickly
iCloud Drive	No	The same place on both	A document worked on from both sides
iPhone Mirroring	No	Wherever it is dropped	Pulling something off the phone while working on the Mac
Email or a messaging app	No	An attachment	When the other two devices are not nearby

Speed only becomes the deciding factor at the top end. For a folder of video files, the cable is worth using, and the cable's own speed depends on the phone rather than the Mac, since the connector and the supported transfer rate vary by model. The cable in the box is not always the fastest one a given phone supports either, which is why an identical transfer can take very different amounts of time on two phones that look the same.

There is a sixth route that belongs in the table only as a warning. Sending a file to yourself by email or by a messaging app works, it needs no settings, and it is what most people fall back on. It also silently recompresses images, strips metadata in some clients, and imposes an attachment size limit that varies by provider. For a screenshot it is fine. For anything that will be edited afterwards, it is the route that quietly damages the file.

Why the file cannot be found afterwards

Most of the confusion after a transfer comes from three specific behaviors.

The first is app ownership. A file received on the iPhone is often opened by an app that then keeps its own copy. Saving it into Files, explicitly, at the moment it arrives, is what makes it findable later. Skipping that step is what makes the same file get sent again a week later.

The second is that the Files app shows several locations that look alike. On My iPhone holds files stored locally by apps that opted in. iCloud Drive holds the synced ones. A file saved to the wrong one of those is not missing, it is one tap away, but the two look identical in a search result.

The third is the Mac side, and it is simpler. AirDrop puts received files in Downloads, and Downloads is usually the least organized folder on the machine. A file that arrived correctly is still lost if it landed in a folder with four hundred other items.

The fix for all three is the same shape. Decide the destination folder before starting the transfer, not after. On the Mac that means a working folder rather than Downloads, and reaching that folder without a detour is a Finder settings question. On the phone it means saving into Files while the share sheet is still open.

Renaming at the same moment is worth the few seconds it costs. A file that arrives keeps whatever name the camera or the sending app gave it, which is a serial number or a string of digits. Putting the date at the front in the form 2026-09-04 makes the folder sort chronologically by name alone, with no view settings involved. Left until later, the renaming carries an extra step, which is working out what the file was. Where a working folder and the tools that act on it can sit together is covered on Features.

What to do first

Pick the route by destination rather than by habit: Finder over the cable when an app has to own the file, AirDrop for one file heading to the Mac, iCloud Drive when both sides will keep editing it. Then set the Mac's landing folder to somewhere other than Downloads. If the same files keep moving between a phone and a working directory, Atriens is built to keep both ends in the same window.