AirDrop not working from an iPhone to a Mac: the settings to check

The direction matters. A Mac that sends to an iPhone without trouble and refuses to receive from it is not a broken Mac. It is a Mac whose receive side is configured differently from its send side, and macOS keeps those two things in separate places. That asymmetry is the single most common shape this problem takes, and it is the reason so many troubleshooting lists fail: they treat AirDrop as one feature with one switch.

What follows is the set of settings that genuinely cause this, ordered by how little they cost to check. Every item here is either visible on screen already or one click away. The expensive steps, restarting and resetting, come last for a reason.

Sending and receiving are two different settings

On a Mac, whether AirDrop is on is one thing. Who may send to you is another. Both live in Control Center: click the Control Center icon in the menu bar, click AirDrop to turn it on, and when it is blue it is on. To change who may send, click and hold AirDrop, or click the arrow next to it, then choose Contacts Only or Everyone.

The same receive setting appears in System Settings under General, then AirDrop & Continuity. Reading it there is often clearer, because the pane states the current value as text instead of as a highlighted state you have to interpret.

Here is the failure that follows from this. A Mac set to Contacts Only will happily send to any phone it can see, and will accept from nothing except devices whose owner is in its contacts. From the phone's side the Mac simply does not appear in the list, which looks identical to the Mac being asleep, out of range or broken. Apple's own troubleshooting note for this is short: check that the recipient has AirDrop set to receive from Everyone or Contacts Only. If it is set to receiving nothing, there is nothing further to diagnose.

So the first move is not to toggle anything. It is to read the receive setting on the Mac, and to keep in mind that the fact that sending works tells you nothing at all about it.

Contacts Only has a second condition that is easy to miss

Setting the Mac to Contacts Only and confirming that the phone's owner is in your contacts is not sufficient. The contact card has to carry the right identifier.

Apple states the requirement from the sender's point of view: if you are sending to someone who only accepts items from a contact, you must be in their contacts list, and they need to have your Apple Account email address or phone number included in your contact card. Read in the receiving direction, that means a Mac set to Contacts Only will reject a phone whose owner is in Contacts under a work email address while the phone is signed in to an Apple Account using a personal one.

This produces a failure that looks completely arbitrary. Two colleagues with adjacent desks, both in each other's contacts, and AirDrop works one way and not the other. The fix is to open the contact card for that person and confirm that the address or number tied to their Apple Account is on it. The alternative, which costs nothing and takes two clicks, is to switch the Mac to Everyone for the length of the transfer and switch it back afterwards.

Unlike iOS, the Mac's Everyone setting does not expire on its own. On an iPhone the equivalent option is Everyone for 10 Minutes, and since iOS 16.2 it reverts by itself: to Contacts Only if the phone is signed in to an Apple Account, and to Receiving Off if it is not. A Mac left on Everyone stays on Everyone until someone changes it, which is worth knowing both as a convenience and as a reason to change it back.

What macOS 26.2 changed, and why old instructions now mislead

Advice written before macOS 26.2 describes a flow that no longer exists, and following it produces a failure that looks like a bug.

With iOS 26.2, iPadOS 26.2, macOS 26.2 or later, a person who is not in your contacts cannot simply appear in your AirDrop list and push a file. They have to use an AirDrop code. On the receiving device you choose to receive, select Continue, and a code appears. You give that code to the sender, the sender enters it, and the transfer proceeds. After that first exchange, the two of you can share in both directions for 30 days without another code. To end that early, open the Contacts app, find the person in your Other Known list, and select Forget This Person.

The practical effect is that a transfer from a stranger's iPhone to your Mac now requires a step that neither person may be expecting. If the sender sees a prompt asking for a code and does not know where the code comes from, the transfer stalls and both sides call it broken. It is not broken. Someone has to read the code off the receiving device.

Situation What the Mac needs What the sender needs
Your own iPhone, same Apple Account AirDrop on Nothing. The item is accepted and saved automatically
A contact's iPhone AirDrop on, Contacts Only or Everyone To be in Contacts with the address or number tied to their Apple Account
Someone not in your contacts, macOS 26.2 or later AirDrop on, set to Everyone The AirDrop code shown on the Mac

The three preconditions that have nothing to do with AirDrop

Underneath every case above sit three requirements, and each of them can fail silently.

Wi-Fi and Bluetooth on both devices. Not connected to a network, simply turned on. A Mac with Wi-Fi off is invisible to AirDrop even on a wired connection, and a Mac with Bluetooth off is invisible even with Wi-Fi working perfectly.

Personal Hotspot disconnected. Apple's instructions say that if either device has Personal Hotspot on, you should disconnect. This is the check that catches people travelling, because a Mac using an iPhone's hotspot for internet is in exactly the state that breaks the transfer between those same two devices.

Range. Within 30 feet, or 10 meters. There is no indicator for this and no error message that mentions it. Walking closer is the cheapest test in this entire article.

If all three read correctly and the transfer still fails, restarting the device is Apple's own next suggestion and it resolves a meaningful share of cases. One setting further out is worth a look on a Mac that never appears as a target for anything at all: in System Settings under Network, then Firewall, then Options, the option named Block all incoming connections prevents incoming connections to nonessential services and apps, and Apple describes it as blocking connections to all sharing services other than basic internet services.

The transfer that arrived and was never accepted

One case is not a settings problem at all, and it is worth separating out because the symptom is indistinguishable from a failure. The phone shows the transfer as sent. The Mac shows nothing. No file appears.

This happens when the Mac has AirDrop open in a Finder window. In that situation the notification asking you to accept or decline appears in that Finder window rather than in Notification Center. Open the AirDrop window, switch to another app, and the prompt is sitting there behind everything else, unanswered. Nothing is saved, because nothing was accepted, and no banner will ever appear to tell you so.

The reverse version of the same confusion is the one that makes people doubt their own devices. When the phone and the Mac are signed in to the same Apple Account, the item is accepted and saved automatically with no prompt at all. Silence is the correct behaviour there. So on one Mac silence means the file is already in Downloads, and on another it means a prompt is waiting out of sight. Same symptom, opposite meaning, and the only way to tell them apart is to know whether the two devices share an account.

Before changing any setting, it costs nothing to bring the Finder AirDrop window forward and look, and to check the Downloads folder sorted by Date Added. Between them, those two checks account for a large share of reports that turn out not to be failures.

Why the phone shows no error, and what to watch instead

Part of what makes this frustrating is that the phone reports nothing useful. A Mac that is present but not accepting looks the same as a Mac that is not there. There is no message explaining which condition failed, because the phone was never told.

That pushes the diagnosis onto the Mac, and specifically onto the right end of the menu bar, where three of the four things worth checking are already displayed. Wi-Fi state is there. Bluetooth state is there if that control has been placed there. Whether the Mac is connected to an iPhone's hotspot shows up there as well. AirDrop mode is one click into Control Center.

The problem is that the menu bar has a fixed amount of room, and every background app wants some of it. Sync clients, VPNs, audio tools, clipboard managers and update agents all place an icon there. When the bar runs out of space, items stop being drawn, and which ones vanish is decided by position rather than by whether you need them. A Mac where Bluetooth is no longer visible is a Mac where the fastest check in this article is unavailable.

macOS offers blunt tools for this. Status menus can be rearranged by holding Command while dragging one, and removed by holding Command while dragging it clear off the bar. Items added from System Settings are managed in the Menu Bar pane, and items from Control Center through Edit Controls. Control-clicking a control inside Control Center also offers Copy to Menu Bar, which is how Bluetooth gets a permanent place near the clock. What none of that does is let you keep twenty icons installed while displaying four.

That gap is what a menu bar manager fills. The icons you never read sit behind a divider and come back on a gesture, and the indicators you diagnose with keep their place. The comparison across the options is mostly about what happens after an icon is hidden, which is the part that decides whether it was worth hiding.

What to change first

Read the Mac's receive setting before touching anything else, because a Mac that sends fine tells you nothing about whether it accepts. Then make sure Wi-Fi and Bluetooth are still visible in the menu bar, and if they are not, hide what you never click so they fit. Koffret does that and keeps the hidden icons clickable without expanding the bar, free for fourteen days with no card.

Frequently asked questions

Why can I AirDrop from my Mac to my iPhone but not the other way round?

Because sending and receiving are governed by different settings. A Mac set to Contacts Only, or to receiving nothing, can still send to any device it can see. Open Control Center, click and hold AirDrop, and check whether the receive setting is Contacts Only or Everyone.

My Mac does not appear in the AirDrop list on my iPhone at all.

Start with the receive setting on the Mac, then confirm Wi-Fi and Bluetooth are on there, then disconnect Personal Hotspot if either device has it on, then move the devices within 30 feet or 10 meters. A Mac that is present but not accepting looks exactly the same from the phone as a Mac that is absent, which is why the order matters.

We are both in each other's contacts and it still fails.

Check which address or number is on the contact card. Contacts Only requires the card to include the Apple Account email address or phone number the other device is signed in with, so a card holding only a work address will fail against a phone signed in with a personal one. Switching to Everyone for the transfer confirms this in seconds.

What is the AirDrop code my Mac is asking for?

It is a confirmation step introduced with macOS 26.2 and iOS 26.2 for transfers between people who are not in each other's contacts. The receiving device displays the code, the sender types it in, and the transfer proceeds. Once used, sharing with that person works without a code for 30 days.

Does Personal Hotspot really break AirDrop?

Apple's instructions say to disconnect if either device has Personal Hotspot on, and it is worth taking literally. The case that catches people is a Mac using an iPhone's hotspot for internet and then trying to receive a file from that same iPhone, which is a normal thing to do while travelling and reliably does not work.

Is resetting network settings on the iPhone a good idea?

It is a late step, not an early one. It clears saved Wi-Fi networks and their passwords, so the cost is real and the evidence you would have used to work out the actual cause is gone. Read the Mac's receive setting, the two radios, the hotspot state and the distance first, then restart, then consider anything destructive.

Back to all posts