Sending a file between two phones: five ways compared

Two phones, one file, same room. This should be the easiest problem in computing and it is reliably annoying: the airdrop equivalent works only between the same brand, the messaging apps compress your video into mush, and the cloud route needs an account, an upload and a download for a file that has to travel two metres.

A file transfer is simply moving a copy of a file from one device to another, and the five methods below cover essentially every case. They differ on three things that actually matter — whether the file is altered, whether it leaves the room, and whether both people need the same platform — and choosing badly is what produces a blurry video or a photo stripped of its metadata.

Which file transfer method should you use?

Read the third column first. A file transfer that leaves the room means an upload, a download, someone else's storage and a copy that persists after you are done — which is fine for a holiday photo and wrong for a contract, a passport scan or unreleased work.

The one everyone reaches for, and its cost

Sending through a messaging app is the default because it is one tap. The cost is that most of them re-encode media on the way through.

Photos sent this way are recompressed, typically to a fraction of the original size, and the metadata — the date, the location, the camera settings — is usually stripped. For a picture of a menu that is irrelevant. For an insurance photograph or anything you may need to prove something about, it is a real loss.

Videos take the heavier hit. A 4K clip can arrive at 720p, and the second person cannot recover what was thrown away.

Most apps offer a way around this: sending the file as a document or attachment rather than as media. It takes one extra tap and preserves the original bytes. If you take one thing from this article, it is that tap — it is the difference between sending a photograph and sending a picture of a photograph.

If the file matters, do not send it as media. Send it as a file.

When the platforms do not match

The built-in file transfer on each platform — AirDrop, Quick Share — is excellent, and it stops at the brand boundary. iPhone to Android is where most people fall back to a cloud link by default.

There is a middle option that gets overlooked: a local network transfer, where both devices join the same Wi-Fi and the file moves directly between them. No account, no upload, no size ceiling beyond storage, and the file never touches an outside server. Apps built for this — such as loopStream, which pairs devices with a scan and sends across the local network — exist precisely to bridge platforms without the round trip.

Three things determine whether this route works:

• Both devices must be on the same network, and it must allow devices to see each other. Many public and guest networks deliberately isolate clients, which is why the office café is the worst place to try this.
• The sending device must stay awake. A phone that locks mid-transfer usually pauses it.
• Speed follows the network, not the devices. On a decent 5 GHz network this is faster than any cloud path, because there is no upload leg.

The second point is the most common cause of a "failed" local transfer that was working fine.

Cloud links: the case for them

The upload feels wasteful for a file crossing a table, and there are still three cases where a link is the right answer.

The other person is not present. Any asynchronous file transfer wants a link.

The file is very large and the network is poor. A resumable upload survives interruptions better than a direct connection that has to start over.

You need a record. A link can be revoked, tracked and re-shared, which matters for anything work-adjacent.

If you use a link, set an expiry and turn off "anyone with the link can edit" unless it is needed. A shared link is a credential — it does not care who is holding it — and links get forwarded far beyond the person you sent them to.

What the file does when it arrives

Two problems appear after a successful file transfer, and both look like the transfer failed.

The wrong app opens it. A file with an unfamiliar extension lands in a viewer that cannot read it, and the recipient concludes the file is corrupt. Sending a widely-readable format — PDF instead of a page layout file, MP4 instead of a camera format — avoids most of it. A Markdown reader is the same idea for text: the file was always fine, it just needed something that reads it.

The name is destroyed. Some paths rename files to a timestamp or an id, which turns a folder of ten transferred documents into a puzzle. Where the name carries meaning, zip the folder first — the archive preserves both names and structure.

Zipping first also solves a subtler problem: many transfer routes lose folder hierarchy entirely and hand over a flat list of files.

What about sending to yourself?

Moving a file between your own two devices is the same problem with one constraint removed — there is nobody to coordinate with — and it deserves its own answer because the usual advice is wrong for it.

The built-in transfer still wins within a brand, and across brands a local file transfer app is still the fastest path. But two options open up that do not apply when a second person is involved:

• A note to yourself. Most messaging apps allow a conversation with your own number, which is a serviceable clipboard across devices. It re-encodes media exactly as it does for anyone else, so treat it as a place for links and text rather than for a video you care about.
• Sync rather than send. If the same file keeps moving between the same two devices, the problem is not a file transfer at all — it is a folder that should be synced once and left alone.

The second point is worth taking seriously. Repeatedly sending yourself the newest version of a document is how people end up with four copies and no idea which one is current. One synced folder removes the question permanently, at the cost of the file living on a server.

There is also a physical route that people forget: an external drive or a card reader that plugs into a phone. For a few hundred gigabytes of footage, this is dramatically faster than any wireless method, and it needs no network, no account and no app.

Choosing, in one pass

1. Same brand, both present? Use the built-in transfer. Nothing beats it.
2. Different platforms, both present, file matters? Local Wi-Fi transfer app.
3. Different platforms, small and casual? Messaging app — but send as a file, not as media.
4. Not present, or needs a record? Cloud link, with an expiry.
5. Enormous, or no usable network? Cable, or a card if the devices take one — the only file transfer that needs no network at all.

The only step people habitually skip is the qualifier in step three. Sending as media is the default and it is the setting that silently degrades the thing you sent.

More on the underlying tools in software, device-to-device patterns in mobile apps, and comparable picks in best tools. Apple documents AirDrop's requirements if the built-in path is failing between two of its own devices.

The short version

Pick a file transfer method by three questions: do both devices share a platform, does the method re-encode the file, and does it need to leave the room.

Built-in transfer within a brand, a local Wi-Fi app across brands, a cloud link when the other person is not there — and whenever you use a messaging app, send as a file rather than as media, because that one tap is the difference between the original and a compressed copy of it.