Send Files from a Phone to a Computer: iPhone, Android, Windows, Mac

By ShareDrop.org Engineering · Published Jul 24, 2026 · Updated Oct 17, 2026

Getting a photo or a document from a phone onto a computer has a different best answer for each pairing. An iPhone and a Mac have AirDrop; an Android phone and a Windows PC have Quick Share. Every other combination (iPhone to Windows, Android to Mac, any phone to Linux) has no built-in wireless path at all. This guide covers all of them in one place: what each method costs, what it does to your photos, and how to fix the usual failures.

Pick by pairing

Two rules hold across the table. For tens to hundreds of files, wireless is fine and usually quickest to set up. For a full library of thousands of photos, plug in a cable: USB moves several hundred megabytes per second, sustained, and the import tools are built for the long haul.

What “send it to myself” does to a photo

The reflex is to message the photo to yourself or email it. Both work, and both can change the file:

• Chat apps re-encode. A 12-megapixel, 4 MB photo typically arrives as a 1–2 megapixel, 100–300 KB JPEG unless you explicitly choose “send as document” or an “HD” option, and even then some apps strip metadata.
• Email keeps the pixels but not the batch. Twenty photos hit the message size ceiling fast (why the limit is what it is), and some phone mail clients offer “small / medium / large” sizes that resample.
• Metadata is the silent casualty. Capture time, camera, lens, GPS position and orientation live in EXIF fields inside the file. Re-encoding often drops them, which is why photos sometimes arrive rotated or land in the wrong place in a timeline.

A file transfer, as opposed to a share, moves the bytes unchanged. Whether the pixels and metadata survive is then decided by the receiving software, not the network.

iPhone to Mac: AirDrop, and why it fails

AirDrop is the best-case tool for this pair: fast, original quality, no account ceremony. When it does not work, the failure is almost always silent. The Mac never appears in the share sheet, or the transfer sits at “Waiting” forever. The causes, in the order worth checking:

“Contacts Only” deserves one explanation. If the Mac and iPhone are signed into the same Apple ID, AirDrop treats them as the same person and shows the Mac regardless of Contacts. A Mac that is not signed into iCloud (a work machine, a fresh install) is a stranger, and Contacts Only then requires your own card in the Mac's Contacts to carry the iPhone's Apple ID email or number. Everyone for 10 Minutes bypasses the question, which is why it is the first thing to try and the last thing to leave on.

AirDrop is a proximity feature and will stay one: its speed comes from the direct radio link that proximity makes possible. For a file on both devices wherever they are, iCloud Drive syncs through Apple's servers; for a one-off send to a Mac somewhere else, use the browser link below.

Android to Windows: Quick Share and Phone Link

Google's Quick Share for Windows is a free download that gives a Windows 10 or 11 PC the same send target an Android phone sees: share a file on the phone, pick the PC, accept on the PC. It finds the PC over Bluetooth and moves the data over Wi-Fi, at original quality, so the PC needs both radios and works fastest on the same network as the phone. Set its visibility to receive from everyone nearby while you send, exactly as on the phone.

Microsoft's Phone Link takes a different approach: it pairs the phone with the PC once and then shows the phone's recent photos and screenshots in a window, from which you drag them to the desktop. It is convenient for a screenshot or two and not built for batches or original video.

iPhone to Windows, Android to Mac: no built-in path

These two pairs cross an ecosystem boundary, so neither vendor ships a wireless tool. For iPhone to Windows, Apple offers iCloud for Windows, which syncs the photo library to the PC continuously at the price of an Apple ID on the PC and a copy in iCloud; with a cable, Windows Photos imports directly. For Android to Mac over a cable, set the phone's USB mode to “Transfer photos (PTP)” and Image Capture imports the camera roll; browsing any other files on the phone needs a third-party transfer app, because macOS does not speak the phone's file-transfer protocol. LocalSend, which is free and open source, works for both pairs once installed on the phone and the computer, as long as they share a Wi-Fi network. Without installing anything, the browser link is the answer.

Any phone to Linux

Linux desktops are outside both walled gardens. Three methods work well. KDE Connect (or GSConnect on GNOME) pairs an Android phone with the desktop once, then puts “send to laptop” in the Android share sheet, alongside clipboard sharing and notification mirroring; its iOS app is narrower. LocalSend works from either phone platform on the same network. The browser link needs nothing installed on either side and works from anywhere; receive in Chromium rather than Firefox for large files. Both apps need their ports open if the Linux firewall is on (the exact lines).

The direct browser link: any phone, any computer

A browser on each device is all this needs, because WebRTC data channels move bytes directly between two browsers, encrypted end to end.

1. On the computer: open sharedrop.org and click Create transfer. A QR code, a link and a six-character code appear.
2. On the phone: point the camera at the QR code and tap the banner, or open sharedrop.org in the browser and type the code into Join.
3. On the computer: a “device requesting to connect” prompt appears. Accept it; nothing connects without this step.
4. For sensitive files: both screens show a six-digit safety code. Check they match (why this matters).
5. On the phone: choose the files. iOS offers Photos or the Files app; Android offers the gallery or Files. The computer reviews the list (names, sizes) and accepts, and each file is verified with SHA-256 before it is marked done.

With the ShareDrop.org app on the phone, the roles flip: tap Send, pick the files, and type the code the phone shows into the computer's Join box. The app is worth it for anything large or repeated. It keeps the screen awake so the system does not suspend the transfer, shows a preparation step while iOS exports the selected photos (a Safari tab can only wait), and resumes from the last verified chunk if it is interrupted. In a browser, keep the tab in the foreground: iOS in particular suspends background tabs, and a suspended tab sends nothing.

A QR code on a monitor scans best from about 30 cm at normal brightness; a matte anti-glare screen can take a second longer. If the camera will not lock on, typing the six-character code is exactly as good: the QR only saves typing it.

Where the files land on the computer

In Chrome or Edge, on Windows, macOS or Linux, the first incoming file asks once for a destination folder; every file is then written there as it arrives. Firefox and Safari hand each file to the download manager instead, assembling it in memory first: fine for photos and documents, and the reason a single file over 512 MB is refused there (why). Receive long 4K videos in Chrome or Edge. On Windows, Defender scans each file as it closes, which can add a second or two per large video; on a Mac, photos and documents get no Gatekeeper prompt, because only applications do.

Opening what arrives: HEIC, HEVC, Live Photos

If a Windows PC will see many iPhone photos, the cleaner fix is on the phone: Settings → Camera → Formats → Most Compatible makes new photos JPEG and new videos H.264. It does not convert what is already in the library; convert those on the computer after the transfer, so the originals stay untouched. An iPhone HDR video (Dolby Vision) can look washed out on a display without HDR support: the file is intact, the screen is not showing what it contains.

RAW files are where the method matters most. A ProRAW or DNG file from a recent phone is 25–75 MB, and a 48-megapixel HEIC is several times a normal photo. Chat apps mangle these worst and email refuses them soonest; a direct transfer, AirDrop, Quick Share or a cable deliver them untouched.

How long it takes

AirDrop between an iPhone and a Mac in the same room typically moves 30–50 MB/s over its direct Wi-Fi link. A browser transfer on the same Wi-Fi runs at the router's speed, around 25 MB/s on Wi-Fi 5 or 6: a hundred 4 MB photos in seconds, a gigabyte of video in under a minute. Across the internet, the phone's upload speed is the ceiling: on home broadband typically 20–50 Mbps, so the same gigabyte takes three to seven minutes, and 5G is often faster than the home line. If the badge on the computer reads Encrypted relay, the two networks could not connect directly and the transfer is being forwarded, with the same encryption and slightly more latency (diagnosing slow transfers).

The whole library: a cable or a sync service

Google Photos and iCloud Photos are not transfer tools, but they solve the same problem for people who want every photo on every device continuously. The trade-offs are an account on the computer, a copy in the cloud for as long as you keep the service, and the quality setting: “storage saver” modes recompress, and only “original quality” keeps what the camera captured. For a library you want mirrored, sync is the right tool; for a one-off move of a few hundred photos, it is slower and leaves more behind.

Computer to phone, the other way

Once connected, the same session works in both directions: choose files on the computer and the phone receives. In Safari on an iPhone, each file is assembled in memory and saved to the Files app, with a 512 MB cap per file, and photos do not go into the Photos library on their own. Chrome on Android saves to Downloads with the same cap. The ShareDrop.org apps on both platforms write as data arrives, with no cap, and put photos and videos straight into the photo library, so use the app on the phone for anything larger than a few hundred megabytes (limits by platform).

After they arrive

• Sort by “date taken,” not “date modified.” The modified date is the moment the file was written on the computer, the same for every file; the capture date survived in EXIF because the bytes were not re-encoded. Windows Photos and macOS Photos read it on import and group by day.
• Photos that arrive rotated are fine. Phones store the image as the sensor captured it and note the orientation in EXIF; a viewer that ignores the field shows it sideways.
• Albums do not travel. They are database entries in the phone's library, not folders on disk, so no transfer method carries them over as-is.
• Screenshots have no camera or location data. They are PNGs with almost no metadata; only camera photos carry EXIF.

Sending photos to someone else's computer

The steps are identical; what changes is metadata. An original photo carries the location it was taken, to a few metres, and the time to the second. Sending originals to a friend is fine; sending them to a marketplace buyer or a stranger is a reason to strip location first. On iOS the share sheet's Options turn off Location for that share; on Android, Google Photos offers to remove location when sharing. A direct transfer sends exactly what you picked, so do the stripping before you pick.

Frequently asked

Do I need iTunes or the Apple Devices app on a Windows PC?

Only for cable sync and backups. A browser transfer needs nothing installed on the PC and nothing signed in.

The photo picker only shows a few photos

iOS lets you grant an app “limited” photo access, in which case the picker shows only the photos you allowed before. In Safari the system picker always shows the whole library, because Safari itself has no library access: it hands you the picker and receives only what you choose. In the ShareDrop.org app, Settings → Apps → ShareDrop.org → Photos → Full Access restores the full library.

Does it work over cellular?

Yes. The phone can be on 5G and the computer on any connection; the transfer goes direct when the networks allow and through the relay when they do not. It uses mobile data equal to the file size once, with no upload-then-download double charge.

Is a cable ever the better choice for a few files?

Rarely. For a handful of files the setup time decides, and wireless wins. The cable wins on volume: tens of gigabytes, or a library you want imported with Live Photos and edits intact.

If it does not connect

Corporate networks and some hotel Wi-Fi block direct connections; the transfer then runs over an encrypted relay automatically, which takes a few extra seconds to establish. If it still fails, put the phone on cellular for a moment to rule out the Wi-Fi, then work through the troubleshooting page. For two computers rather than a phone and a computer, see sending files between two computers; for two phones on different platforms, Android and iPhone.