You have a 2 GB video on the laptop and it needs to be on the phone. There is no cable in reach, the phone is nearly full, and you would rather not upload a personal file to an account somewhere just to download it again. This is one of the most-searched questions on the internet for a reason: every obvious route has a wall in it.
Here is what actually works, in the order worth trying, and where each method breaks.
- A direct browser-to-browser transfer needs no app, no account and no cable, works across different networks, and stores nothing on a server.
- Quick Share or AirDrop is fastest when both devices are on the same network and within reach.
- A cloud link is the right answer only when the file must wait, or reach several people.
- Email caps attachments near 25 MB, which is why none of this is simple by default.
Why the usual routes stall
Email caps attachments near 25 MB. Chat apps compress video and cap the rest. Cloud storage makes you upload the whole file and then download it again — twice the waiting, and the file sits on a server afterwards. A USB cable needs the cable, a free port, and sometimes a driver.
None of those are bugs. Email was designed for letters, chat apps for messages, and cloud drives for storage rather than for moving one file between two devices you already own.
Method 1 — a direct browser-to-browser transfer
This is the one most guides leave out, because there is no app to sell you. Modern browsers can open an encrypted connection directly between two devices and stream a file across it. Nothing is uploaded, nothing is stored, and no account is needed on either side.
How it works in practice:
- Open the transfer page on the device that has the file and pick it.
- The page shows a short passkey — six digits, or a QR code.
- On the second device, open the same page and type the passkey, or scan the code.
- The two browsers connect to each other and the file streams across.
What makes it worth trying first:
- No install. Both sides need a browser, which they already have.
- No size ceiling set by a service, because the file never lands on one.
- Cross-network. Unlike Quick Share or AirDrop, the two devices do not have to be on the same Wi-Fi. A laptop on home broadband can send to a phone on mobile data.
- Nothing left behind. When the tab closes, the transfer is gone — there is no link to expire and no copy to delete.
Where it breaks: some strict office, campus and hotel networks block direct connections between devices. If the connection will not establish, move one device to mobile data and it will almost always go through. Both devices also have to stay awake — a phone that sleeps mid-transfer stops it.
VaultStorage has this built in: open the passkey transfer on the home page, no account needed, and the file goes straight from one device to the other.
Method 2 — the built-in share on the same network
If both devices are yours and on the same Wi-Fi, the operating system already has this:
- Android and Windows: Quick Share (formerly Nearby Share)
- Apple devices: AirDrop
- Windows to Windows: Nearby sharing
These are fast — often faster than anything else here, because they can drop to a direct Wi-Fi link — and they need no third party at all.
Where they break: the two devices must be near each other and usually on the same network, both must have Bluetooth and Wi-Fi on for discovery, and cross-ecosystem pairs (an iPhone and a Windows laptop, say) are still awkward. They are the best answer when both devices are on your own desk, and no answer at all when one of them is in another city.
Method 3 — a local server over your own Wi-Fi
The technical route: run a small FTP or SMB server on one device and connect to it from the other, both on the same network. File managers on most phones can do this without an extra app.
It is the best option for moving a lot of files at once — a whole folder of photos rather than one video — and it is completely offline. It is also the fiddliest: IP addresses, permissions, and a setup you will have to look up again next time.
Method 4 — cloud storage, used deliberately
Cloud drives are not the wrong answer; they are the wrong default. They are genuinely the best choice when:
- the file has to reach several people, or someone in another time zone
- the recipient should be able to fetch it later, not right now
- you want a copy kept on purpose, as a backup
They are the wrong choice when the file is personal, when you only need it on your own second device, or when you will forget to delete it afterwards — which is usually.
Speed, honestly
The bottleneck is almost never the method; it is the slower of the two connections. A direct transfer between two devices on good Wi-Fi is limited by the Wi-Fi. A transfer to a phone on mobile data is limited by the mobile signal. A cloud round trip is limited by your upload speed, which on most home connections is a fraction of the download speed — which is why a 2 GB upload can take twenty minutes while the download takes two.
That single fact is the reason a direct transfer usually wins: it moves the file once instead of twice.
Sending to someone else, not to your own device
Half of these searches are not about two devices you own. Somebody needs a file — a video, a scan, a folder of photos — and they are not in the room.
That rules out AirDrop, Quick Share and a local server straight away: all three need the two devices near each other or on one network. What is left is a direct browser transfer or a cloud link, and the choice comes down to one question: does the other person need it right now, or later?
- Right now, both online: a direct transfer. You send the passkey by message, they open the page, the file moves. Nothing is stored, nothing to clean up.
- Later, or to several people: a cloud link with an expiry date and, if the file is private, a password. Then set a reminder to delete it — the link outliving its purpose is how files leak.
What each method exposes
Worth knowing before you pick one, because "private" means different things here:
| Method | Where the file rests | Who could reach it |
|---|---|---|
| Direct browser transfer | Nowhere — it streams device to device | Only the person holding the passkey, while the tab is open |
| Quick Share / AirDrop | Nowhere | Devices in range during the transfer |
| Local FTP or SMB | On the sending device | Anyone on that Wi-Fi, if the share is open |
| Cloud link | On the provider's servers until deleted | Anyone with the link, plus the provider |
| Email attachment | In both mailboxes, indefinitely | Both mail providers, and anyone in either inbox |
Email is worth a second look on that table. A passport scan mailed to yourself sits in two mailboxes forever, gets indexed by search, and travels with the account if it is ever compromised. It is the least private option on the list and the one people reach for first.
When a transfer stalls
Four things cause almost every failure, and each has a quick fix:
- The phone went to sleep. Keep the screen on for the length of the transfer; a browser tab in the background gets suspended.
- The network blocks direct connections. Office, campus and hotel Wi-Fi often do. Switch one device to mobile data.
- The receiving device is full. A 2 GB video needs 2 GB free, plus room for the browser to assemble it.
- The browser is old. Direct transfers need a current browser on both sides; anything from the last couple of years is fine.
If a transfer breaks halfway, start it again rather than trying to resume — a broken stream leaves a partial file that looks complete until you open it.
Which one to use
| Situation | Use |
|---|---|
| Two of your devices, same desk | Quick Share / AirDrop |
| Two devices on different networks | Direct browser transfer |
| Sending to someone else, right now | Direct browser transfer |
| Sending to several people, or for later | Cloud link with an expiry |
| A whole folder, offline | Local FTP or SMB |
| Anything under 25 MB to one person | Email, honestly |
One habit worth keeping
Whatever method you pick, decide before you send it whether a copy should survive the transfer. A direct transfer leaves nothing behind, which is exactly right for a passport scan and exactly wrong for the only copy of a family video. If the file matters, put it somewhere you control first — then send it.
If the file you are moving is a receipt, a bill or a warranty card, it is worth keeping it where the expiry date is tracked too rather than only in your downloads folder.
Questions people ask
What is the largest file I can send this way?
With a direct browser-to-browser transfer there is no size limit imposed by a service, because nothing is stored on the way. The real limits are the space on the receiving device and both devices staying awake until the transfer finishes. Tens of gigabytes are ordinary.
Do both devices have to be on the same Wi-Fi?
No. A same-network method like Quick Share or AirDrop needs both devices on the same network; a browser-to-browser transfer works across networks, so a laptop on home broadband can send to a phone on mobile data. Some strict office and hotel networks block the direct connection, and that is the one case where it fails.
Is a direct transfer actually private?
The data goes from one device to the other over an encrypted connection and is not stored anywhere in between. Compare that with a cloud link, where the file sits on a server until you remember to delete it, and anybody who gets the link can open it.
Why is email refusing my 40 MB attachment?
Most mail providers cap attachments around 25 MB, and the receiving server may cap them lower still. Email was never built for large files — that limit is the reason every other method on this page exists.