How can we help?

ShareDrop is a peer-to-peer file transfer tool designed to move files directly between connected devices.

Open the Send page, select the files you want to share, and create a session. Share the generated link, code, or QR code with the receiver.

The receiver can open the shared link, scan the QR code, or enter the session code to join.

ShareDrop sessions are designed to work without requiring a traditional account-based file-sharing workflow.

Yes. Multiple receivers can connect to the same sender session. Each receiver has an independent peer-to-peer connection and transfer state.

Yes. A receiver can join an active session. Once its connection becomes ready, the shared files can be transferred to that receiver.

Yes. Multiple files can be selected for the same session. ShareDrop tracks both individual file progress and overall transfer progress.

Yes. Each receiver uses its own peer-to-peer connection, allowing transfers and progress to be tracked independently.

The disconnected receiver loses its active peer-to-peer connection. Other connected receivers can continue independently.

Yes. Every receiver has its own connection and transfer progress, so completion can happen at different times.

ShareDrop is designed around peer-to-peer transfer rather than permanent cloud file storage. The signaling layer helps establish the connection between participants.

The file transfer uses the secure communication mechanisms provided by the WebRTC connection.

ShareDrop is designed as a temporary transfer tool rather than a permanent cloud storage service.

No. Important files should still be backed up using a dedicated backup or storage solution.

Check that both devices have a working internet or local network connection, that the session is still active, and that the browser allows the required connection features.

Transfer speed depends on the network path, device performance, browser behavior, and the conditions of the peer-to-peer connection.

A connection interruption, browser restriction, or disconnected peer can stop a transfer. Check the browser console and reconnect the affected receiver when necessary.

The peer connection may be established while the data channel is still becoming ready. Waiting briefly or reconnecting the receiver can help identify whether the issue is connection-related.

Include whether you were sending or receiving, your browser and device, what happened, and any browser console error you saw.