Getting files in

Five ways to get a large file onto an iPhone, and when each is the right one

iTunes file sharing is a memory, AirDrop only exists between Apple devices, and e-mailing yourself a 4 GB film has never worked. What is left is a handful of genuinely different approaches, and the one that suits a single file from a friend is not the one that suits forty gigabytes from your own computer.

5 min read Updated 29 July 2026

The five routes

Ordered roughly by how much setup they need. All five end with the file on the device; what differs is who else touches it on the way.

01

A web page served by the phone itself

The app runs a small web server on the local network. You open the address it shows in any web browser on your computer, and drag files into the page. Nothing leaves the network, and the computer needs no software at all — not even a matching operating system.

Works well when

Any computer, no account, no install, no cable. Fast on modern Wi-Fi, and the obvious choice for bulk transfers from a desktop.

Where it falls down

Both devices must be on the same network, and it only runs while the app is open in front of you.

02

A direct link between two devices

Two phones establish an encrypted connection to each other, usually confirmed with a short code, and the file travels straight across. A small signalling server helps them find each other; the file itself does not pass through it.

Works well when

Works across platforms where AirDrop does not, and there is no cloud account holding a copy afterwards.

Where it falls down

Both people have to be present at the same time, and both apps have to stay open.

03

A cloud account you already have

Dropbox, OneDrive, Box, pCloud and the rest. Upload from the computer, open the account inside the app on the phone, download what you need.

Works well when

Asynchronous — nobody has to be present. Files stay available afterwards, from anywhere.

Where it falls down

Every byte crosses somebody else’s servers twice, quotas apply, and large libraries are slow both ways.

04

Your own server, over WebDAV

A Nextcloud, ownCloud or plain WebDAV share. The app connects with an address and credentials, and browses it like a folder.

Works well when

Your hardware, your rules, no size limits but the disk. The best option for a permanent library you do not want on the phone.

Where it falls down

You have to run and secure the server, and remote access means dealing with certificates and ports.

05

An external drive

A USB-C stick or SSD plugged straight into an iPad or a Mac, read in place.

Works well when

By far the fastest for large volumes, and nothing is copied to the device at all if the app can play from the drive.

Where it falls down

Not an option on an iPhone in practice, and the drive has to be formatted in something iOS reads — exFAT or APFS.

Which one for which job

The jobThe route that fitsWhy
Forty films from your own computerWeb browser page over Wi-FiNo quota, no upload to anywhere, and the drag-and-drop is hard to beat
One video a friend recordedDirect device-to-device linkNo account for either of you, nothing left behind afterwards
Documents you also want on other devicesCloud accountThe copy on the server is the point, not a side effect
A permanent library you keep at homeWebDAV / NextcloudPlay from the server, keep only what you are watching on the device
A holiday’s worth of footage from a cameraExternal drive on an iPadSpeed, and no need to duplicate it onto the tablet at all

Why the local route sometimes refuses to appear

Local transfers rely on two devices being able to see each other on the same network, and there are three routine reasons they cannot. The first is client isolation — a setting on many routers, and the default on nearly every hotel, café and campus network, that lets devices reach the internet but not one another. It is a sensible security default and it makes local transfer impossible; a phone hotspot is the usual workaround.

The second is being on different networks that look like one: the computer on the 5 GHz band of a mesh system and the phone on a guest network, or one of them on a VPN that routes everything through somewhere else. A VPN on either device is worth turning off as the first diagnostic step.

The third is simply that the serving app has been backgrounded. A phone cannot keep a web server answering while it is suspended, so the address stops responding the moment you switch apps. This is not a limitation an app can engineer around; it is the same suspension rule that governs downloads.

What to check before you open a transfer route

A transfer server is, for as long as it runs, a way into the files on your device. These are not paranoid precautions — they are the difference between a tool and a hole.

  • A code that is required, not optional

    Anything reachable on the network should be behind a PIN. On a shared network, an unauthenticated file server is an open invitation.

  • Destructive operations off by default

    Uploading is one permission; deleting and renaming are another. The second set should start switched off and be granted deliberately.

  • It stops when you stop

    The server should stop with the screen, not linger in the background all afternoon.

  • Credentials in the Keychain, not the database

    Applies to cloud and WebDAV accounts. A password in an app’s own database is a password in that app’s backup.

  • Know whether anything passes through a third party

    A peer-to-peer route may still use a relay when a direct connection cannot be made. Worth knowing which you are getting.

Questions people ask

Can I still use iTunes file sharing?

The mechanism survives in Finder on macOS and in the Apple Devices app on Windows, and it works for apps that enable it. It is slow, it needs a cable, and it has no idea about folders — which is why practically every app that handles large media now offers a network route instead.

Is a transfer through a web browser secure?

On your own network, behind a PIN, with the server stopping when you leave the app — yes, in the sense that matters: nothing leaves the local network and nobody without the code can use it. On an untrusted network it is only as safe as the PIN, which is why the PIN should not be optional.

Why is my transfer slower than my Wi-Fi should allow?

Usually the phone’s radio, not the network: a phone on 2.4 GHz two rooms away is a small fraction of what the same phone does standing next to the router on 5 GHz. Thousands of tiny files are also far slower than one large one, because each has its own round trip.

Does device-to-device transfer work over mobile data?

Usually, but not always — some carrier networks block the direct connection and force a relay, which is slower. On the same Wi-Fi it is direct and fast, and that is where these transfers belong.

FoxDL

The routes FoxDL supports

All five, with the local two built so that no byte passes through a server we run.

  • Wi-Fi Transfer — open the address in any computer’s web browser, enter the 6-digit PIN, drag files into the page. Foreground-only, on purpose.
  • Per-operation permissions on that page, with the destructive ones off by default.
  • Device-to-device transfer over an encrypted peer-to-peer link, opened with a 6-digit code, with send-more and speed/ETA while it runs.
  • Cloud accounts — Dropbox, OneDrive, Box, pCloud, Baidu and Aliyun.
  • WebDAV, Nextcloud and ownCloud for your own server.
  • External drives and folders browsed and played in place on iPad and Mac.
  • Share sheet, drag and drop, and “Open in” from any other app.
  • Every credential lives in the Keychain, never in the database and never in a log.

Free allowances differ: on iPhone and iPad a short break per session, on Mac Wi-Fi Transfer is free and device-to-device is once a day. Pro removes both.

Questions people ask about this

All questions

Keep reading

Your library, finally in one place.

Free to download. No account, no sign-up, and the whole feature set is in the free version.

Download on the App Store