Moving files between iPhone and Android, both directions

Two people, two phones, one file. Nothing about this is hard until the phones are different brands, at which point the built-in transfer that works flawlessly within each ecosystem simply does not appear.

iPhone to Android is the transfer case the built-in tools deliberately do not cover, because each platform's own sharing feature works only within its own ecosystem. It is one of the most searched file questions there is, and the answer depends less on the file than on three things: whether both devices are present, whether the file must arrive unaltered, and whether it can leave the room. Get those straight and the method chooses itself.

The four routes that work

Ranked by how often each is the right answer for iPhone to Android rather than by sophistication.

• A local Wi-Fi transfer app. Both devices join the same network and the file moves directly between them — no upload, no account, no size limit beyond storage, and the bytes are unchanged. This is the closest thing to a cross-platform equivalent of the built-in transfer, and tools like loopStream exist precisely for the iPhone to Android gap.

• A cloud link. Upload, share the link, download. Slower for anything large and it requires a connection, but it works when the other person is not present and gives you a record.

• A messaging app. One tap and universally available, with a serious caveat covered below.

• A cable or a card. Fastest for very large amounts, and the only route that needs no network at all. It requires the right adapters, which is usually the obstacle.

Ask three questions: are both devices here, must the file arrive unchanged, and can it leave the room? The method follows from the answers.

The compression problem

This is the single most consequential thing to know about moving media from iPhone to Android, and it is invisible until afterwards.

Most messaging apps re-encode photos and videos in transit. A 4K clip can arrive at 720p; a photo is recompressed and typically stripped of its metadata — the date, the location, the camera settings. For a picture of a whiteboard this is irrelevant. For anything you might need to prove something about, it is a permanent loss, and the original is not recoverable from what arrived.

The fix is one tap: send the item as a document or file attachment rather than as a photo or video. Every major messaging app offers this, and it preserves the bytes exactly.

Two related traps apply to iPhone to Android specifically:

• HEIC and HEVC. iPhones record in these formats by default, and older Android devices may not open them. Either set the iPhone camera to "Most Compatible", or convert before sending. This is the most common cause of a file that transfers successfully and then will not open.
• Live Photos and motion photos. These are a still plus a short video, and the pairing does not survive most transfers. What arrives is the still image, which is usually fine — but if the motion mattered, export it as a video first.

Which direction is harder

Both directions work; they fail differently.

iPhone to Android is mostly a format question. The transfer itself is straightforward, and the friction is HEIC photos, HEVC video, and Live Photos arriving flattened. Converting before sending removes nearly all of it.

Android to iPhone is mostly a receiving question. iOS is more restrictive about where arriving files land, and things frequently end up in the Files app rather than in Photos. If a received photo does not appear in the photo library, it is almost certainly sitting in Files under Downloads — save it to Photos from there.

Two things behave the same in both directions and catch people out equally:

• Folder structure is usually lost. Most routes hand over a flat list of files. Zip the folder first; the archive preserves both structure and names.

• Filenames may be rewritten. Some paths rename files to a timestamp or an identifier, which turns twenty transferred documents into a puzzle. Zipping fixes this too.

What about the things that are not files?

Half of a real iPhone to Android move is data that never appears as a file at all, and each category has its own route.

Contacts export cleanly as a vCard, which both platforms read. Exporting from the account rather than the phone is more reliable, since most contacts live in an account rather than on the device.

Calendars travel through the account too. If they are on a shared service, adding the account on the new phone is the whole job.

Message history is the hardest, and honestly so: the two platforms use different systems, and the manufacturers' migration tools are the only route that carries it across. Third-party tools that promise this are the category most worth being suspicious of, because they ask for extraordinary access to the most sensitive thing on the phone.

Two-factor authenticator codes deserve their own warning. These do not transfer with a normal file move, and setting up a new phone without migrating them first is how people lock themselves out of their own accounts. Move them deliberately, using the authenticator's own export, before wiping anything.

App data varies by app. Anything backed by an account restores by signing in; anything stored only on the device is lost unless the app offers its own export. Check the apps that matter to you individually, before the switch rather than after.

The authenticator point is the one to act on today if you are planning a move at all, because it is the only item on this list where a mistake locks you out of fixing the mistake.

Moving a lot at once

Migrating rather than sharing is a different problem, and three points decide whether it goes well.

1. Check free space on the receiving device first. More stalled transfers are caused by a full destination than by anything on the network, and the error message rarely says so.
2. Move in batches of a few hundred items. A single transfer of thousands is one failure away from starting over, while batches fail cheaply.
3. Verify by count, not by eye. Compare the number of items before and after. A transfer that reports success and drops files does exist, and it is discovered months later.

For a full phone migration, the manufacturers' own tools handle contacts, messages and settings that no file transfer touches. Use them for that layer, and treat photos and documents as a separate job with the routes above — the migration tools are good at accounts and poor at large media libraries.

One more thing worth doing before a big move: check that what you are copying is what you think. A photo library including several years of screenshots and duplicates is often half the size it needs to be, and pruning first is faster than transferring twice.

When both devices are not present

If the other phone is elsewhere, the local iPhone to Android routes are unavailable and the choice is between a link and a message.

Prefer a link for anything that matters: it does not re-encode, it survives a poor connection through resumable uploads, and it can be revoked. Set an expiry and turn off editing permissions unless they are needed — a shared link is a credential, and it does not care who is holding it.

Use messaging for the casual case, and remember the send-as-file tap if the quality matters.

More on the surrounding tasks in file tools, device-to-device patterns in online tools, and photo handling in image tools. Google documents its own migration tooling for the full-phone case.

The short version

For iPhone to Android in either direction with both phones present, a local Wi-Fi transfer app is the right default: nothing uploads, nothing is re-encoded, and there is no size limit.

If you use a messaging app, send as a file rather than as media. Convert HEIC and HEVC before sending to older Android devices. Zip folders to keep names and structure. And when moving a library rather than a file, check free space first, work in batches, and verify by count — because a transfer that quietly drops files reports success just like one that does not.