How AirDrop Works (short technical primer)

AirDrop uses Bluetooth Low Energy (BLE) for discovery and point‑to‑point Wi‑Fi (peer‑to‑peer) for the actual file transfer. That means discovery and transfer are separate layers — Bluetooth advertises the device, then the devices negotiate a direct Wi‑Fi link to move data at higher throughput. Understanding both layers helps you troubleshoot: discovery issues are usually Bluetooth problems, while slow or failing transfers often point to Wi‑Fi or firewall interference.

Apple ties AirDrop visibility to multiple settings: your device’s discoverability mode (Everyone, Contacts Only, Receiving Off), iCloud contact relationship (for Contacts Only), and system features like Handoff and Continuity. macOS Finder exposes AirDrop as a receiving endpoint, while iOS integrates AirDrop into the share sheet — both must be able to see each other.

Because AirDrop avoids your local Wi‑Fi AP and uses a direct connection, problems can look like Wi‑Fi issues even when your router is fine. The typical culprits are Bluetooth pairing interference, outdated OS/firmware, system firewall rules, or a stuck network stack on either the Mac or iPhone.

Common Causes When AirDrop Isn’t Discovering Devices

If your Mac does not appear in the iPhone’s share sheet or the iPhone doesn’t show in Finder AirDrop, the most common cause is a discovery mismatch — Bluetooth off, AirDrop set to “Receiving Off,” or Personal Hotspot enabled. Personal Hotspot binds the Wi‑Fi interface to a different role and blocks peer‑to‑peer connections, so AirDrop can’t establish the transfer link.

Other frequent issues include macOS firewall settings blocking incoming connections, the Mac being logged into a different iCloud account (affecting Contacts Only visibility), or both devices being on different versions of the OS with a bug in the AirDrop implementation. Older Macs or iPhones with failing Bluetooth modules can also intermittently fail discovery.

Environmental factors matter too: crowded 2.4 GHz radio environments, physical obstructions, or a long distance between devices can stop the BLE discovery. Bluetooth signal range is short; for reliable discovery, keep devices in the same room and within 10 meters (30 feet).

Step-by-step Fix: iPhone to Mac and Mac to iPhone

Follow these steps in order — they progress from the least invasive to the more advanced. Do each step and test AirDrop after it completes. This saves time and avoids unnecessary resets.

• Quick checklist: ensure both devices have Wi‑Fi and Bluetooth on; disable Personal Hotspot; both devices unlocked and awake; AirDrop set to Everyone or Contacts; devices within 30 ft.

1) Basic toggles: on both Mac and iPhone, turn Wi‑Fi off and on, and do the same for Bluetooth. On iPhone, open Control Center and use the AirDrop icon (or Settings > General > AirDrop). On Mac, choose Finder > Go > AirDrop and set “Allow me to be discovered by” to Everyone temporarily.

2) Restart the hardware: reboot the iPhone and restart the Mac (Apple menu > Restart). macOS can leave Bluetooth or Wi‑Fi drivers in a bad state that a reboot clears. If you prefer less disruptive, log out and back in on the Mac to restart user-space services relevant to Finder and AirDrop.

3) Check iCloud and Contacts: if using Contacts Only, both devices must be signed into iCloud and the sender must be in the recipient’s Contacts with the email or phone used for iCloud. For faster diagnosis, temporarily set AirDrop to Everyone — if that works, the issue is likely a Contacts/iCloud mismatch.

Advanced fixes and diagnostics

If the basics don’t resolve the problem, run deeper checks: verify macOS firewall, remove conflicting Bluetooth devices, reset network interfaces, and examine system logs. The firewall in System Preferences > Security & Privacy > Firewall can block incoming connections; allow signed apps or temporarily turn it off to test.

Reset the Mac’s Bluetooth module (works on Intel Macs; on Apple silicon, restart is preferred). To reset Bluetooth on Intel macs: hold Shift+Option and click the Bluetooth icon in the menu bar, then choose “Reset the Bluetooth module.” On iPhone, Settings > General > Transfer or Reset iPhone > Reset > Reset Network Settings will clear network caches (this also resets saved Wi‑Fi networks, so be ready to rejoin).

If transfers fail despite discovery, try sending smaller files, test with AirDrop between two Macs if available, and check Console.app on macOS for messages from the AirDrop or Bluetoothd services. For a developer/diagnostic approach, collect logs with the system profiler and consider an SMC/PRAM reset on older Intel Macs if hardware-related Bluetooth issues persist.

• Advanced commands (macOS Terminal — use with caution):
• sudo pkill bluetoothd — restarts Bluetooth daemon;
• sudo ifconfig awdl0 down && sudo ifconfig awdl0 up — resets Apple Wireless Direct Link (AWDL) used by AirDrop/Continuity.

Note: AWDL interface resets are effective but transient. If you find yourself doing these commands frequently, investigate OS updates or hardware repair.

For curated community-tested scripts and additional community notes about airdrop not working on mac, see this troubleshooting repository — it collects observations, commands, and potential macOS-specific fixes you can try.

Prevention and best practices

To prevent future AirDrop headaches: keep both devices updated to the latest stable OS (AirDrop improvements and bug fixes ship frequently), avoid using Personal Hotspot while transferring, and maintain clean contact entries for iCloud-based visibility. If you rely on AirDrop regularly, set “Allow me to be discovered by” to Everyone while you transfer and switch back to Contacts Only afterward for privacy.

Minimize Bluetooth clutter: unpair devices you no longer use and remove legacy Bluetooth accessories that might be triggering reconnection attempts. Periodically reboot your Mac or toggle Wi‑Fi/Bluetooth if you notice intermittent discovery problems.

If you manage multiple Macs in an environment, consider documenting approved OS builds and a short AirDrop checklist for colleagues — consistency reduces troubleshooting time. For users who need enterprise-grade file sharing, consider managed MDM alternatives if AirDrop disruptions affect workflows.

When to contact Apple or service providers

If you’ve exhausted software debugging — OS updates, resets, firewall checks, AWDL resets, and network resets — and AirDrop still fails to discover or transfer, there’s a chance the Bluetooth radio or Wi‑Fi peer‑to‑peer hardware is faulty. Apple Diagnostics and an Apple Store or authorized service provider can run hardware tests that are otherwise unavailable.

Before visiting support, collect these items: exact macOS and iOS versions, console logs showing Bluetooth/AWDL errors, and notes on when the problem started. This speeds up triage for technicians and increases the chance of a first-visit fix.

Also consider third‑party interference: enterprise firewalls, VPN clients, or kernel extensions (KEXTs) can block interfaces AirDrop depends on. If your Mac has corporate software, consult IT — they may restrict peer‑to‑peer networking for security reasons.

FAQ

Semantic core (keyword clusters)

References & Backlinks

Community collection of fixes and logs: airdrop not working on mac (GitHub).