Identify where the transfer stops
AirDrop has several stages: the recipient becomes visible, the sender chooses them, the recipient accepts when required and the receiving device opens or stores the item. “AirDrop failed” can describe a problem at any of those stages. Start by naming the stage that failed. This prevents unrelated fixes, such as changing a PDF's format when the recipient never appeared.
Use a small, harmless test file before sending a large private collection. Both people should be present and expecting the transfer. Confirm the displayed recipient rather than selecting a similar device name in a crowded room. This guide covers nearby Apple devices; it does not turn AirDrop into a universal transfer service for other platforms.
Make the receiving device discoverable
Check that both devices have Wi-Fi and Bluetooth on and are near each other. Disconnect Personal Hotspot if either device is using it. Keep the receiving device awake while testing. On iPhone or iPad, the AirDrop receiving setting is available through the connectivity controls in Control Center and in the relevant Settings area. Contacts Only requires the contact relationship to be recognized; a person standing beside you is not automatically recognized as a contact.
For a deliberate one-time transfer, the recipient can choose Everyone for 10 Minutes where supported. This is a temporary discovery choice, not permission for strangers to send anything silently. Return to the normal restricted setting after the test rather than leaving discovery broader than needed. On newer versions, an exchange with a non-contact may also require an AirDrop code; follow the prompts on the two devices instead of assuming the older tap-and-accept flow always applies.
Send one item and observe the next stage
Open a small photo or document, use Share > AirDrop and select the intended recipient. If an acceptance prompt appears, the recipient should verify the sender and accept. Transfers between your own devices using the same Apple Account can behave differently from transfers to another person. Do not infer a fault from the absence of a prompt that was not required.
Ask the recipient what happened rather than only watching the sender's progress. Did the item arrive in Photos, open in an appropriate app or appear in Downloads on the Mac? Receiving a file and knowing where it went are separate steps. If it arrived but cannot open, the wireless transfer may have succeeded and the remaining problem may be file compatibility.
| Observed failure | First useful check | What the check separates |
|---|---|---|
| Recipient never appears | Radios, proximity and receiving mode | Discovery from file-format issues |
| Waiting persists | Recipient awake and acceptance prompt visible | An unaccepted request from a stalled transfer |
| Small item works, large one fails | Available space, stability and smaller batches | Basic connectivity from scale-related trouble |
| Transfer completes but item seems absent | Receiving app or Downloads location | Delivery from filing confusion |
| File is present but will not open | File type and receiving app support | Transport from compatibility |
Work through a realistic photo handoff
Two friends want to exchange twenty trip photos, one using an iPhone and one a Mac. They first send one ordinary image. The Mac appears, the recipient accepts and opens the file in Downloads. They then send a small group and inspect it before transferring the rest. If Live Photos or original editing data matter, they agree on that requirement before selecting sharing options.
This short trial answers more than repeatedly sending all twenty images. It confirms discovery, acceptance, destination and format with little waiting. If the still image works but a motion photo loses its movement, troubleshoot the chosen sharing representation using the Live Photos guide, not the Wi-Fi settings.
Change one thing before retrying
If discovery remains unreliable, recheck the receiving mode and the sender's contact details, then restart the affected device if ordinary toggles and a fresh share attempt do not help. Avoid signing out of an Apple Account, resetting all network settings or deleting contact records as an early experiment. Those changes can disrupt unrelated services and make it harder to know what fixed the original problem.
A managed device may restrict AirDrop. Inspect the relevant workplace or school policy rather than attempting to remove its management. An older system may use different labels or lack a newer handoff convenience. The core test remains the same: can these two supported devices exchange a small known item under their current permitted settings?
Verify the contents, then close the handoff
Open at least one received item and confirm the number of files for a batch. For documents, check the intended version rather than a similarly named older copy. Keep the sender's originals until the recipient confirms that the material is usable. A completed animation is useful evidence of delivery, but it is not a substitute for opening the result.
For repeat collaboration, a shared iCloud Drive folder may be more suitable than sending new copies repeatedly. For a single transfer, AirDrop is convenient precisely because it can remain a small, visible action with a clear recipient and a checked result.
Sources & further reading
Apple’s documentation supports the feature details. The scenarios and decision sequences above are CJVV’s editorial guidance.