Share a complete folder directly
For:All users
No technical knowledge required.A complete folder can contain thousands of files and nested subfolders that need to arrive in the same arrangement. Selecting items individually risks omissions. Creating a ZIP adds packaging time, temporary disk use, and an archive the receiver must unpack before using the files. WolfP2P streams the folder's files between browsers and preserves supported relative paths, so “share” describes the human outcome rather than a hosted link.
Why WolfP2P fits
A Compatible Browser preserves the folder's nested paths without requiring a ZIP archive. There is no transfer application or network share to configure.
The folder travels over an encrypted direct transfer channel, and Safe mode can retain recoverable destination progress for a large file within the set.
Folder transfer is especially useful when the arrangement carries meaning: a website with asset directories, an album organized by year, or a project whose files refer to neighboring folders. WolfP2P preserves supported relative paths; it does not reproduce every filesystem permission, timestamp, link, or platform-specific attribute.
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. Complete folder preservation and disk-backed large-file handling require a Compatible Browser, such as current Chrome, Edge, or Brave, with the required capabilities confirmed by WolfP2P's live check. 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 folder
Check the folder boundary
Open the folder and confirm that it contains everything the receiver needs—and nothing you did not intend to send. Resolve unsafe names or links to material outside the folder.
Select the folder as one source
Create a tunnel in a compatible browser and choose the complete folder instead of selecting its files individually or building a ZIP archive.
Connect the folder's recipient
Privately share the tunnel link or six-character code and confirm that the intended browser has joined.
Choose where the tree will be recreated
The receiver reviews the offered paths and total size, selects a destination folder with enough space, and accepts.
If the browser refuses Documents or reports system files, create a subfolder inside Documents and select that instead. See folder permissions.
Transfer and inspect the structure
Keep both computers online, recover verified progress if interrupted, and check nested folders and representative files at the destination.
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.
WolfP2P preserves file bytes and supported relative paths, but not the source file's modification date and time. A transferred file receives the current date and time when it is written at the destination.
Questions and answers
Does the receiver get the original folder structure?
Compatible Browsers, such as Chrome, Edge, or Brave preserve nested relative paths inside the destination folder selected by the receiver.
Must the folder be compressed first?
No. WolfP2P enumerates and transfers the selected files without first building a ZIP archive. Compare direct folder transfer with ZIP packaging when portability, compression, or keeping one archive matters.
What happens to files already at the destination?
WolfP2P uses relative path and byte size to locate a destination candidate, then requires SHA-256 content evidence before skipping the completed file. This is verified one-way reuse, not continuous synchronization.
Can any browser receive a large folder safely?
The complete folder experience requires compatible browser capabilities. Receiving requires writable destination-folder access. A browser without that capability cannot receive through the current Product. Check compatibility first.