Live Your Apple Lifecalm help for your Apple devices

Home / I want my iPhone to work better for me / Why Does AirDrop Sometimes Not Work When It Should?

Why Does AirDrop Sometimes Not Work When It Should?

Two iPhones an inch apart isn't enough. AirDrop needs three things lined up — and the receiver has to be willing.

You're probably here because you tapped share, picked AirDrop, and the other person's phone either didn't show up or the transfer hung. On Android, "nearby share" style transfers felt more automatic, or at least more obvious about why they failed. AirDrop is fast when it works and mysteriously silent when it doesn't — so it reads like a bug. Usually it's one of a handful of ordinary conditions not being met, not a broken phone.
Direct answer: AirDrop isn't "on whenever the phones are close." It needs Wi-Fi and Bluetooth turned on, both devices awake and unlocked, and — crucially — the receiving phone set to be discoverable to you. If the receiver has AirDrop limited to people in their contacts and you're not in there, or they've turned receiving off, you won't see them no matter how close you stand. The fix is a short checklist, not a repair.

What AirDrop actually needs

AirDrop uses a combination of wireless connections to find nearby devices and move the file. The baseline:

None of these is obvious from looking at the phones, which is why it feels random.

Why "two iPhones together" isn't enough

The biggest misconception is that proximity alone makes AirDrop work. It doesn't. The receiving phone decides who's allowed to send. If that phone is set to receive from contacts only, and the sender isn't in the receiver's contacts (or the contact card is missing the sender's details), the sender is invisible to the share sheet. Similarly, if the receiver turned AirDrop off, nothing the sender does will help. Android switchers often expect a neutral "everyone nearby can send" default; iPhone puts the receiver in control, which is safer but less obvious.

Things that quietly get in the way

The simple order to check

When a transfer won't start, go in this order — it resolves almost every case:

That's the whole list. If the receiver shows up and the transfer starts, everything else was fine.

AirDrop isn't only iPhone to iPhone

It's easy to think of AirDrop as a phone-to-phone trick, but the same sheet can send to a nearby iPad or Mac signed in to the same Apple Account, or to someone else's Apple device that's set to be discovered. If a Mac isn't showing up, the same rules apply: its Wi-Fi and Bluetooth are on, its screen is awake, and its AirDrop is set to receive from you. The "receiver chooses who can send" rule holds across every device type, so a missing Mac is almost never the Mac being broken — it's the discoverability setting, the same as on iPhone.

What the receiver actually sees

When everything lines up, the person receiving gets a preview and an Accept prompt — AirDrop doesn't push files onto someone without their okay. If they don't tap accept, nothing transfers, and that can look like a failure on your end when it's really them not confirming. Also worth knowing: the receiver controls whether to receive from everyone or only contacts, and they can switch back after the transfer. Leaving it open to everyone for a minute to swap a file, then returning it to contacts-only, is the calmer habit — you stay in control without leaving a door open all day.

You probably don't need to worry about

AirDrop being "broken" after one failed try. It almost never is. You also don't need to restart both phones for every attempt, and you don't need a third-party file app to move things between iPhones — AirDrop is built in. And you don't need to leave "receive from everyone" on permanently; switching it back to contacts-only after the transfer is the calmer, safer habit.

A simple way to decide

If AirDrop won't connect, blame the connection settings and the receiver's discoverability before blaming the phone. A failed AirDrop is often explained by Wi-Fi or Bluetooth being off, a locked screen, or the receiver not being discoverable. Fix those three and it usually just works.

What to do next

Ask Us a question