Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
Self-host PairDrop
updated Nov 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Nov 2026 · how we test
We earn commissions when you shop through the links below. Full disclosure →
A browser-based way to send files and text between devices on the same network, in the style of AirDrop: open the page on two devices and they find each other, with no account or app install. Files go peer to peer over WebRTC, devices can be paired by a code or QR for use across networks, and a WebSocket fallback is available. A Node.js server with a static web client.
Pick PairDrop when you want to move a file or a snippet of text between your own devices without accounts, cables or a cloud service: open the page on two devices and they appear to each other, and files travel peer to peer over WebRTC. Devices can also be paired with a code or QR so they find each other across networks, rooms can be joined by a code, and a WebSocket fallback can be enabled for clients without a direct connection. It is GPL-3.0 Node.js. Our snippet runs the image upstream publishes on the GitHub Container Registry (`ghcr.io/schlagmichdoch/pairdrop`), pinned to `v1.11.2`, with the project's default settings. We did not find an upstream RAM minimum, so our 64 MB floor is an estimate. Within the file-sharing category it is the odd one out: copyparty, SFTPGo and Zipline store files on the server, PsiTransfer holds them for a link, and PairDrop keeps nothing on the server at all.
What you need
Any VPS with at least 64 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
Paid link — we earn a commission if you shop through it.
Install
Run these commands on your server:
# PairDrop — local file and text transfer between devices — upstream's GitHub Container Registry image, pinned to v1.11.2cat > docker-compose.yml <<'EOF'services: pairdrop: image: ghcr.io/schlagmichdoch/pairdrop:v1.11.2 restart: unless-stopped ports: - 3000:3000EOFdocker compose up -dtimeout 120 bash -c 'until curl -fsS http://localhost:3000/ >/dev/null; do sleep 3; done'# → http://SERVER_IP:3000 — open it on two devices: they appear to each other. Behind a reverse proxy that sets X-Forwarded-For, only devices on the same network discover each other
PairDrop's deployment notes flag these before you expose it:
non-negotiableThe notes say you must run it behind a proxy that sets the X-Forwarded-For header; otherwise every client appears to come from the same address and all clients discover each other regardless of network. Their examples bind the container to 127.0.0.1 for that reason. Our snippet publishes port 3000 on all interfaces so you can try it, so put a proxy in front, or bind to 127.0.0.1, before real use.
non-negotiableSome browser features, including the copy button, installing it as a web app, persistent pairing, changing the display name and notifications, need the page to be served over HTTPS, and the notes recommend TLS anyway. Port 3000 serves plain HTTP.
non-negotiableTransfers between devices on different networks need a TURN server, which you host yourself (the notes point to coturn and a docker-compose-coturn.yml) or take from a public one such as OpenRelay; RTC_CONFIG points PairDrop at it. Without one, only direct peer-to-peer connections work, and WS_FALLBACK=true is the documented way to relay through the server when WebRTC is unavailable.
non-negotiableThe notes list the image on Docker Hub (linuxserver), GitHub Container Registry and a self-built option, and the examples use untagged images; we pin v1.11.2, a tag on ghcr.io. DEBUG_MODE logs peers' IP addresses, which the notes say never to enable in production.
PairDrop used 35 MB of RAM at idle on GCP e2-standard-2 · Ubuntu 26.04 LTS · Docker 29.9.3 (first boot, measured Nov 2026). We list a minimum of 64 MB.
Is the PairDrop install snippet verified?
The PairDrop install snippet is marked verified on Ubuntu 26.04 (Nov 2026).