ADrop field guide
Understand browser-to-browser file transfer
These guides explain the engineering decisions behind ADrop and turn common failures into checks you can perform. They are maintained alongside the application, based on its actual WebRTC, signaling, storage, and recovery paths—not generic file-sharing advice.
How a browser transfer works
Follow a file from device discovery through signaling, DTLS, chunking, flow control, and saving.
Diagnose a failed connection
Separate discovery, signaling, peer-connection, and storage failures with a practical decision tree.
Plan a large-file transfer
Understand browser memory, direct disk writes, mobile suspension, free space, and interrupted transfers.
Security and privacy model
See exactly what the signaling server learns, what encryption protects, and what risks remain.
Why these guides exist
“Peer to peer” is a useful label, but it does not tell you whether a transfer uses a relay, what happens when the tab sleeps, or where an incoming multi-gigabyte file waits before download. Those details decide whether a tool is suitable for a particular file and network. ADrop documents its behavior so that users can make that decision before selecting a file.
Every guide distinguishes an application choice from a browser or network constraint. For example, ADrop chooses not to configure a TURN relay, while a corporate firewall chooses whether a direct path is possible. A browser chooses whether it exposes a direct file writer. Keeping those boundaries clear makes troubleshooting faster and privacy claims testable.
Need the short version? Use the ADrop help page. Use these guides when you want to understand why a transfer behaves a certain way.