English
PairDrop Hosting
Send files and text between devices on your network straight from the browser, no accounts.
No setup fees-
One click deploy -
1 GB RAM Memory needed -
15 GB Disk Space Needed -
From 2 € Price
Tech
- Docker image
- lscr.io/linuxserver/pairdrop:latest
- Default port
- 3000
How PairDrop works
PairDrop lets browsers discover compatible peers on the same network and can connect remote devices through temporary public rooms or saved device pairing. After a recipient accepts a transfer, WebRTC carries file or text data directly between peers where the network path permits. The hosted server coordinates discovery and signalling rather than acting as a long-term document repository.
When direct connectivity is blocked by NAT, firewalls, or restrictive networks, a configured TURN service can relay WebRTC traffic. The availability and privacy characteristics of that relay depend on the deployment. Devices must remain online during transfer, and the recipient should verify the displayed peer identity before accepting sensitive files.
Key PairDrop features
PairDrop works from a modern browser and can exchange several files, directories where supported, text, and clipboard-style messages. Local-network discovery reduces setup for nearby devices, while rooms and pairing help reconnect systems that are not on the same network. Browser support, background restrictions, file-system permissions, and network policy can affect the experience.
The application is for immediate transfer, not synchronisation, shared folders, version history, archival storage, or delayed download links. Although the catalogue mapping marks PairDrop as storage-driven and therefore supplies larger-plan guidance, ordinary peer payloads are not meant to become a persistent server-side library. Network traffic and relay behaviour are the more important operational limits.
Who uses PairDrop
People move a photo from a phone to a laptop, technicians exchange logs during a support call, classrooms distribute files between nearby devices, and small teams share temporary material without creating accounts in a cloud drive. Rooms help when participants are on separate networks.
PairDrop is less suitable for regulated document exchange, unattended delivery, durable collaboration, or workflows that need audit trails, access expiry, antivirus review, link management, and central retention. Those cases call for a controlled file platform rather than an ad hoc peer transfer page.
Self-hosting PairDrop: requirements and cost
PairDrop is driven mainly by concurrent peers, signalling activity, transfer volume, browser behaviour, and any relay traffic required when a direct WebRTC route cannot be created. The catalogue records PostgreSQL and MariaDB as Not required. The service does not use a relational database for a permanent user file archive. PairDrop is marked storage-driven in the plan mapping, so 50 GB on Plan 3 is a realistic starting point and 100 GB on Plan 4 provides more room for a large working set.
On AvaHost, PairDrop uses Plan 1 at €2. The hosted PairDrop package includes one-click deployment, a custom domain with automated HTTPS, automatic application updates, and scheduled backups. The hosted package provides the PairDrop web and signalling service, not a permanent file library, content scanning, delivery audit, managed TURN guarantee, or recipient verification. A custom HTTPS domain protects browser sessions, while users remain responsible for confirming the intended peer and for the sensitivity and legality of transferred content.
F.A.Q
PairDrop starts at €2 on Plan 1. Signalling is lightweight, while transfer traffic, simultaneous peers, and any relayed WebRTC sessions are the main operational drivers. The entry plan suits modest ad hoc sharing. Monitor network use and browser behaviour as more people join rooms or exchange large files at the same time.
The approved mapping marks PairDrop as storage-driven, so Plan 3 offers 50 GB and Plan 4 offers 100 GB guidance. PairDrop itself is intended for immediate peer transfers rather than a permanent server file library. Choose a larger plan only after considering actual package storage, logs, updates, and operational requirements alongside transfer traffic.
Temporary rooms and paired devices can help remote browsers discover each other. WebRTC then attempts a direct connection; restrictive NAT or firewall conditions may require TURN relay support. Both devices must be online, browser and network policy must permit the transfer, and AvaHost does not promise that every network combination can establish a route.
Automated HTTPS protects the connection to the hosted PairDrop interface, but it does not prove that a discovered browser belongs to the intended person. Confirm the displayed peer, room context, and transfer prompt before accepting sensitive content. The service does not add identity verification, malware review, a delivery audit, or permanent access records.