# How to transfer files without uploading them to the cloud

Source: https://help.strongfolder.com/en/guides/send-files-without-uploading/
Updated: 2026-11-05

> To transfer files without uploading them, connect the two devices directly. Over the internet, a peer-to-peer browser tool such as StrongFolder streams files from the sender's browser to the recipient's over an encrypted WebRTC connection, with nothing stored on a server. Nearby, use AirDrop, Quick Share, a cable or a USB drive. The sender must stay online during the transfer.

1. **Open StrongFolder** — Go to [strongfolder.com](https://strongfolder.com) or click the StrongFolder Chrome extension. No account is needed.
2. **Choose files or a folder** — Pick what you want to send. The files stay on your disk — the browser only reads their names and sizes to create the link.
3. **Send the link** — Copy the link or show the QR code. When the recipient opens it, their browser connects to yours and the download starts at once.
4. **Stay online until it finishes** — The files come straight from your device, so keep the tab open until the recipient's download is complete. Then click Stop Sharing.

Almost every way to share a file online starts the same way: upload it to someone's server,
then send a link. That is fine for small files. For large ones it means waiting for an upload,
spending storage quota, and leaving a copy on a server you don't control. This guide shows how
to transfer files without uploading them first, and how the options compare.

**Key facts**

- **"Without uploading"** means the file goes **directly to the recipient**, not to a cloud first.
- **Over the internet:** a P2P browser tool (StrongFolder) — no account, no app, nothing stored on a server.
- **In the same room:** AirDrop (Apple), Quick Share (Android, Windows), a cable or a USB drive.
- **No quota, no waiting:** the recipient starts downloading at once. No size limit set by StrongFolder. The practical limits are free disk space on the recipient's device, connection speed, and how long both devices stay online.
- **The trade-off:** sender and recipient must be **online at the same time**; your tab stays open.

## What does "without uploading" actually mean?

Every network transfer moves bytes out of your device — that part can't be avoided. The
question is **where they go**. With a cloud service they go to the provider's server, wait
there, and are downloaded later. With a direct transfer they go to the recipient's device and
nowhere else.

That difference has practical consequences:

- **No upload wait.** The recipient doesn't wait for 20 GB to reach a server before they can
  start.
- **No storage quota.** Nothing counts against 15 GB of Google storage or 2 GB of Dropbox Basic.
- **No stored copy.** After the transfer there is nothing on a server to expire, leak or
  delete.
- **No size cap from a service**, because no service has to store the file.

## How can I transfer files without uploading them?

| Method | Works over the internet? | App or account needed? | Stored on a server? | Folders kept? | Best for |
|---|---|---|---|---|---|
| **StrongFolder (P2P in browser)** | **Yes** | **No** | **No** | **Yes** | **Anyone, anywhere, any size** |
| AirDrop | No, nearby only | Apple devices | No | Yes, Apple to Apple | Mac, iPhone, iPad |
| Quick Share | No, nearby only | Android / Windows app | No | Varies | Android and Windows PCs |
| Local-network apps (e.g. LocalSend) | No, same network | App on both devices | No | Varies | Home or office LAN |
| USB cable / external drive | No | No | No | Yes | Terabytes, no internet |
| Own server (SFTP, NAS) | Yes | Setup and accounts | Yes, on *your* server | Yes | Teams with IT support |

Only the first and last rows work across the internet. A home NAS or an SFTP server is still
an upload — just to a server you own, which you must run, secure and keep online.

### Direct browser-to-browser transfer

StrongFolder uses WebRTC, the same technology browsers use for video calls. Your browser and
the recipient's browser find each other through a small signalling service, then open an
encrypted data channel between them and stream the files through it. WebRTC encrypts every data channel with DTLS, so the file stream is encrypted in transit on every connection.

Sometimes a direct path is impossible — strict corporate firewalls and some mobile networks
block it. If a direct connection is impossible (strict corporate firewall, some mobile networks), the encrypted stream passes through a StrongFolder relay (TURN) server. The relay forwards the data and does not store it. Files are never uploaded to or stored on a StrongFolder server. The technical details are in
[how WebRTC file transfer works](https://help.strongfolder.com/en/guides/how-webrtc-file-transfer-works/).

[Send files now](https://strongfolder.com)
### Nearby sharing: AirDrop and Quick Share

If both devices are in the same room, built-in nearby sharing is the fastest route: AirDrop
between Apple devices, Quick Share between Android phones and Windows PCs. Both send files
directly over Wi-Fi or Bluetooth, but only across short distances and only within their
ecosystems. For a Mac and a Windows PC, or an iPhone and an Android phone, see the
[AirDrop alternative for Windows and Android](https://help.strongfolder.com/en/guides/airdrop-alternative-windows-android/) and
[Mac to Windows file transfer](https://help.strongfolder.com/en/guides/mac-to-windows-file-transfer/).

### Cables and drives

A USB cable between a phone and a computer, or an external SSD, avoids the network entirely.
It is the right call for terabytes, or when there is no internet. It is not the right call when
the recipient is in another city.

## Why would I avoid uploading to the cloud?

- **Size.** Free cloud and transfer plans stop at a few gigabytes; a 200 GB project doesn't
  fit. See [how to send a 100 GB file for free](https://help.strongfolder.com/en/guides/send-100gb-file-free/).
- **Time.** With a cloud, total time is upload *plus* download. Directly, both happen at once.
- **Privacy.** Contracts, medical scans, unreleased footage or source code don't need a
  second home on a provider's servers. More in [secure file sharing](https://help.strongfolder.com/en/guides/secure-file-sharing/).
- **Folders.** Cloud drives usually hand the recipient a ZIP; a direct transfer recreates the
  folder tree. See [send a folder without zipping](https://help.strongfolder.com/en/guides/send-folder-without-zipping/).
- **No sign-ups.** Neither side creates an account.

## What are the trade-offs of not uploading?

A file that is not stored anywhere can only be downloaded while it is being shared. That is
the core trade-off, and we prefer to say it plainly:

- **Both sides online at once.** The sender's browser tab must stay open and online until the recipient finishes downloading — files come from the sender's device, not from a server.
- **No "send and forget".** The link works while the sender keeps sharing. When the sender clicks Stop Sharing or closes the tab, the files are no longer available.
- **Your upload is the speed limit.** A home connection with a slow upload limits every
  transfer you send.
- **Each recipient uses your bandwidth.** One link can be opened by several recipients; each downloads directly from the sender.

The full explanation is in [why the sender stays online](https://help.strongfolder.com/en/guides/why-sender-stays-online/).

## When is the cloud still the better choice?

Upload to a cloud drive or a transfer service when:

- you need to send the link and **switch off your computer**;
- the recipient is in another time zone and will **download tomorrow**;
- many people will **browse, preview or comment** on the files for weeks;
- you need **version history** or collaborative editing.

Many people use both: a direct transfer for the big one-off delivery, a cloud folder for the
long-lived shared workspace. The comparison is in detail in
[P2P vs cloud file transfer](https://help.strongfolder.com/en/guides/p2p-vs-cloud-file-transfer/).

## Summary

To transfer files without uploading them, connect the devices directly — over the internet
with a browser-based P2P tool, nearby with AirDrop or Quick Share, or offline with a cable or
drive. You skip the upload wait, the quota and the stored copy; in exchange, you stay online
until the recipient finishes. Learn the basics in [P2P file transfer](https://help.strongfolder.com/en/guides/p2p-file-transfer/)
or go back to [how to send large files](https://help.strongfolder.com/en/guides/send-large-files/).

## FAQ

### Is it possible to send files without uploading them anywhere?

Yes. A peer-to-peer transfer sends the data straight from your device to the recipient's device instead of to a cloud first. The bytes still travel over the internet, but they are not stored on a server along the way.

### Do my files pass through any server?

Usually not. If a direct connection is impossible (strict corporate firewall, some mobile networks), the encrypted stream passes through a StrongFolder relay (TURN) server. The relay forwards the data and does not store it. To create the link, the service keeps transfer metadata: file and folder names, sizes and the number of files.

### Can the recipient download later, when I'm offline?

No. The link works while the sender keeps sharing. When the sender clicks Stop Sharing or closes the tab, the files are no longer available. If the recipient needs the files later, use a cloud link instead.

### Is a direct transfer faster than uploading to the cloud?

Usually the total time is shorter: with the cloud, the recipient waits for your full upload and then downloads; with P2P they download while you send. The speed is limited by the slower of your upload and their download.

### Do I need to install an app?

No. StrongFolder runs in the browser on both sides; the Chrome extension is optional. No account needed to send or receive. Signing in with Google is optional and keeps a list of your transfers.

### Is it safe?

WebRTC encrypts every data channel with DTLS, so the file stream is encrypted in transit on every connection. Files are never uploaded to or stored on a StrongFolder server.