Skip to main content
Preparing workspace

Device-to-Device File Drop

Send files between phones, tablets, and computers with a private WebRTC connection. No upload, account, or server storage required.

Still loading. If the tool doesn’t appear, reload this page.

About this tool

Device-to-Device File Drop

Send files directly between devices with a private peer-to-peer connection.

Device-to-Device File Drop creates a direct WebRTC connection between two browsers. Start a connection on one device, exchange the short setup messages with the other device, and then send files without uploading them to a storage service. File data travels directly between peers and is not stored by this tool. Like AirDrop, it sends files straight from one device to another, but it runs in the browser, so there is nothing to install. This tool is independent and not made by or affiliated with Apple.

How to use Device-to-Device File Drop

  1. 1

    Choose Start a connection on the sending or first device and copy its connection message.

  2. 2

    On the second device, choose Join a connection, paste the message, and copy the response back.

  3. 3

    Paste the response into the first device, connect, then add files and send them.

Why use Device-to-Device File Drop

  • Direct transfer

    Files travel over a peer-to-peer WebRTC data channel instead of being uploaded to this website.

  • Works across platforms

    Use modern browsers on Windows, macOS, Linux, Android, or iOS without installing an app.

  • No account required

    The setup is temporary and the tool does not require a login or cloud storage.

Frequently asked questions

Are my files uploaded?

No. After the connection is established, files are sent directly between the two browsers. The setup messages contain connection metadata, not your files. To find a route, each browser asks Google's public STUN server (stun.l.google.com) for its own network address; no file data goes to it. There is no relay server, so two devices on networks that block direct connections, such as some office or mobile networks, cannot connect.

Why do I need to copy connection messages?

WebRTC needs a small signaling exchange before two browsers can connect. This frontend-only version keeps that exchange under your control rather than sending it through a service.

Can I send multiple files?

Yes. Add one or more files, then send them together. Each recipient can download files individually as they arrive.