AirDrop — WebRTC File Transfer
Send files directly between browsers over a peer-to-peer WebRTC connection — no upload, no server storage, no signup. Share a code, connect, and transfer files of any size instantly.
- Choose 'Send Files' to share, or 'Receive Files' to download from someone.
- The sender picks files (drag and drop or browse), then clicks 'Generate Code' to get an 8-digit room code.
- Share the code (or the link) with the receiver — via chat, email, or say it out loud.
- The receiver enters the code and clicks 'Connect'. Both browsers connect directly via WebRTC.
- Files transfer peer-to-peer with a real-time progress bar, and download automatically on the receiver's side.
All processing happens entirely in your browser. Your data never leaves your device.
Key Features
- Direct peer-to-peer file transfer — files never touch a server
- Works with any file type and any file size
- Real-time progress tracking with per-file and overall progress bars
- Shareable 8-digit code or direct link for easy connection
- Encrypted WebRTC data channel for secure transmission
- Drag and drop or browse to select multiple files
- Auto-download on the receiver's side when each file completes
- No account creation, no installation, no signup required
About AirDrop
Traditional file sharing services upload your data to a cloud server, store it there, and then let the recipient download it. This means your files travel through and sit on someone else's infrastructure — introducing privacy risks, upload speed bottlenecks, and file size limits tied to paid tiers.
ForgeKit AirDrop takes a fundamentally different approach using WebRTC (Web Real-Time Communication), the same browser technology behind video calls. Instead of uploading to a server, it establishes a direct peer-to-peer connection between the sender's and receiver's browsers. Your files travel directly from one device to the other over an encrypted data channel, never touching any intermediate server.
The only server involvement is a lightweight signaling step: the sender creates a room code, and the receiver uses that code to exchange the connection information needed for WebRTC to establish the direct link. Once connected, the signaling server is no longer involved — all data flows browser-to-browser. There are no accounts, no file size limits, no storage, and no data retention.
Frequently Asked Questions
No. Files transfer directly between browsers over an encrypted WebRTC peer-to-peer connection. The only server interaction is a lightweight signaling exchange to establish the connection — your actual file data never touches any server.
There is no enforced file size limit. However, since the transfer happens in real-time over a direct connection, very large files (multiple GB) will take longer and depend on both parties' internet speed and connection stability.
Yes. Unlike cloud-based file sharing, peer-to-peer transfer requires both the sender and receiver to have the tool open simultaneously. The sender generates a code, the receiver enters it, and the transfer happens in real-time.
If either party closes their browser or loses their connection, the transfer stops. You would need to start a new session with a new code to retry. Completed files that were already downloaded are not affected.
Currently, AirDrop supports one-to-one transfers. To send the same files to multiple recipients, you would start a separate session for each person.
Yes, in most cases. WebRTC uses STUN servers to traverse NATs and firewalls. However, very restrictive corporate firewalls or symmetric NATs may prevent a direct connection from being established.