Reach for P2P only when the job is embarrassingly small
A common mistake we see is treating every transfer like it needs infrastructure. Ask one question: will anyone need this file a week from now in a shared folder? If yes, use your org's approved drive. If no, keep reading.
- Good fit: one deck, one recording, one export—receiver is standing next to you with a QR code or short code.
- Poor fit: archival, compliance review, or “I might need this link later”—that wants retention and audit trails, not a transient tab.
- Gray area: sensitive but tiny—only you know your policy; when in doubt, ask IT instead of guessing.
Conference Wi‑Fi to hotel laptop: the transfer that actually worked
In practice, this is the story people tell when Device File Share earns its tab slot—your details will vary, but the beats repeat.
- You grab slides from your phone after the venue blocks USB. AirDrop is not an option across OS families, and you do not want to log personal Drive on the borrowed machine.
- You open Device File Share on both ends, read the pairing code out loud once, and send the PDF before the AV team changes rooms.
- Receiver opens the file locally to confirm pages render—especially if the deck embeds fonts—then you close the tab so the channel is gone.
- If the network fights you, you abort to USB sneakernet or the host's official upload—no shame; P2P was never a magic wand.
When peer-to-peer beats the shared drive
Cloud drives are great for retention, versioning, and sharing with a link. They are the wrong tool when you just need a single artifact to land on another device once, especially if that device is not logged into the same ecosystem. Device File Share optimizes for that narrow case: pair, send, verify, close.
What actually happens in the tab
WebRTC negotiates a path between browsers. That usually means STUN/TURN-style signaling so two NATs can find each other. The important mental model: you are granting a live channel, not filing something into long-term storage on purpose. Keep receivers ready before you start a large transfer, and open the file once if integrity matters.
Threat model in sixty seconds
Anyone who can read your screen or shoulder-surf the pairing code can intercept the workflow. Malicious Wi‑Fi still matters for any web session. Do not use P2P browser transfer for regulated health or financial payloads unless your security team signs off. For everything else, it is a pragmatic escape hatch—faster than hunting for cables, smaller footprint than spinning up shared drives.
Before you send: shrink or convert
Heavy attachments behave better after a pass through Image Tools or PDF Tools. Structured exports often route through File & Data Converters.