Direct transfer · peer-to-peer · encrypted

Send files straight to another device.

Files travel live from one browser to the other while you're both on the page. No app, no account, no upload to wait for.

  • Live, like a call

    Both of you keep the page open until the files arrive.

  • Never stored

    Encrypted on the sending device and not kept on our servers.

  • Nothing to install

    Any browser, any device. No account. Up to 1 GB per file.

Verifiable build·check the code yourself

What each person does

The person receiving

  1. Open Receive

    You get a short code and a QR code, valid for two minutes until someone connects.

  2. Give it to the sender

    Send them the link, let them scan the QR code, or read the code out.

  3. Check and accept

    You see the file names and sizes, and accept only what you expect.

  4. Files save to your device

    Keep the page open until it says the files were received.

Open Receive

The person sending

  1. Get the receiver's code

    Or just open the link they send you — it connects automatically.

  2. Enter it or scan it

    Type the code on the Send page, or scan their QR code with your phone.

  3. Choose your files

    The receiver sees what you're sending and has to accept it.

  4. Wait for “Files sent”

    Keep the page open until the receiver's device confirms everything arrived.

Open Send

Direct transfer or a cloud link?

Direct transfer

This page
  • Sent live from one device to the other
  • Nothing kept on a server afterwards
  • Both people need the page open at the same time

Best when you're both available now — your own devices, or someone you're talking to.

Cloud link

Cloud Share
  • Upload once, get a link that expires
  • They download it whenever they like
  • Nobody has to be online at the same time

Best when the other person will get to it later, or several people need the file.

Use a cloud link instead →

Where Your File Actually Goes

What peer-to-peer means here

Most ways of sending a file make two journeys: up to someone's server, then back down to the recipient. A direct transfer makes one. The file goes from the browser on one device to the browser on the other, and is never written to storage along the way.

That changes three things at once. There is no upload to wait for before the other person can start receiving. There is no copy left sitting on a server after you are done. And there is no storage quota to run into, because nothing is stored.

Three routes, one layer of encryption

When the two devices can reach each other, larger files travel over a direct WebRTC data channel between them — the one route where your file data never touches our infrastructure at all. Setting that channel up takes a moment, so small files skip it and go through our socket relay instead: the setup would take longer than the transfer.

Corporate firewalls and some mobile carriers block a straight route between devices. Some peer connections cannot find a direct route and are relayed by our TURN server instead. It forwards packets that are already encrypted twice over — your AES-GCM ciphertext inside the connection's own DTLS — and holds no key for either layer.

If no peer connection can be made at all, the socket relay is the last resort. Chunks are relayed through our server when a direct connection is impossible, and for small transfers where negotiating one would take longer than sending the file — still as ciphertext we hold no key for. The relay is a bridge, not a reader.

Whichever route is taken, the encryption described below happens on the sending device before the data leaves it. The route decides how the bytes travel, not whether they are protected.

How the file is encrypted

The receiving browser generates a per-session RSA-2048 (RSA-OAEP, SHA-256) key pair. The sender wraps a random 256-bit AES key with that public key, then encrypts every chunk with AES-256-GCM before it leaves the device.

The private key is generated inside the receiving browser, is non-extractable, and is destroyed when the tab closes. It is never transmitted.

Each chunk carries a GCM authentication tag with its sequence number authenticated alongside it, and a SHA-256 hash of the whole file is verified on arrival.

Checking you are sending to the right device

Both devices display a fingerprint of the public key each is actually using, as 8 emoji and 12 hex characters. Comparing them rules out a substituted key — the one attack encryption alone cannot prevent. If the codes on the two screens match, nobody has slipped their own key into the middle of the connection.

What this cannot promise

That holds as long as the code running in your browser is the code we describe. For the encryption itself you no longer have to take that on trust: it is served as a published build you can reproduce byte for byte and compare against what your browser loaded. What remains is the application around it, which is closed source — it is what hands your file and your password to that code, and nothing here proves it does not read them first.

The security page sets out the full architecture, including what you can check for yourself without trusting us.

When to Use a Direct Transfer

A good fit when…

  • Moving files between your own devices. Phone to laptop, old PC to new one, tablet to desktop — whatever the operating systems.
  • A large file for someone you are talking to now. They receive it as it sends, instead of waiting for an upload to finish first.
  • Files you would rather not store anywhere. Contracts, ID scans and unreleased work leave nothing behind on a server afterwards.
  • A borrowed or locked-down computer. It runs in the browser, so there is nothing to install and nothing to sign into.

Use something else when…

  • The other person is not online right now. A direct transfer needs both browsers open at once. A link they can open later suits this better: Cloud Share
  • Several people need the same file over days. Upload it once and share one link rather than running a transfer per person.
  • One file is larger than 1 GB. Split it into parts first, or export a smaller copy for the transfer.
  • You need someone to send a file to you. Give them a link they can upload to instead: File Requests

Direct Transfer vs the Usual Options

The common ways to move a file from one device to another, compared on what they store and what they ask of you.

Direct transferCloud linkEmail attachmentUSB cable
Stored on a serverNeverUntil the link expiresIn both mailboxes, indefinitelyNo
Largest fileUp to 1 GBPer-upload limit, shown as you add filesAround 25 MBFree space on the drive
Both people presentYes, at the same timeNoNoSame room
Install or sign-upNeitherEmail verified onceAn email accountA cable, sometimes drivers
EncryptionAES-256-GCM per chunk, key wrapped with RSA-2048Optional, with a passwordUsually in transit onlyNone
Works across platformsAny modern browserAny modern browserYesOften awkward, e.g. iPhone to Windows

Direct Transfer Questions

The receiver. They open the Receive page, which shows a short code and a QR code. The sender then enters that code on the Send page, scans the QR code, or opens the link the receiver sends them. If you're the sender and don't have a code yet, ask the receiver to open Receive first.

Open the Receive page on the device that should get the file and it shows a room code and a QR code. On the sending device, scan the code or type it into the Send page, choose the file, and the receiver approves it. The file then streams from one browser straight to the other, with no upload step and no copy left on a server.

It is as safe as its encryption and its pairing. Here, the receiving browser generates a per-session RSA-2048 (RSA-OAEP, SHA-256) key pair. The sender wraps a random 256-bit AES key with that public key, then encrypts every chunk with AES-256-GCM before it leaves the device. The safety code shown on both screens lets you confirm you are connected to the right device.

Yes. Nothing is stored in between, so the file has nowhere to wait — both browsers need to be open until it finishes. If the other person will open it later, send a cloud link instead.

Sometimes, but only as ciphertext, and it is never written to storage. When the two devices can reach each other, larger files go straight between them and never touch our infrastructure. If a network blocks that route, the connection is relayed through a TURN relay server; small files, and connections that cannot be made at all, go through our socket relay. On every route the data is encrypted before it leaves the sending device, so anything passing through us is ciphertext we hold no key for.

Up to 1 GB per file. For anything larger, split it into parts or send a compressed copy.

No. A direct transfer works across different networks, including mobile data, and is usually just as fast as being on the same Wi-Fi — what actually matters is whether the two devices can connect directly at all. Mobile data and heavily restricted networks are the ones most likely to block that and fall back to our relay, which is slower.

Yes. It runs in any modern browser — Safari, Chrome, Edge or Firefox — so any pair of devices works, including combinations that AirDrop and Quick Share do not support.

Short interruptions are handled: both sides wait for the other to reconnect, and the receiver asks for any chunks it missed. If a tab is closed, the transfer ends and has to be started again.

The file's contents are never stored or logged. Non-content details are — the file name, size and type, timestamps, which route it took, and each side's IP address and browser — for rate limiting and abuse prevention. The privacy policy lists all of it.