PairDrop: public rooms, pairing secrets, and the relay you depend on
PairDrop: Transfer Files Cross-Platform. No Setup, No Signup.
At a glance
- What is it?
- PairDrop is a browser based, AirDrop inspired file transfer tool forked from Snapdrop, with peer to peer WebRTC transfers, persistent device pairing, temporary public rooms, and an optional TURN relay for peers behind NAT. Its default Docker port binding and its two license declarations are the parts to check before you deploy it.
- Who is it for?
- PairDrop fits people moving photos and documents between their own devices on a network they control, and fits self-hosters willing to run their own STUN and TURN configuration. It does not fit unattended transfers, air-gapped deployments without a relay, or teams that need the license and the deployed ports settled before shipping.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Activity is slowing. The repository last received commits 6 months ago.
- What is it written in?
- Mainly JavaScript, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- schlagmichdoch/PairDrop11,815 ★ · +360
| Repository | 2026-09-22 | 2026-11-15 |
|---|---|---|
| schlagmichdoch/PairDrop | 11.5k | 11.8k |
360 Stars in the last 54 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Public rooms vanish when you close the tab
Two of the mechanisms that distinguish PairDrop from the Snapdrop it forks behave very differently. Persistent device pairing is durable: you pair two devices with a 6-digit code or a QR-Code, the two sides exchange shared secrets, and paired devices find each other again even after you reopen PairDrop, independently of which local network they are on. Public rooms are the opposite. You join with a 5-letter code or a QR-Code, every device in that room sees every other device, and the room ends when you close PairDrop. The consequence is that a public room cannot carry work across a session boundary. Both sides have to be present at the same time with the code still valid, so a transfer started on a train and finished at a desk does not work. Decide which mechanism you need before promising someone a file will be waiting.
Pairing survives a restart, but the README never says where secrets live
The pairing mechanism is built on shared secrets rather than on network adjacency, which is what lets two paired devices find each other across different local networks. The README states that pairing is persistent, that devices are discoverable after reopening PairDrop, and that you can edit and unpair devices easily. What it does not state is where those shared secrets are kept, whether the 6-digit code can be entered on a different browser or a different machine, how a pairing is revoked beyond unpairing in the interface, and what happens to paired devices when site data is cleared. The consequence for a security review is that you cannot complete one from the README alone: the persistence claim is clear, the storage and revocation story is not. Anyone relying on pairing to reach a device that has been reset, reinstalled, or wiped has to verify recovery behavior directly in the app.
The compose file binds the web UI to 127.0.0.1
The shipped docker-compose.yml pulls the LinuxServer image and publishes the UI on loopback only:
- WS_FALLBACK=false # Set to true to enable websocket fallback if the peer to peer WebRTC connection is not available to the client.
- RATE_LIMIT=false # Set to true to limit clients to 1000 requests per 5 min.
- RTC_CONFIG=false # Set to the path of a file that specifies the STUN/TURN servers.
- DEBUG_MODE=false # Set to true to debug container and peer connections.
- TZ=Etc/UTC # Time Zone
ports:
- "127.0.0.1:3000:3000" # Web UI. Change the port number before the last colon e.g. `127.0.0.1:9000:3000`Local network file sharing is the headline feature, and the default mapping keeps the interface reachable from the machine it runs on and nowhere else. The comment explains how to move the host port, but it changes the number before the last colon, not the bind address, so a copy of this file exposes nothing to your colleagues. You have to edit the address yourself, and once you do, every device on that network can load the page. The image reference is lscr.io/linuxserver/pairdrop:latest, a floating tag, so a restart after a pull can bring a different build than the one you tested.
Rate limiting lives only in the start:prod script
Two operational flags exist in package.json, and neither is on by default in the obvious entry point:
"start": "node server/index.js",
"start:prod": "node server/index.js --rate-limit --auto-restart"The Dockerfile ends with ENTRYPOINT ["npm", "start"], so an image you build yourself from that file runs the plain script with neither flag. Rate limiting and restart on error are reachable only through start:prod, or by passing the flags directly. The RATE_LIMIT environment variable in the compose file belongs to the LinuxServer image and is set separately from the command line flag. The consequence is that the hardened path is not the default path: if you build from the repository rather than pulling the published image, you get an unprotected server unless you change the command, and the rate limit that compose documents as 1000 requests per 5 minutes is not applied by anything in the Dockerfile. Also worth knowing: engines requires node >=15 and package.json declares no devDependencies at all.
LICENSE says GPL-3.0 while package.json says ISC
The repository ships a LICENSE file and the project is published under GPL-3.0, but the package manifest carries a different declaration: the license field in package.json reads ISC. Nothing in the repository reconciles the two, and package.json also leaves author and description empty. The consequence falls on anyone who redistributes rather than on anyone who runs the app. Self-hosting from a clone touches none of it, but shipping a modified copy, bundling the server into a larger product, or publishing an image built from this tree forces the question of which terms apply. Additional terms are not limited to the main file either: the README links MIT copies for NoSleep and heic2any inside the licenses directory, alongside a Dockerfile that installs dependencies from npm with NODE_ENV=production. Resolve the license question before you fork the project rather than after.
No transfer starts until a request is accepted
The transfer flow is deliberately hands-off on the sender side. Files move after the recipient accepts a request, and completed transfers auto-download where the browser allows it. Several files are packaged as a ZIP using zip.js and arrive as one download with a single overall progress indicator, and on Android and iOS the Share menu handles downloading, sharing, or saving to the gallery. HEIC and HEIF images are converted through heic2any, so iPhone photos keep working in browsers that cannot display the format. The constraint is the acceptance step: there is no unattended send, no shared folder, and no way to push a file to a device that is not being watched by a person. If the receiving end is a phone in a pocket, the transfer sits until someone opens it. The auto-download wording also carries a condition, if possible, so browsers that block automatic saving leave you tapping through the prompt.
Peers behind NAT rely on the PairDrop TURN relay
The README says PairDrop connects devices in complex network environments, including public Wi-Fi, company networks, iCloud Private Relay and VPN setups, and devices on a mobile hotspot. The exception is a device outside your local network that sits behind a NAT, and the README states those are auto-connected via the PairDrop TURN server. That relay is the project's own infrastructure, which is the single most important operational fact here. Self-hosting gives you the option to specify your own STUN and TURN servers, and the repository ships rtc_config_example.json, turnserver_example.conf, docker-compose-coturn.yml and a separate how-to document for hosting an instance. What follows for the reader is a dependency you cannot see from the code: if your own deployment has no relay configured, peers behind NAT have no documented path to each other. RTC_CONFIG defaults to false and WS_FALLBACK defaults to false, so a fresh instance runs without either escape hatch.
Master is ahead of the last tag
The most recent push to the default master branch is dated 2026-04-22, while the newest release is v1.11.2 from 2025-02-24 and the version field in package.json also reads 1.11.2. That gap has a practical meaning: master may be past the last published tag, so a clone may not be the same artifact as v1.11.2. For self-hosters this matters because the compose file does not pin a version either, pulling lscr.io/linuxserver/pairdrop:latest. Beyond versioning, the tree carries a second surface area: a pairdrop-cli directory and documentation for sending from the command line, dev and docker-compose-dev.yml for development, Weblate for translations, and context menu integration for Ubuntu Nautilus and Windows plus Share menu hooks on iOS and Android. The project is broad, GPL-3.0 licensed, supported by donations, and built on a small dependency set of express, ws, express-rate-limit, ua-parser-js and unique-names-generator.
Editorial conclusion
PairDrop fits people moving photos and documents between their own devices on a network they control, and fits self-hosters willing to run their own STUN and TURN configuration. It does not fit unattended transfers, air-gapped deployments without a relay, or teams that need the license and the deployed ports settled before shipping. Before you rely on it, check whether the LICENSE file or the ISC field in package.json governs your redistribution, decide whether you will bind the container to more than 127.0.0.1, and confirm which tag of the image you actually run.
Frequently asked questions
what is pairdrop
PairDrop is local file sharing in a web browser, inspired by Apple's AirDrop and forked from Snapdrop. Transfers go peer to peer over WebRTC with a Node.js backend and a WebSocket fallback option, and it can be self-hosted with Docker or Node.js.
how to use pairdrop
PairDrop works as a web app on any device with a modern browser, or you can host your own instance with Docker or Node.js. Files are transferred after the recipient accepts the request, and multiple files arrive as a single ZIP download.
Does PairDrop work with iPhone?
The web app works on all devices with a modern web browser, and on iOS you can send files directly from the Share menu. After a transfer you can download, share, or save to the gallery through the Share menu, and HEIC images are converted for browsers that cannot display them.
how to use pairdrop on android
On Android you send files straight from the Share menu, and once a transfer completes you can download, share, or save to the gallery the same way. Sending multiple files at once shows one overall progress indicator, and a batch arrives as a ZIP.
Is PairDrop safe?
The README makes no security guarantee and documents no key handling. It states that transfers are peer to peer between devices on the same local network, and that devices behind a NAT are auto-connected through the PairDrop TURN server.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/schlagmichdoch-pairdrop)Star history chart for your README
[](https://hysenlabs.com/projects/schlagmichdoch-pairdrop)Was this useful?