Async, not real-time
PairDrop alternative.
PairDrop is best when both browsers are open and you want a peer-to-peer transfer. quik.space is the alternative when you want async: drop, send the link, the recipient grabs it later.
FAQ
What's the difference between PairDrop and Snapdrop?
PairDrop is a fork of Snapdrop that adds public rooms (a shared code lets two devices on different networks pair without IPs in common) and a polished UI. Mechanically it's still WebRTC peer-to-peer, so both sender and receiver have to be in their browser at the same time.
Are there PairDrop alternatives for Windows specifically?
PairDrop itself works in any browser on Windows. The 'alternative' question usually means 'something I can use when the other person isn't online yet'. quik.space handles that case: drop the file, send the link, the recipient grabs it whenever. No simultaneous-presence requirement.
When is PairDrop better than quik.space?
When you want a fully peer-to-peer transfer that doesn't go through a server. PairDrop sends bytes directly browser-to-browser via WebRTC; nothing transits a server other than the signaling channel. If trustlessness is the priority, PairDrop wins. quik.space transits through Supabase Storage on the way to the recipient.
When is quik.space better than PairDrop?
When async matters. The sender finishes, closes the tab, walks away. The recipient gets the link later — minutes, hours, or up to 72 hours by default. PairDrop requires both browsers open at the same time.
Can I do PairDrop-style room codes on quik.space?
Loosely yes — passcode-protected uploads give you a 10-character code that the recipient types at /unlock to grab the file. The mechanic is the same shape as PairDrop rooms, just async.