Send Files from Android to iPhone (Without Any Cloud)
Android and iPhone each ship an excellent way to beam files to a nearby device, and each one stops dead at the edge of its own ecosystem. Quick Share talks to Android and Windows; AirDrop talks to Apple. Put an Android phone next to an iPhone and neither can see the other. This guide lists every realistic way across that gap and is honest about what each one costs you: an account, a quality loss, a cable, or your patience.
The options, side by side
| Method | Original quality? | Account needed? | Practical limit | Catch |
|---|---|---|---|---|
| Chat app (WhatsApp, Telegram, Messenger) | Not by default — photos and videos are re-encoded | Yes | App-specific; ~2 GB as a “document” | Both people need the same app; the file crosses the provider's servers |
| Yes | Yes | Roughly 18–20 MB per message | Anything larger is silently turned into a cloud link | |
| Cloud drive link | Yes | Sender yes; receiver usually | Your storage quota | Upload, then download: two trips, and a copy stays in the cloud |
| Cable | Yes | No | None | USB-C to Lightning or USB-C needs the right cable and a computer in between on older setups |
| Direct browser link (P2P) | Yes: original bytes, checksum-verified | No | 512 MB per file on the receiving iPhone (see below) | Both devices must be online at the same time |
Why the built-in tools cannot do this
Quick Share and AirDrop are not the same protocol wearing different clothes; they are unrelated designs. AirDrop discovers peers over Apple's own Wireless Direct Link and authenticates them with Apple IDs. Quick Share (the former Nearby Share) uses Bluetooth LE for discovery and Wi-Fi for transfer, with Google account trust. Neither company has published its protocol for the other to implement, so the gap is a business decision, not a technical accident. Do not waste time looking for a settings toggle.
Step by step: a direct link between the two phones
The method that needs nothing installed on either side is a peer-to-peer link in the browser. It works because both phones already have the one client that runs everywhere, a web browser with WebRTC, and WebRTC data channels move bytes directly between two browsers.
- On the sending phone, open
app.sharedrop.org(or the ShareDrop.org app) and tap Send. Pick the photos, videos or files. The phone shows a QR code and a short code. - On the receiving phone, open the same address, tap Receive, and point the camera at the QR code — or type the short code.
- Accept on both sides. The receiver approves the incoming files; both screens show the same six-digit safety code. If the codes match, nobody is sitting between you (why that works).
- Wait for “done.” Each file is hashed with SHA-256 on both ends; the transfer only reports complete when the hashes agree, so a file marked done is byte-identical to the original (how integrity checking works).
On the same Wi-Fi the link is usually direct and runs at whatever the router allows, typically 100–400 Mbps on Wi-Fi 5/6. Across the internet, the slower phone's upload speed is the ceiling (measured numbers).
iPhone to Android: the same steps in reverse
Nothing changes except which phone taps Send. Receiving on the Android side, Chrome assembles each file in memory and saves it to Downloads, with the same 512 MB per-file cap Safari has; the ShareDrop.org Android app writes as data arrives with no cap, and puts photos and videos into the gallery. For a large video going to an Android phone, use the app on that side.
Photos in bulk: what to expect on arrival
- HEIC photos from an iPhone open natively on Android 10 and later; older Android phones show a blank thumbnail until an app that understands HEIC opens them. If the Android side is old, set the iPhone camera to Most Compatible before shooting, or convert after the transfer.
- Live Photos arrive as a still plus, if you selected it, a short video; Android has no Live Photo concept and shows two items.
- Android motion photos going the other way are a single JPEG with the video embedded inside; the iPhone shows the still and ignores the motion.
- Hundreds at once is fine on the same Wi-Fi (the transfer is router-bound and a few hundred photos take a minute or two), but note that iOS prepares selected photos before sending, which for a large selection means a noticeable pause before the first byte moves.
This is files, not a phone migration
Contacts, messages, call history and app data are not files you can pick, and no file transfer tool moves them. For switching phones outright, Apple's Move to iOS and Google's Switch to Android handle that layer, cable or over Wi-Fi. Photos and documents are where those migration tools are slowest and most lossy, and where a direct transfer or a cable does the better job, so a real switch often uses both: the migration app for the account-shaped data, a direct transfer for the media.
Does it use mobile data?
On the same Wi-Fi, no: the bytes go from one phone to the other through the router and never leave the building. Across different networks, yes on both sides: the sender uploads the file once and the receiver downloads it once, and if the connection goes through a relay the same applies; the relay does not add a second copy of the traffic at either phone. A 1 GB video costs 1 GB of data at each end, the same as any other method, and unlike a cloud link nothing is uploaded and then downloaded twice.
How long it takes
Same Wi-Fi: a few hundred megabytes in well under a minute on a Wi-Fi 5/6 network. Different networks: the sending phone's upload speed sets the pace — 5G is often 40 Mbps or better, home Wi-Fi behind a typical broadband line 20–50 Mbps, so a gigabyte takes three to seven minutes either way (what to check when it is slower).
Frequently asked
Do both phones need the app?
No. Either phone can use a browser instead, and an app can talk to a browser. The app is better for large files and for keeping the screen awake; for a few photos, Safari or Chrome is fine on both sides.
Can I send a whole folder from a phone?
Phone pickers select items, not folders; you get files, flat. To keep a folder's structure, zip it in the Files app first, or send from a desktop browser where folder picking exists (details).
Why does the sending phone ask me to approve a connection?
Because a code can be seen by someone looking over a shoulder. The prompt is the moment you confirm that the device asking to connect is the one you meant, and the safety code afterwards confirms it stayed that way.
The limits you should know before you start
- Receiving on iPhone in Safari: 512 MB per file. Safari has no streamed-to-disk saving path, so a received file is assembled in memory. Rather than let that fail unpredictably, the transfer refuses files above 512 MB up front and tells you (the full limits page). The ShareDrop.org iOS app does not have this ceiling because it writes to storage as data arrives.
- Both phones need to stay awake. A phone that locks its screen may drop the connection; transfers resume where they stopped, but a sleeping device sends nothing.
- HEIC stays HEIC. A direct link sends the bytes you picked. If the iPhone side later needs JPEG for an old Windows machine, that is a separate conversion — see the photo-specific guide.
When one of the other options is actually better
If you send the same person files every day, a shared cloud folder beats any per-file ritual: accept the account and the stored copy. If you have thousands of photos to move once, a cable to a computer is the fastest path by a wide margin. And if the recipient is offline right now, email or a link is the only thing that works asynchronously; a direct link needs both sides present. Pick the tool for the job, not the one with the nicest animation.
