WolfP2PSend the complete working project
For:Advanced users and digital professionals
Assumes familiarity with files, browsers, and common computer workflows.A video edit, photo shoot, design package, or audio production often combines large source media with many smaller project, proxy, preset, and reference files. Moving only the obvious media can leave the project incomplete; flattening the folders can break relative references. Cloud staging also creates another hosted copy of unreleased or client-owned work. WolfP2P streams the complete selected project between browsers while preserving supported relative paths and the original file bytes.
Why WolfP2P fits
For a deliberate handoff of the complete working folder, a Compatible Browser preserves nested assets and relative paths without requiring a ZIP archive. Source video, photography, and audio retain their original file quality.
Unreleased work and protected intellectual property travel over an encrypted direct transfer channel. The no-intermediary-copy design avoids leaving another stored copy with a cloud or file-sharing provider.
Photography projects. Keep RAW files, sidecars, selections, exports, and shoot folders together. WolfP2P delivers the working set; it is not a hosted proofing gallery and does not add review or client-approval features.
Video and editing projects. Move footage, proxies, project files, linked assets, graphics, and exports in one preserved structure. Confirm that machine-specific paths and application relinking rules remain portable.
Design projects. Include source documents, linked images, packaged assets, fonts you are permitted to share, and final deliverables. A transferred font or asset is not automatically installed or relinked.
Audio projects. Keep session files, recorded media, stems, masters, and permitted presets together. The receiving system still needs compatible applications, plug-ins, codecs, and versions.
Course and webinar projects. Move source recordings, slides, editing projects, captions, supporting files, and published outputs without treating delivery as collaborative editing or publishing.
Before sending, collect assets that live outside the main project folder, remove caches or previews that can be regenerated when that meaningfully reduces the transfer, and confirm that you may share licensed fonts, stock media, plug-ins, presets, and customer material. WolfP2P preserves the selected files; it cannot determine whether the project is complete or properly licensed.
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 transfer the project
Package the working set
Collect source media, project documents, linked assets, fonts and presets you may share, and any handoff notes. Remove regenerable caches when doing so will not break the project.
Check portability
Look for absolute paths, missing assets, application versions, plug-ins, codecs, and licenses that the receiving workstation will need.
Select the project root
Create a tunnel and choose the highest-level folder that contains the complete intended working structure.
Let the receiver review the handoff
Privately share the invitation. The receiver checks the offered paths and size, chooses a destination 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 open the project
Keep both computers active, recover verified progress if necessary, then open the project at the destination and resolve any application-specific relinking.
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 WolfP2P change the source media?
No. WolfP2P transfers the selected bytes without compressing, resizing, transcoding, or normalizing the media.
Are project folders preserved?
Compatible Browsers, such as Chrome, Edge, or Brave preserve nested relative paths when a folder is selected and written to a destination folder. Source filesystem modification dates are not preserved. Use a filesystem-aware copy or archive workflow when a project depends on original timestamps or other filesystem metadata. For a folder without application-specific dependencies, use the shorter complete-folder workflow.
Will the project open automatically on the other computer?
No. WolfP2P moves files; it does not install fonts, plug-ins, codecs, applications, or relink assets that use machine-specific absolute paths.
Can an interrupted large source file continue?
Safe mode supports durable checkpoint recovery on compatible browsers. Keep both tabs open and choose the same destination when resuming.