WolfP2P browser and operating-system compatibility
For:Advanced users and digital professionals
Assumes familiarity with files, browsers, and common computer workflows.Find your current browser-on-a-computer setup below. WolfP2P also runs a live capability check because support can vary by browser version, operating system, browsing mode, and organization policy.
Compatibility at a glance
Live capability checks remain authoritative for the browser currently in use.
| Current browser examples | What you can transfer | |
|---|---|---|
| Compatible Browsers | Chrome, Edge, Brave, and other Chromium-based browsers on computers when WolfP2P's live check confirms the required capabilities | Individual files, complete folders, very large files, preserved folder structure, and disk-backed recovery |
| Partially Compatible Browsers | Safari and Firefox, when the live check confirms WebRTC support | Can send individually selected files. Receiving requires destination-folder access, which these browsers do not provide through WolfP2P's current receiver implementation. |
If the live check reports a limitation, follow the result shown for the browser currently in use rather than relying on this general list.
Compatible Browsers
A Compatible Browser provides the folder selection, destination-folder access, direct disk writing, and related capabilities needed for the complete WolfP2P experience. Current Chrome, Edge, and Brave are the recommended examples. Opera, Vivaldi, and other browsers built on the open-source Chromium project belong in this category only when WolfP2P's live check confirms those capabilities.
Partially Compatible Browsers
A Partially Compatible Browser can send individually selected files when the live checks permit it. Receiving in WolfP2P requires a writable destination folder. The current receiver has no memory-buffer or browser-download fallback; use a browser with the required directory access to receive files.
Without writable destination-folder access, this browser cannot receive a transfer or provide destination-based recovery in the current Product. The category describes current WolfP2P functionality, not the browser's general quality or security.
Choose a browser for the transfer you need
| Recommended browser setup | Important limitation | |
|---|---|---|
| Send one or more individual files | Compatible or Partially Compatible Browser | A Partially Compatible Browser cannot reliably resume the sending side after a reload |
| Receive ordinary individual files | Compatible Browser | Receiving requires access to a destination folder |
| Send a complete folder | Compatible Browser | A Partially Compatible Browser can send only individually selected files |
| Preserve a folder structure at the destination | Compatible Browser on the receiving computer | Receiving requires access to a destination folder |
| Receive very large files or collections | Compatible Browser on the receiving computer | The destination must have enough free space; there is no memory-download fallback |
| Resume part of a large file in Safe mode | Compatible Browser with destination-folder access | Receiving and checkpoint recovery both require writable destination-folder access |
Browser support can change as browser vendors add or remove capabilities. The messages shown by WolfP2P for the current browser are therefore more authoritative than a permanent browser-version table.
The recommended setup
For the complete WolfP2P experience, use a Compatible Browser—for example, an up-to-date Chrome, Edge, or Brave—at both ends. This setup supports choosing a complete source folder, selecting a destination folder, preserving relative paths, skipping matching destination files, and using disk-backed recovery.
The receiver's browser must let WolfP2P write directly into a chosen destination folder. Without that capability, the receiver cannot accept the transfer.
Before starting a large transfer:
- Confirm that the sender can choose the complete source folder.
- Confirm that the receiver can choose a destination folder. If Documents is refused with a system-files message, create and select a subfolder inside it; see folder permissions.
- Check that the destination has enough free disk space.
- Keep both computers awake and both tabs open.
- Avoid private browsing when it prevents WolfP2P from retaining the file permissions needed for recovery.
Understand browser capability messages
These messages report a missing or limited browser capability—not necessarily a fault in WolfP2P, your files, or your operating system. Each explanation states what the browser cannot provide, which WolfP2P feature that affects, and what you can do next. The message shown by WolfP2P's live check is authoritative for the browser currently in use. These exact anchors are also the destinations used by the application's **More info** links.
Why can't this browser select folders? NO_FOLDER_PICKER
Capability message: “This browser cannot select folders.”
You can choose individual files instead. If you need to send a complete folder with its nested structure, open WolfP2P in a Compatible Browser, such as current Chrome, Edge, or Brave.
Selecting several individual files is not the same as selecting a folder because the browser does not provide their complete relative folder paths.
What does limited file handling mean? LIMITED_BROWSER_FILE_HANDLING
Capability message: “File handling is limited in this Partially Compatible Browser.”
This browser cannot let WolfP2P save directly into a folder you choose. It can send individually selected files, but the current receiver cannot accept files without destination-folder access.
There is no memory-buffer or browser-download receiving fallback, and no 2 GB fallback allowance.
Open WolfP2P in a Compatible Browser, such as Chrome or Edge, and arrange a new tunnel with the sender. An occupied seat is not automatically transferred to a different browser.
Why can't this browser make a direct connection? NO_WEBRTC
Capability message: “This browser cannot make a direct connection.”
WolfP2P needs browser support for WebRTC data channels to move files directly between the two computers. If that capability is unavailable, the transfer cannot run in this browser; there is no upload-based fallback.
Update the browser or open WolfP2P in a current version of Chrome, Edge, Brave, Firefox, or Safari, then try again. WolfP2P does not upload the files to its server as an alternative.
Why does WolfP2P require a secure connection? SECURE_CONTEXT_REQUIRED
Capability message: “Required browser security features are unavailable.”
Open WolfP2P through its official HTTPS address. Required browser security features are unavailable when the page is loaded over an insecure connection or in an environment that does not provide a secure browser context.
Operating-system filename and path differences
Windows, macOS, and their filesystems do not accept exactly the same filename and path forms. A name that works on the sending computer may therefore be invalid at the destination.
WolfP2P checks incoming paths before creating destination files and rejects unsafe or unsupported forms. It does not silently rename them because that could create duplicate names or make the received structure differ from the source.
If a path is rejected, rename the affected source file or folder to a simple, portable name and offer the set again. When WolfP2P displays TRANSFER_DESTINATION_PATH_INVALID, use the current path-error explanation.
Sleep and background execution
Your browser may help keep the screen awake during a transfer, but no browser can continue transferring while the computer is fully suspended. Closing a laptop lid, manually putting the computer to sleep, or some system power settings can still interrupt the connection.
Keep both computers awake and both tabs available until the transfer completes. See what happens when a computer sleeps for prevention and recovery guidance.
Operating-system scope
WolfP2P runs in the browser rather than through a native Windows or macOS application. Files can move between Windows and macOS when the browsers at both ends provide the capabilities required for that transfer.
Cross-platform transfer does not make every filename portable. It also does not override operating-system permissions, free-space limits, security software, or organization-managed browser policies. See Transferring Folders Between Mac and Windows for practical preparation.
Phones, tablets, and unverified platforms
The current release offers the transfer panel on computers. When WolfP2P identifies a phone or tablet, it asks you to open the same link on a computer. Public information pages remain available.
On a computer, live capability checks still determine which file operations are available. Keep the original files until the receiver has confirmed completion.
Related help
Browser permissions
Restore access when the browser blocks or forgets a selected file or folder permission.
File and destination errors
Follow the exact explanation for an invalid path, unavailable destination, or disk failure.
Sleep interruptions
Understand what happens when either computer suspends during a live transfer.
Transfer recovery
Review durable checkpoints, verified reuse, and the limits of restoration.