WolfP2PShare a sensitive file privately
For:All users
No technical knowledge required.A personal record, signed agreement, customer document, private photograph, unpublished design, or project containing protected intellectual property may be small enough for email or messaging but too sensitive to leave with another storage provider unnecessarily. You need to deliver it to one known person while limiting where additional copies are created. WolfP2P streams the accepted file bytes between the two browser peers without creating a hosted middle copy, while still requiring you to verify the recipient and trust both endpoints.
Why WolfP2P fits
WolfP2P sends the selected file over a browser-provided encrypted peer-to-peer connection. Its coordination server helps the browsers connect but does not receive, read, store, or relay the file bytes.
That avoids an intermediary file copy on WolfP2P's server and reduces the number of services entrusted with the file. The invitation can travel through a private message or another trusted channel without attaching or uploading the sensitive file itself. There is also no transfer application to install or account to create.
The first browser that successfully joins takes the tunnel's open peer role. Once both roles are occupied, additional attempts to use the invitation are refused, so another party cannot join the live tunnel and receive the offered file. An interrupted participating browser can reclaim its reserved role during supported recovery.
“Private” does not mean consequence-free or anonymous. Send only files you are authorized to transfer, confirm the person at the other end, and use an organization-approved system instead when policy requires identity assurance, revocation, audit evidence, data-loss prevention, or controlled retention.
Before you start
The browsers need a direct network path. The current configuration gathers host candidates only, with no STUN traversal between separate private networks and no TURN file relay. Even a shared network can block the connection. Both peers must remain online while file bytes are moving. Keep both transfer tabs open until completion. Confirm that the receiver can write to the chosen destination and has enough free space for the transfer mode.
How to share the sensitive file
Confirm authority and the intended person
Make sure you are permitted to send the file, then contact the receiver through a separate channel you already trust.
Minimize invitation exposure
Wait until the receiver is ready before creating the tunnel, then privately share its link or six-character code and ask them to join promptly.
Verify who joined
Confirm through the trusted channel that the intended person occupies the receiving role. Do not rely on possession of the invitation alone as proof of identity.
Offer only after confirmation
Select the sensitive file after verifying the receiver. Ask them to review the offered count and total size, choose the intended destination, and accept.
If the browser refuses Documents or reports system files, create a subfolder inside Documents and select that instead. See folder permissions.
Complete and account for the file
Keep both tabs active until delivery completes, then follow any endpoint protection, retention, deletion, or service-record obligations that apply after transfer.
For the complete sequence, see How WolfP2P Works. For the coordination boundary, see What WolfP2P's Server Sees.
One browser tab represents one tunnel. Reloading or browser-restoring the same tab can resume its session, but genuinely closing the tab ends that session.
A restrictive network may prevent a direct WebRTC connection. WolfP2P does not fall back to relaying file bytes through its server.
The coordination server relays WebRTC connection details and is not a zero-trust component. The current product does not provide out-of-band fingerprint verification.
WolfP2P does not independently verify the receiver's real-world identity. Anyone who obtains a valid invitation before the intended receiver joins may attempt to use it, so share it privately and create a new tunnel if it may have been exposed.
Transport encryption does not protect a file after either endpoint opens or stores it. WolfP2P cannot prevent the receiver from retaining, copying, or redistributing the delivered file, and it does not scan files for malware or enforce access policy, audit records, data-loss prevention, or regulated retention. Use an organization-approved managed system when those controls are required.
Questions and answers
Can WolfP2P read the sensitive file?
WolfP2P's coordination server does not receive the file-data channel, so it cannot read the transferred file contents. The sender's and receiver's browsers necessarily process the readable bytes at their endpoints.
Is the connection encrypted by WolfP2P?
The browsers provide the encryption. Their standardized WebRTC implementations establish and operate the DTLS-protected data channel; WolfP2P uses that channel rather than supplying a proprietary encryption protocol. Read Encrypted Transfer for the standards and boundaries.
Does private transfer prove who received the file?
WolfP2P refuses additional newcomers after the first receiving peer successfully joins using the invitation link or tunnel code. However, WolfP2P does not currently provide accounts, verified identities, or an independent fingerprint comparison. The first successful joiner could be someone who obtained the invitation without authorization, so confirm the intended person separately before offering the file.
Can someone reuse the invitation after the receiver joins?
Not to enter the occupied live tunnel. Once both peer roles are held, additional join attempts are refused. A participating browser may reclaim its own reserved role after an interruption; that recovery does not give a third party another place in the tunnel.
Does WolfP2P keep a copy for later download?
No. Both computers must be online simultaneously because WolfP2P does not hold the file for later delivery. Use a managed or hosted service when delayed download, revocable access, or an audit trail is more important than avoiding intermediary storage. Compare direct transfer with a hosted sharing link for that decision.