Relayium

How to transfer files from Android to iPhone (no cable)

Last updated: 2026-08-07

Android and iPhone do not share an AirDrop, so moving a few photos or a video between them usually means a USB cable, a chat app that compresses your images, or a round-trip through some cloud drive. All three are slower and more fiddly than they should be.

Relayium skips all of that. Both phones open the same page: on the same LAN the end-to-end encrypted files travel directly, while across networks a TURN relay carries ciphertext it cannot read or decrypt and keeps no realtime content copy or history. No app is needed; the creator signs in for cross-network pairing, while the person joining never needs an account. This guide walks through it step by step.

What you need before you start

What you need

  • An Android phone with Chrome (or any modern browser) and an iPhone with Safari — both up to date.
  • For the fastest path, both devices on the same Wi-Fi network. On the iPhone that usually also means turning iCloud Private Relay off for that one network: it sends the phone out through a different public IP, and same-network discovery groups devices by exactly that address. Leaving it on is a perfectly good choice — a pairing code on https://relayium.com/cross-network then reaches the phone without changing the setting.
  • The page open over https://relayium.com/ on both phones. Encrypted transfer needs HTTPS, and over plain http:// the page says so instead of listing devices.
  • The files you want to send, up to 1,000 per batch, and somewhere for them to land on the receiving phone — which folder that is belongs to its browser, not to Relayium.

Nothing to install. On the same network there is nothing to sign up for either — realtime transfers work straight from the browser on both devices.

Step by step: both devices on the same Wi-Fi

This is the simplest route. On the same network, the two phones discover each other automatically, so there is almost nothing to type.

  1. On both the Android phone and the iPhone, open the transfer page in the browser.

    https://relayium.com/
  2. Compare the public IP in the status pill on both phones. Matching addresses put the two in one room; a different one on the iPhone commonly means iCloud Private Relay or mobile data rather than a broken Wi-Fi.

    Connected · this device iPhone · public IP 203.0.113.9
  3. Each phone now lists the other under “Nearby devices”. On the sending phone, tap the receiving one and press “Open workspace”. On a current browser that is the card's one action, because files and messages then share the single encrypted connection it opens.

  4. The workspace replaces that card, and its controls carry both: “Send files” for a batch of up to 1,000, or type into the message box and press “Send”. “Send a folder” is offered on the Android phone but not on the iPhone, because no iOS browser lets a page pick a folder. Then, on the receiving iPhone, read the line under the request before you accept — it says whether Safari will ask where to save or write to its own Downloads — and tap “Accept”.

  5. Keep both browser tabs in front until the file counter reaches the last file. To compare a verification code (SAS) first, turn on “Advanced verification” on both phones before you start: a match confirms both phones joined the same end-to-end encrypted session, and it does not prove which network path carries the ciphertext. Left off, there is no code to compare and the session is still encrypted.

What a working transfer looks like

The other phone's card is gone by then — the workspace took its place — so the state is read off the workspace header: the device you are connected to, a link state of “Connected”, and one path badge reading “LAN direct”. The file counter on both screens ends on the last file of the batch.

Then confirm the file rather than the page. On the iPhone that means the Downloads folder in the Files app, which is where Safari puts a download; on the Android phone it means the browser's own downloads list — chrome://downloads in Chrome, about:downloads in Firefox.

Connected to iPhone · Connected · LAN direct
File 2/2

When the two phones can't see each other

One cause worth knowing on the iPhone: iCloud Private Relay is on for many iCloud+ accounts and changes the public IP the phone appears to come from, which is exactly what same-network discovery groups by. It is one common reason among several, not the only one, and the checks below are the usual first ones rather than an exhaustive list — each decides its case from what is already on screen.

Symptom, check, fix

The iPhone never appears on the Android phone, or the other way round.
https://relayium.com/   # compare the public IP in the status pill on both phones

Two different public IP addresses mean two rooms. On an iPhone iCloud Private Relay is one common cause, and a phone that quietly stayed on mobile data is another; neither is the only possibility. If you are willing to change them, turn Private Relay off for that one Wi-Fi under Settings › Wi-Fi › the network › Limit IP Address Tracking, or join the Wi-Fi, then reload https://relayium.com/. If you would rather leave Private Relay or a VPN on, a pairing code on https://relayium.com/cross-network reaches the phone without touching either.

Both phones show the same public IP and neither card appears.
https://relayium.com/   # the hint under the device list names the router setting

The router is separating its own clients. Turn off “AP isolation / client isolation” in its Wi-Fi settings, or pair the two phones across networks with a code on https://relayium.com/cross-network when the router is not yours to change.

The iPhone warns, before you accept, that the whole batch has to be held in memory.
https://relayium.com/   # the warning states the batch size it is about to hold

Every iPhone browser is WebKit and has no File System Access API, so the batch is assembled in memory and Relayium warns past roughly 256 MiB. Send fewer files at a time, or send that file into a desktop Chrome or Edge instead, which writes it straight to disk with no size cap.

The counter finished but you cannot find the file on the iPhone.
https://relayium.com/   # the line under the request said where this browser saves

Safari does not put a download in the photo library. Look in the Files app under Downloads — the exact location is whatever Settings › Safari › Downloads points at, iCloud Drive or On My iPhone — and open it from there; a photo only reaches the Photos app if you save it out of the file yourself.

The transfer stalls or fails when you switch apps or the screen locks.
https://relayium.com/   # the Relayium tab has to be the one in front on both phones

A backgrounded tab may be throttled or suspended on either phone, and while it is, no bytes move. Relayium requests a screen wake lock where the browser offers one, which covers the screen switching off but grants no background execution and does not survive app switching — leave both tabs in front until the counter finishes.

On different networks: pairing and relay

The server generates exactly six decimal digits (0–9, including a leading zero). The sender signs in to create the code, while the person joining by code, link or QR never needs an account. It accepts new joins for five minutes; an already connected transfer is not cut off when that countdown ends.

Across networks, browsers use an encrypted TURN relay by design rather than trying a direct path first. The key stays on the two devices, so the relay forwards only end-to-end-encrypted ciphertext, cannot read the files and keeps no realtime content copy or history.

Other ways to move files between Android and iPhone

Relayium isn't the only option, and it's worth knowing the honest trade-offs of the alternatives:

Will my photos lose quality?

No. Unlike a messaging app, Relayium sends the original file byte-for-byte — no re-compression, no resizing. What lands on the iPhone is an exact copy of what left the Android phone.

To prove it, each file is verified end-to-end with a SHA-256 hash, so a photo or video that arrives is guaranteed identical to the one you sent. Large files are handled well too: a browser with the File System Access API (Chrome or Edge on a desktop) writes the incoming file straight to disk, with no size cap. Firefox, Safari and phone browsers — an iPhone is always WebKit — don't have that API, so there the batch is assembled in memory instead, and Relayium warns you before you accept once it goes past roughly 256 MB. That number is a deliberately cautious estimate rather than a measured ceiling: where it actually breaks down depends on the device's memory, its OS and how many tabs are open.

Frequently asked questions

Do I need to install an app on either phone?

No. Relayium runs entirely in the browser on both Android and iPhone. Open relayium.com on each device and you're ready — no download either way. On the same network a realtime transfer needs no account; pairing across networks just asks the sender to sign in. You can optionally add it to your home screen as a PWA, but that's just a shortcut.

Do both phones have to be on the same Wi-Fi?

No. The same network is the fastest path because the devices discover each other automatically, but a pairing code connects two phones across different networks — even one on mobile data and one on Wi-Fi. The transfer stays end-to-end encrypted in both cases, though pairing across networks requires the sender to sign in — the receiver never needs an account.

Are the photos compressed or changed in any way?

No. The original file is transferred byte-for-byte with no compression, and each file is checked end-to-end with a SHA-256 hash, so what arrives on the iPhone is bit-for-bit identical to what you sent from Android.

Open Relayium on both phones and send your first files across — no install, and no account needed on the same network.

Try Relayium now

Keep reading