PrivyDrop

PrivyDrop is a free, open-source peer-to-peer (P2P) tool for transferring files, images, folders, and clipboard text between devices.

  • Cloud
  • Network Services
PrivyDrop is a free, open-source peer-to-peer (P2P) tool for transferring files, images, folders, and clipboard text between devices. It links browsers directly over an end-to-end encrypted WebRTC connection with no server-side data relay, supports resumable transfers, and requires no registration, file-size, or speed limits, making it a quick, privacy-friendly way to share data without a cloud service.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

56/100 Fair

Maintained
86last commit 15 days ago
Popular
44149 GitHub stars
Easy to install
251 install platform, install notes
Light to run
85512 MB minimum RAM
Security check
201 serious finding, 8 minor, CI, tests

Availability: platform listings confirmed today

GitHub stars
149
Open issues
0
Last commit
2026-11-06
Latest release
v1.3.0
License
MIT
Activity
steady

Checked 2 days ago - source: GitHub (david-bai00/PrivyDrop)

Resources & Compatibility

Minimum requirements: 512 MB RAM, 1 CPU core(s), 2 GB disk.

Checked 2 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Use an explicit --mode with deploy.sh Always pass a --mode value to deploy.sh, such as --mode lan-http for home network use or --mode public for internet access. This matters because the mode controls how the app is configured; if you skip it or choose the wrong one, PrivyDrop may not be reachable the way you expect. source
  • Free default ports 3001 and 3002 PrivyDrop's backend starts on port 3001 and the frontend on port 3002 by default. If those ports are already in use, stop the other app or make it use another port, because the affected part will not start while that port is taken. source
  • Add 1GB of swap on 1-2GB servers On a fresh Ubuntu server with only 1GB-2GB of RAM, add 1GB of swap before the first Docker build (the one-time step that prepares the app), then rerun the deploy if it failed. Swap gives the system extra room on disk when memory runs out, which can stop that preparation step from crashing. source

Fetched 2 days ago - each note links to its source

Alternatives (6)

  • AirDrop - With AirDrop, you can wirelessly send documents, photos, videos, websites, map locations, and more to a nearby iPhone, iPad, iPod touch, or…
  • Metastream - Metastream allows you to watch internet videos with friends.
  • My-folder-online
  • Safefiles
  • filedrop - Filedrop is a tiny and cute app for sharing stuff via wifi.
  • snapdrop - Snapdrop is a self-hosted web app that lets you share files between devices on the same local network directly from the browser, inspired b…

Checked 2 days ago - source: AlternativeTo

Common questions

Which ports does PrivyDrop use by default?

The backend starts on port 3001 and the frontend on port 3002. If either port is already in use, stop the other app or change the port, because the affected part will not start while the port is taken.

How do I enable resumable transfers for large files?

Set the browser save directory so Chrome can stream files directly to disk. If a transfer is interrupted, refresh both the sender and receiver pages to restart it.

Why might the first Docker build fail on a low-memory server?

On a fresh Ubuntu server with only 1GB-2GB of RAM, add 1GB of swap before the first Docker build. If the build failed, rerun the deploy after adding swap.

Can multiple people receive the same file at once?

Yes, a single room can have multiple receivers downloading files or text simultaneously. New recipients can join without disrupting ongoing transfers.

Answers sourced from github.com, github.com, github.com

Community

Collected 2 days ago - public community threads