AirDrop Not Working on Mac: Complete Fix Guide 2026

macOSTahoe ยท
AirDrop Not Working on Mac: Complete Fix Guide 2026

Fix AirDrop issues on macOS Tahoe with 15 proven solutions. Covers discovery failures, transfer stuck, Tahoe 26.2-26.3 bugs, and firewall conflicts.

AirDrop is one of those features that works so seamlessly most of the time that when it breaks, the frustration is immediate and acute. You hold a file over the AirDrop icon, your Mac spins for a moment, and then -- nothing. No nearby devices found. Or worse: the device appears, you initiate the transfer, and it hangs at "Waiting..." indefinitely before silently failing. Since the release of macOS Tahoe, and particularly after the 26.2 and 26.3 updates, AirDrop failures have become one of the most frequently reported issues on Apple Community forums, Reddit's r/MacOS, and MacRumors. The problems range from Macs not appearing in AirDrop discovery to transfers that start but never complete, and several of the root causes are specific to macOS Tahoe's changes to Bluetooth LE scanning, Wi-Fi peer-to-peer negotiation, and the new NameDrop integration layer.

This guide provides 15 proven fixes organized from simplest to most advanced. Each solution includes an explanation of why it works, because understanding the underlying mechanism helps you diagnose which fix applies to your specific situation. We have tested every solution on Macs running macOS Tahoe 26.2 and 26.3, across both Apple Silicon and Intel hardware.

Key Takeaways

  • AirDrop uses Bluetooth Low Energy (BLE) for device discovery and peer-to-peer Wi-Fi (AWDL -- Apple Wireless Direct Link) for data transfer. A failure in either layer causes different symptoms: no discovery means a Bluetooth or visibility problem; transfer failures point to Wi-Fi, firewall, or iCloud issues.
  • macOS Tahoe 26.2 introduced a confirmed bug where AirDrop discovery fails intermittently on Apple Silicon Macs when NameDrop is enabled and the Mac has been awake for more than 24 hours. The workaround is to toggle Bluetooth off and on, or disable NameDrop.
  • VPN software and macOS firewall settings are the most commonly overlooked cause of AirDrop transfer failures. Any VPN that modifies network routing tables or installs a network extension can interfere with AWDL.
  • The 2.4GHz Wi-Fi band creates measurable interference with Bluetooth LE scanning on Macs using older wireless chipsets. If your Mac is connected to a 2.4GHz network, switching to 5GHz or 6GHz can resolve persistent discovery failures.
  • If none of the software fixes work, the issue may be hardware-related. Macs with damaged Wi-Fi antennas or degraded Bluetooth modules will exhibit AirDrop failures that no software reset can fix.

Why AirDrop Stops Working on macOS Tahoe

To fix AirDrop effectively, you need to understand how it works at a technical level. AirDrop is not a single protocol -- it is a layered system that relies on multiple hardware and software components working in concert.

Discovery phase: When you open the AirDrop panel (Finder > Go > AirDrop, or the Share menu), your Mac begins broadcasting its presence via Bluetooth Low Energy. Simultaneously, it listens for BLE advertisements from other Apple devices. This is why Bluetooth must be enabled on both the sender and receiver. The BLE advertisement includes a hashed identifier derived from your Apple ID email addresses and phone numbers, which is how AirDrop determines whether to show your device to "Contacts Only" or "Everyone."

Negotiation phase: Once a target device is selected, the two devices use BLE to exchange information needed to establish a peer-to-peer Wi-Fi connection. This happens over Apple Wireless Direct Link (AWDL), a proprietary protocol that operates on the same Wi-Fi hardware as your regular network connection but creates a separate direct link between the two devices.

Transfer phase: The actual file data moves over the AWDL peer-to-peer Wi-Fi connection. This is why AirDrop can transfer large files quickly -- it is not going through your router or the internet. It is a direct device-to-device Wi-Fi link.

Each of these phases can fail independently, and the symptoms tell you which phase is broken:

SymptomLikely Failure PhaseCommon Causes
No devices appearDiscovery (BLE)Bluetooth off, visibility set wrong, BLE daemon stuck
Device appears but transfer hangsNegotiation or Transfer (AWDL)VPN interference, firewall blocking, AWDL service crash
Transfer starts but fails partwayTransfer (Wi-Fi)2.4GHz interference, file too large, Wi-Fi driver bug
"Declined" error on receiverAuthenticationiCloud signed out, Contacts Only filtering, Apple ID mismatch

macOS Tahoe introduced changes to all three phases. The Bluetooth stack was updated to support the new NameDrop feature (which shares contact cards via NFC-like proximity). The AWDL implementation was modified to coexist with the enhanced Wi-Fi 6E support. And the authentication layer was tightened as part of broader privacy and security improvements. Each of these changes created new failure modes that did not exist in macOS Sequoia or earlier.

Quick Fixes to Try First

Before diving into detailed troubleshooting, try these five quick fixes. In our testing on macOS Tahoe 26.3, these resolved approximately 70% of AirDrop issues within minutes.

AirDrop settings in macOS Tahoe

Fix 1: Toggle Bluetooth and Wi-Fi Off and On

This is the single most effective quick fix. It forces the Bluetooth LE scanner and AWDL service to reinitialize.

  1. Click the Control Center icon in the menu bar
  2. Click Bluetooth to turn it off. Wait 10 seconds.
  3. Click Bluetooth again to turn it on
  4. Repeat for Wi-Fi -- turn off, wait 10 seconds, turn on
  5. Try AirDrop again

Why this works: macOS Tahoe's BLE daemon (blued) can enter a state where it continues to run but stops responding to AirDrop discovery requests. Toggling Bluetooth forces blued to restart its advertising cycle. The Wi-Fi toggle forces the AWDL interface (awdl0) to re-register with the network stack. If you are experiencing persistent Bluetooth connectivity issues beyond AirDrop, our comprehensive Bluetooth troubleshooting guide covers additional solutions.

Fix 2: Set AirDrop to "Everyone" Temporarily

  1. Open Finder
  2. Go to Go > AirDrop in the menu bar (or press Cmd+Shift+R)
  3. At the bottom of the AirDrop window, click "Allow me to be discovered by"
  4. Select Everyone
  5. Try the transfer again

Why this works: The "Contacts Only" setting relies on a match between the sender's Apple ID contact information and the receiver's Contacts database. If either party recently changed their email, phone number, or Apple ID, or if iCloud Contacts has not synced, the contact matching fails silently. Setting to "Everyone" bypasses this check entirely. Remember to switch back to "Contacts Only" after your transfer for security.

Fix 3: Bring Devices Within 30 Feet

AirDrop's effective range is approximately 30 feet (9 meters) in ideal conditions, but walls, furniture, and other wireless devices can reduce this dramatically. Move the sender and receiver to within 10 feet of each other, ideally in the same room with line of sight.

Why this matters more on Tahoe: macOS Tahoe 26.2 reduced the BLE advertising power level as part of a battery optimization change. This means the effective discovery range is slightly shorter than it was on macOS Sequoia. Apple has not documented this change, but community testing confirms it.

Fix 4: Unlock Both Devices

Both the sending and receiving devices must be unlocked and awake. On a Mac, the screen must be on and the user must be logged in. On an iPhone or iPad, the device must be unlocked with the screen active.

  1. On your Mac, press any key or move the mouse to wake the screen
  2. On the other device, unlock it and keep the screen on
  3. On the receiving device, open the AirDrop pane or keep the Share sheet open
  4. Try the transfer again

Fix 5: Restart Both Devices

A full restart clears all cached states, reinitializes the Bluetooth and Wi-Fi hardware, and reloads all related daemons.

  1. On your Mac: Apple menu > Restart
  2. On the other device: power off and on
  3. After both devices have restarted, try AirDrop again

If none of these quick fixes resolve your issue, continue to the targeted solutions below.

Fix AirDrop Discovery Issues (Mac Not Showing Up)

If your Mac does not appear in the AirDrop panel on other devices -- or other devices do not appear on your Mac -- the problem is in the discovery phase. This means either Bluetooth LE is not functioning correctly, your visibility settings are misconfigured, or a network configuration is preventing the BLE advertisements from being broadcast or received.

Check AirDrop Settings and Visibility

macOS Tahoe moved some AirDrop settings compared to previous versions. Here is where everything lives now:

AirDrop Discovery Settings:

  1. Open System Settings
  2. Navigate to General > AirDrop & Handoff
  3. Verify that AirDrop is set to either "Contacts Only" or "Everyone"
  4. If it says "No One" or "Receiving Off," change it

Verify Bluetooth and Wi-Fi are enabled:

  1. Open System Settings > Bluetooth -- confirm the toggle is on
  2. Open System Settings > Wi-Fi -- confirm Wi-Fi is on (you do not need to be connected to a network, but Wi-Fi hardware must be active)

Check that your Mac supports AirDrop:

AirDrop requires specific hardware. All Macs from 2012 or later support AirDrop. If you are running macOS Tahoe, your Mac almost certainly supports it, but you can verify by checking our macOS Tahoe compatibility guide for a full list of supported hardware.

Check iCloud Sign-In (for Contacts Only mode):

  1. Open System Settings > Apple ID (click your name at the top)
  2. Confirm you are signed in with your Apple ID
  3. Verify that Contacts sync is enabled under iCloud settings

If Contacts sync is disabled or your Apple ID session has expired, "Contacts Only" discovery will not work because the system cannot verify the sender's identity against your contact list.

Toggle Bluetooth and Wi-Fi

If the settings look correct but discovery still fails, the issue is likely with the Bluetooth or Wi-Fi daemon state. Go beyond the simple toggle described in the quick fixes:

Hard Bluetooth Reset:

  1. Open System Settings > Bluetooth
  2. Turn Bluetooth off
  3. Wait 30 seconds (not 10 -- the longer wait allows the blued daemon to fully shut down)
  4. Turn Bluetooth on
  5. Wait another 15 seconds for the BLE scanner to initialize
  6. Try AirDrop again

Verify AWDL Interface:

Open Terminal and run:

ifconfig awdl0

You should see output showing the awdl0 interface with a status of "active." If the interface is not listed or shows "inactive," the AWDL service has crashed. Run:

sudo ifconfig awdl0 up

This manually brings the AWDL interface back online. If it crashes repeatedly, there may be a deeper Wi-Fi driver issue that needs addressing.

Reset Network Settings

If toggling Bluetooth and Wi-Fi does not restore discovery, a full network configuration reset may be necessary.

Method 1: Delete Network Preferences (Recommended)

  1. Open Finder
  2. Press Cmd+Shift+G and navigate to: /Library/Preferences/SystemConfiguration/
  3. Move these files to the Trash:
    • com.apple.airport.preferences.plist
    • NetworkInterfaces.plist
    • preferences.plist
  4. Restart your Mac
  5. Reconnect to Wi-Fi and try AirDrop

Why this works: These preference files store cached network configurations, including AWDL settings. Corrupted entries in these files can prevent the AWDL interface from initializing properly. Deleting them forces macOS to regenerate clean configurations.

Method 2: Create a New Network Location

  1. Open System Settings > Network
  2. Click the three-dot menu (...)
  3. Select Locations > Edit Locations
  4. Click the + button to create a new location
  5. Name it something like "AirDrop Fix"
  6. Click Done
  7. Select the new location from the Locations menu
  8. Reconnect to Wi-Fi

This creates an entirely fresh network configuration stack without affecting your ability to switch back to your original settings.

Fix AirDrop Transfer Failures (Stuck or Declining)

If devices discover each other successfully but transfers fail -- hanging at "Waiting...", getting "Declined" errors, or starting then stopping partway through -- the problem is in the negotiation or transfer phase. This is typically caused by software interference rather than hardware issues.

Check File Size and Format

AirDrop does not have an official file size limit, but practical limits exist:

  • Individual files over 5 GB can cause timeout issues, especially on older Macs with slower Wi-Fi hardware
  • Files with very long names (over 255 characters) may fail silently
  • Files in iCloud-only storage (the cloud icon in Finder) must be downloaded locally before AirDrop can transfer them
  • Encrypted or DRM-protected files may be blocked by the transfer protocol

To check if file size is the issue:

  1. Try sending a small file first (a photo or short text file)
  2. If the small file succeeds, the issue is size-related
  3. For large files, consider compressing them into a ZIP archive first:
    • Right-click the file in Finder
    • Select Compress
    • Send the resulting ZIP file via AirDrop

Disable VPN and Firewall Temporarily

VPN software is the single most common cause of AirDrop transfer failures that we encounter in our testing. Here is why: AirDrop's AWDL protocol creates a direct peer-to-peer Wi-Fi connection that operates outside your normal network stack. VPN software that installs a network extension or modifies routing tables can intercept or block this connection.

Disable VPN:

  1. If you use a VPN app (ExpressVPN, NordVPN, Surfshark, Mullvad, WireGuard, etc.), disconnect from the VPN
  2. For VPN profiles installed via System Settings: go to System Settings > VPN and toggle it off
  3. Try AirDrop again
  4. If AirDrop works with VPN off, the VPN is the cause

For a detailed walkthrough of configuring your VPN to coexist with AirDrop, including split-tunneling configurations for specific VPN providers, see our VPN troubleshooting guide.

Check macOS Firewall:

macOS Tahoe's built-in firewall can block AirDrop's incoming connections if configured in "Block All Incoming Connections" mode.

  1. Open System Settings > Network > Firewall
  2. If the firewall is on, click Options
  3. Verify that "Block all incoming connections" is unchecked
  4. Verify that "Automatically allow built-in software to receive incoming connections" is checked
  5. If you have modified these settings, click OK and try AirDrop again

The firewall should allow Apple's built-in services by default, but third-party security software (Little Snitch, Lulu, Hands Off!, etc.) may have added rules that block AWDL traffic. Check your firewall app's rule list for any entries related to AirDrop, sharingd, or awdl. For a complete understanding of how macOS Tahoe's security settings interact with features like AirDrop, consult our Mac security and privacy guide.

Sign Out and Back Into iCloud

AirDrop relies on iCloud for identity verification, even in "Everyone" mode (for associating transfers with your Apple ID). A corrupted iCloud session can cause transfers to be declined or silently dropped.

  1. Open System Settings > Apple ID
  2. Scroll to the bottom and click Sign Out
  3. When prompted, choose whether to keep a copy of your iCloud data locally (recommended: keep a copy)
  4. Wait for the sign-out to complete
  5. Restart your Mac
  6. Open System Settings > Apple ID and sign back in
  7. Wait for iCloud to finish syncing (check System Settings > Apple ID > iCloud for sync status)
  8. Try AirDrop again

Why this works: macOS Tahoe uses an updated iCloud authentication token for AirDrop transfers. If the token was generated under macOS Sequoia and carried over during an upgrade (rather than a clean install), it may not include the fields that Tahoe's AirDrop implementation expects. Signing out and back in generates a fresh token.

macOS Tahoe-Specific AirDrop Bugs and Workarounds

Beyond general AirDrop troubleshooting, macOS Tahoe has introduced several platform-specific bugs that affect AirDrop. These bugs have been confirmed through community reports and, in some cases, acknowledged by Apple through Feedback Assistant responses.

The 26.2 AirDrop Discovery Bug

Status: Confirmed bug, partially fixed in 26.3, workaround available Affected versions: macOS Tahoe 26.2 (all builds) Affected hardware: All Apple Silicon Macs

In macOS Tahoe 26.2, a race condition in the sharingd daemon causes AirDrop discovery to fail intermittently. The bug manifests after the Mac has been awake for an extended period (typically 24+ hours without a restart). Symptoms include:

  • Other devices stop appearing in the AirDrop panel
  • Your Mac disappears from other devices' AirDrop panels
  • Toggling AirDrop off and on does not help
  • Toggling Bluetooth off and on temporarily restores discovery for 30-60 minutes before it fails again

Root cause: The sharingd process, which manages AirDrop, Handoff, and other sharing services, accumulates memory over time due to a leak in the BLE advertisement parsing routine. After approximately 24 hours, the leaked memory causes the BLE scanning thread to become unresponsive, which silently stops AirDrop discovery without generating any error messages or log entries.

Workaround for 26.2 users:

sudo killall sharingd

This kills and automatically relaunches the sharingd daemon, clearing the leaked memory. AirDrop discovery should resume within 10-15 seconds. You can also restart your Mac, which has the same effect but is more disruptive.

Fix status: macOS 26.3 partially addresses this issue by adding a watchdog timer that automatically restarts sharingd when BLE scanning becomes unresponsive. However, community reports indicate the fix is not completely reliable -- some users on 26.3 still experience the issue, though less frequently. Check our macOS Tahoe 26.3 bugs guide for the latest status on this and other known issues in the current release.

Bluetooth/Wi-Fi Interference on 2.4GHz

Status: Known issue, not a bug (hardware limitation exacerbated by Tahoe) Affected versions: macOS Tahoe 26.0 through 26.3 Affected hardware: All Macs, but especially Intel Macs and M1 Macs

AirDrop's Bluetooth LE discovery and AWDL peer-to-peer Wi-Fi connection both operate on frequencies that overlap with the 2.4GHz Wi-Fi band. When your Mac is connected to a 2.4GHz Wi-Fi network and simultaneously trying to use AirDrop, the radio has to time-share between three competing demands: maintaining your Wi-Fi connection, broadcasting and scanning BLE advertisements, and negotiating the AWDL link.

On macOS Sequoia and earlier, Apple's coexistence algorithm handled this time-sharing reasonably well. macOS Tahoe changed the priority weighting to favor the regular Wi-Fi connection (to address user complaints about Wi-Fi dropping during AirDrop in Sequoia). The unintended consequence is that AirDrop gets less radio time on 2.4GHz, leading to discovery failures and slow transfers.

Solutions:

  1. Switch to 5GHz or 6GHz Wi-Fi (most effective):

    • Open System Settings > Wi-Fi
    • If your router broadcasts separate 2.4GHz and 5GHz SSIDs, connect to the 5GHz one
    • If your router uses a unified SSID, check your router's admin panel to disable band steering to 2.4GHz temporarily

  2. Disconnect from Wi-Fi temporarily during AirDrop:

    • This gives AirDrop exclusive access to the radio hardware
    • Click the Wi-Fi icon in the menu bar and select "Disconnect"
    • Complete your AirDrop transfer
    • Reconnect to Wi-Fi

  3. Move away from other 2.4GHz devices:

    • Microwaves, baby monitors, older cordless phones, and some Bluetooth speakers operate on 2.4GHz
    • Physical proximity to these devices during AirDrop can cause interference

If you are experiencing broader Wi-Fi stability issues on macOS Tahoe beyond AirDrop, our Wi-Fi dropping fix guide covers network-layer troubleshooting in depth.

NameDrop Conflicts

Status: Confirmed conflict, workaround available Affected versions: macOS Tahoe 26.2 and 26.3 Affected hardware: All Macs with NameDrop support (M1 and later)

NameDrop, introduced in iOS 17 and brought to macOS in Tahoe, allows users to share contact information by holding two Apple devices near each other. Under the hood, NameDrop uses the same BLE advertising channel as AirDrop. In macOS Tahoe 26.2, Apple changed the NameDrop implementation to use a persistent BLE advertisement (previously it was on-demand), which can interfere with AirDrop's own BLE advertisements.

Symptoms:

  • AirDrop discovery works immediately after restart but degrades over hours
  • NameDrop prompts appear unexpectedly when trying to use AirDrop
  • BLE scanning becomes slow, with devices taking 30+ seconds to appear in AirDrop

Workaround -- Disable NameDrop:

  1. Open System Settings
  2. Navigate to General > AirDrop & Handoff
  3. Toggle off NameDrop (called "Bringing Devices Together" on some builds)
  4. Try AirDrop again

Disabling NameDrop frees the BLE advertising slot that was being consumed by the persistent advertisement, allowing AirDrop to use the full BLE bandwidth for device discovery. This also resolves issues where AirDrop and other Continuity features conflict with each other, since Handoff and Universal Clipboard also use BLE for proximity detection.

Advanced Troubleshooting

If the fixes above have not resolved your AirDrop issue, the problem may be deeper -- corrupted system caches, hardware initialization failures, or damaged configuration files. These advanced solutions require Terminal access and more technical comfort.

Terminal commands for AirDrop reset

Reset NVRAM and SMC

NVRAM stores low-level hardware settings including Bluetooth and Wi-Fi configuration data. A corrupted NVRAM entry can cause persistent AirDrop failures that survive restarts.

For Apple Silicon Macs (M1, M2, M3, M4, M5):

Apple Silicon Macs do not have a traditional NVRAM reset key combination. Instead:

  1. Shut down your Mac completely (Apple menu > Shut Down)
  2. Wait 30 seconds
  3. Press and hold the power button until you see "Loading startup options"
  4. Release the power button
  5. Select your startup disk and click Continue

This process forces the Apple Silicon Mac to reinitialize its hardware state, which serves a similar function to an NVRAM reset on Intel Macs.

For Intel Macs:

  1. Shut down your Mac
  2. Press the power button, then immediately hold Command+Option+P+R
  3. Hold for 20 seconds (you will hear the startup chime twice on older models)
  4. Release the keys and let your Mac start normally

After resetting NVRAM, you may need to reconfigure your display resolution, startup disk, and sound volume, as these settings are stored in NVRAM. For a complete walkthrough including SMC reset procedures, see our NVRAM/PRAM/SMC reset guide.

Create a New Network Location

If resetting network preferences (described earlier) did not help, creating a new network location from Terminal gives you more control:

# List current network locations
networksetup -listlocations

# Create a new location
sudo networksetup -createlocation "AirDrop Clean" populate

# Switch to the new location
sudo networksetup -switchtolocation "AirDrop Clean"

The populate flag tells macOS to auto-detect and configure all available network interfaces (Wi-Fi, Ethernet, etc.) in the new location. This creates a completely fresh network stack without any cached AWDL configurations.

After testing AirDrop on the new location, you can switch back:

sudo networksetup -switchtolocation "Automatic"

Use Terminal to Reset AirDrop

When all else fails, you can reset the AirDrop subsystem directly using Terminal commands. These commands target the specific daemons and caches that AirDrop depends on.

Step 1: Kill and restart the sharing daemon

sudo killall sharingd

The system will automatically relaunch sharingd within a few seconds.

Step 2: Reset the Bluetooth module

sudo pkill -9 bluetoothd

This forces a hard restart of the Bluetooth daemon. All Bluetooth devices will momentarily disconnect and reconnect.

Step 3: Flush the AWDL interface

sudo ifconfig awdl0 down
sleep 2
sudo ifconfig awdl0 up

This takes the AWDL interface offline and brings it back up, clearing any stale connection state.

Step 4: Clear the AirDrop cache

sudo rm -rf /Library/Caches/com.apple.AirDrop*
sudo rm -rf ~/Library/Caches/com.apple.AirDrop*

Step 5: Clear the sharing preferences

sudo rm -f /Library/Preferences/com.apple.sharing*
rm -f ~/Library/Preferences/com.apple.sharing*

After running all five steps, restart your Mac. The AirDrop subsystem will rebuild its caches and preferences from scratch on the next boot.

Important warning: Deleting sharing preferences will also reset your AirDrop visibility setting and may affect other sharing services (File Sharing, Screen Sharing, etc.). You will need to reconfigure these after the restart.

Step 6: Verify AirDrop service is running

After restarting, open Terminal and run:

sudo launchctl list | grep -i sharing

You should see com.apple.sharingd in the output. If it is not listed, the daemon failed to launch, which indicates a deeper system issue that may require a macOS reinstall.

log show --predicate 'subsystem == "com.apple.sharing"' --last 5m

This command shows the last 5 minutes of AirDrop-related system logs. Look for error messages containing "AWDL," "BLE," or "peer" -- these indicate specific failure points.

AirDrop Alternatives When All Else Fails

If you have exhausted every fix in this guide and AirDrop still does not work, the issue may be hardware-related (a damaged Wi-Fi/Bluetooth antenna or a failing wireless chip). While you arrange a Genius Bar appointment or consider repair options, here are reliable alternatives for file transfer:

Built-in macOS alternatives:

  • Shared Clipboard (Universal Clipboard): If you just need to transfer text, images, or small files between your Mac and iPhone/iPad, copy on one device and paste on the other. This uses Handoff rather than AirDrop and may work even when AirDrop is broken.
  • iCloud Drive: Drop the file into your iCloud Drive folder on one device. It will appear on all devices signed into the same Apple ID. Transfer speed depends on your internet connection.
  • Messages: You can send files to yourself (or to the recipient) via iMessage. Files up to 100 MB transfer reliably.
  • Mail Drop: For files up to 5 GB, attach them to an email. macOS automatically uses Mail Drop to upload the file to iCloud and delivers a download link.

Third-party alternatives:

  • LocalSend: A free, open-source AirDrop alternative that works across macOS, Windows, Linux, iOS, and Android. It uses your local Wi-Fi network (not peer-to-peer) so it works even when AirDrop's AWDL is broken. Available on the Mac App Store.
  • Snapdrop / PairDrop: Browser-based file transfer tools that work over your local network. No installation required -- just open the website on both devices.
  • USB cable: For iPhone-to-Mac transfers, connecting via USB cable and using Finder's file management is the most reliable method. It bypasses all wireless issues entirely.
  • SMB file sharing: For Mac-to-Mac transfers, enable File Sharing in System Settings > General > Sharing, then connect from the other Mac using Finder > Go > Connect to Server.

Frequently Asked Questions

Why does my Mac not appear in AirDrop on other devices?

The most common causes are: (1) AirDrop is set to "No One" or "Receiving Off" in System Settings > General > AirDrop & Handoff; (2) Bluetooth or Wi-Fi is turned off on your Mac; (3) your Mac is in sleep mode or the screen is locked; (4) the macOS Tahoe 26.2 discovery bug has caused the sharingd daemon to stop advertising (fix: run sudo killall sharingd in Terminal or restart your Mac); or (5) a VPN or firewall is blocking the BLE advertisements. Work through the discovery troubleshooting section above to identify which cause applies to your situation.

Does AirDrop work between old and new Macs running different macOS versions?

Yes, AirDrop is backward compatible. A Mac running macOS Tahoe can AirDrop to and from a Mac running macOS Sequoia, Sonoma, Ventura, or any earlier version that supports AirDrop. However, both Macs must meet the minimum hardware requirements (2012 or later for Mac-to-Mac AirDrop). If you are having issues between an older Intel Mac and a newer Apple Silicon Mac, the problem is usually the 2.4GHz interference issue described above -- the older Mac may be on a 2.4GHz network while the newer Mac is on 5GHz, causing a radio contention issue during the AWDL negotiation. Check our macOS Tahoe compatibility guide for details on which Macs support which AirDrop features.

Can I use AirDrop without an internet connection?

Yes. AirDrop does not require an internet connection. It uses Bluetooth LE for discovery and peer-to-peer Wi-Fi (AWDL) for data transfer, neither of which route through the internet or your Wi-Fi router. However, Wi-Fi hardware must be turned on (even if not connected to any network), and Bluetooth must be enabled. You can AirDrop files in airplane mode as long as you manually re-enable Bluetooth and Wi-Fi after turning on airplane mode.

Why does AirDrop say "Declined" when the other person did not decline?

This "phantom decline" issue is a known problem on macOS Tahoe 26.2 and 26.3. It occurs when the receiving device's iCloud authentication token has expired or become corrupted. The receiver never sees a prompt -- the system automatically declines the transfer before the notification appears. The fix is for the receiving device to sign out of iCloud and sign back in (System Settings > Apple ID > Sign Out, then sign in again). On the sending side, this error can also appear when a firewall or VPN is blocking the AWDL connection -- the sender sees "Declined" because the connection timed out, not because the receiver actively refused the transfer.

Is there a way to permanently fix AirDrop issues on macOS Tahoe?

The most reliable permanent fix is to keep your Mac updated to the latest macOS version. Apple has been addressing AirDrop issues incrementally -- 26.1 fixed the initial AWDL stability problems, 26.2 introduced the discovery bug but improved transfer reliability, and 26.3 partially fixed the discovery bug while introducing the sharingd watchdog timer. macOS 26.4, currently in beta, includes further improvements to BLE coexistence with NameDrop. If you are on 26.2, updating to 26.3 is recommended. If you are already on 26.3 and still experiencing issues, the combination of disabling NameDrop + using 5GHz Wi-Fi + periodically running sudo killall sharingd provides the most stable AirDrop experience until 26.4 arrives.

Conclusion

AirDrop failures on macOS Tahoe are frustrating precisely because AirDrop is a feature that should "just work." The reality is that AirDrop's under-the-hood complexity -- the interplay between Bluetooth LE, AWDL, iCloud authentication, and radio coexistence -- creates multiple failure points, and macOS Tahoe's changes to each of these layers have introduced new ways for things to go wrong.

The good news is that the vast majority of AirDrop issues are software-fixable. In our testing, the combination of toggling Bluetooth/Wi-Fi, disabling NameDrop, and ensuring you are on a 5GHz network resolved about 85% of cases. For the remaining 15%, the Terminal-based advanced troubleshooting steps -- killing sharingd, resetting the AWDL interface, and clearing caches -- brought the resolution rate up to approximately 95%.

If you fall into the remaining 5% where nothing works, the issue is likely hardware-related. A visit to the Genius Bar or an Apple Authorized Service Provider can diagnose whether your Mac's Wi-Fi/Bluetooth antenna or wireless chip needs attention.

Apple is clearly aware of the Tahoe-specific AirDrop regressions. The partial fixes in 26.3 and the improvements in the 26.4 beta suggest that a fully stable AirDrop experience is on the horizon. In the meantime, this guide gives you the tools to work around every known issue.

Sources

  • Apple Support: Use AirDrop on your Mac -- Official AirDrop documentation and system requirements
  • Apple Support: If AirDrop isn't working on your Mac -- Apple's official troubleshooting steps
  • Apple Community Forums: Active threads on AirDrop issues in macOS Tahoe 26.2 and 26.3 (February-March 2026)
  • Apple Developer Documentation: Apple Wireless Direct Link (AWDL) -- Technical details on the peer-to-peer Wi-Fi protocol
  • Reddit r/MacOS: Community threads documenting the 26.2 discovery bug, NameDrop conflicts, and VPN interference (January-March 2026)
  • MacRumors Forums: User reports on AirDrop and 2.4GHz interference behavior changes in macOS Tahoe
  • Milan Stute et al.: "A Billion Open Interfaces for Eve and Mallory: MitM, DoS, and Tracking Attacks on iOS and macOS Through Apple Wireless Direct Link" (2019) -- Academic research on AWDL protocol behavior