WolfP2PLarge file transfer versus email attachments
For:All users
No technical knowledge required.WolfP2P streams a large file directly between two browsers without placing an intermediary copy in email or hosted-file infrastructure. The receiver gets bytes while the sender is sending, WolfP2P imposes no email attachment limit, the selected file bytes remain unchanged, and compatible browsers can provide recoverable progress for a long transfer. Email remains convenient when a small file fits the provider's rules and the recipient needs to open it later.
The current connection configuration uses host candidates only, with no STUN traversal between separate private networks and no TURN relay. A shared or otherwise directly reachable network can work, subject to browser and network policy; remote reachability is not guaranteed.
Live large-file delivery or inbox delivery
| WolfP2P | Email attachment | |
|---|---|---|
| Is there an intermediary file copy? | WolfP2P's server does not receive, store, or relay the file bytes | The attachment is stored by mail infrastructure, or by a file-hosting service when the provider substitutes a sharing link |
| How does delivery begin? | The receiver gets bytes directly as the sender transmits them | The sender first uploads the attachment or hosted copy through the provider |
| Same-network path | File traffic can stay on local Wi-Fi or Ethernet when the browsers establish a local connection | The attachment follows the provider's mail or hosted-file path |
| Does it suit very large files? | Designed for large-file transfer, subject to browser, disk, and network limits | Attachment limits vary by provider |
| Can interrupted large-file progress be recovered? | Safe mode can resume from durable checkpoints on compatible browsers | Provider behavior varies |
| Are media files transformed? | No | Images may be resized unless the sender opts out or selects original/full size; files attached explicitly as files are generally preserved |
| Is the file path direct and encrypted? | Yes, through the WebRTC data channel | No direct peer channel; protection depends on the mail providers and delivery path |
| Must both people be online together? | Yes | No |
| Does it create a message record? | No | Yes |
Which approach fits?
the attachment exceeds the provider's limit; you do not want another stored copy held by mail or file-hosting infrastructure; a large media file should arrive at original quality; or recoverable progress matters for a long transfer.
The recipient needs to collect the file later. A written message record matters. The attachment is small and fits the provider's rules.
Create a tunnel and email or message its invitation to the receiver. Only the invitation travels through that service—not the large file or an intermediary copy of it.
Important trade-off
WolfP2P requires both people online while the bytes move. Its encrypted direct transfer channel and no-intermediary-copy design solve a different problem from email's asynchronous delivery.
See Send a File Too Large for Email for the complete workflow.