PairDrop

Capabilities

• In-browser transfers with no install or account Both sides open a page in a modern web browser, see each other, and send, with the official positioning stating transfers work cross-platform with no setup and no signup.[1][2]

• Same-network peer-to-peer sharing Devices on the same local network discover each other and exchange images, documents, or text over direct WebRTC connections, and files on the same network are never sent to any server.[1][2][3]

• Persistent pairing for internet transfers Devices pair with a 6-digit code or QR code and then find each other through shared secrets regardless of network, which covers public Wi-Fi, company networks, VPNs, and mobile hotspots.[1]

• Temporary public rooms A 5-letter code or QR code gathers distant devices into one visible room, and leaving the page leaves every room, so the room exists only for the session.[1]

• Self-hosting with Docker or Node.js Documented images come from linuxserver.io and the project's own container registry, with a compose example, environment flags, and support for custom STUN and TURN servers on a self-run instance.[1]

• Files and text with ZIP bundling and previews Transfers start after the recipient accepts, completed files auto-download where the browser allows, multiple files arrive as one ZIP, and video and audio get in-page previews.[1]

• Share-menu, context-menu, and CLI sending Documented paths cover the Ubuntu file-manager context menu, the Windows context menu, the iOS and Android share sheets, and a command-line interface, so sending does not always start from the open page.[1]

• PWA install and personal touches The app installs as a progressive web app on desktop Chromium browsers, Android, and iOS Safari, with editable display names, light and dark themes, wake-lock during transfers, and community translations.[1][2]

Who will love it

• Mixed-device households Homes mixing Android phones, iPhones, and Windows, Mac, or Linux computers get one documented receiving path on every screen, including original-quality photo handoffs where platform-locked sharing falls short.[1][2]

• Cloud-averse sharers on a budget Individuals who would rather keep transfers off third-party servers pay nothing: the software is libre, the public instance is free, and development is sustained by donations.[1][2][3]

• Self-hosters and homelabs Anyone already running a home server can point the documented Docker image at their own network, keep discovery on private IPs, and substitute their own TURN server for cross-network transfers.[1]

Boundaries to check

• One-shot sharing, not continuous sync Each transfer is a deliberate send that both sides accept in the moment; folders do not stay mirrored in the background, so anyone wanting always-up-to-date replicas should evaluate a sync tool instead.[1]

• No central administration With no accounts, no SSO, and no management console documented, teams that need to provision, audit, or revoke sharing centrally will find no supported controls.[1][2]

• Both sides must be present No link-based or email delivery is documented: if the recipient does not have the page open when you send, the transfer cannot complete, so one-sided drop-offs belong in a link-sharing tool.[1]

Fit and compatibility