Browser folder permissions
For:All users
No technical knowledge required.WolfP2P requests file access through an action you take, such as choosing a source or destination, granting access to a saved location, or resuming a saved session. The browser controls whether a permission prompt is needed and can be shown. Access already granted may be used without another prompt.
This page helps resolve a dismissed, denied, or blocked prompt. For a plain-language explanation of what the warning permits and what remains inaccessible, read Why WolfP2P Asks for File and Folder Access.
Permissions for the sender
The sender chooses the files or folder to offer. WolfP2P needs read access to enumerate the selection and read file bytes while the transfer is active.
On a browser with persistent file handles, retaining access also allows WolfP2P to find the same source after a supported reload. If the browser falls back to an ordinary file input, the current transfer can still send the selected file, but the browser cannot promise that the same source selection will remain available after reload.
Permissions for the receiver
The receiver chooses where to save the files. Browser permission lets WolfP2P save them there, keep supported subfolders, check existing files, and record progress that can be reused.
The receiver should choose the intended destination carefully. Granting access to one selected folder does not give WolfP2P unrestricted access to the rest of the computer.
Why permission may be requested again
A browser may require another permission decision after a reload, browser restart, restored session, changed browser setting, or earlier denial. WolfP2P cannot bypass that decision.
For resume, grant access to the same source or destination associated with the interrupted transfer. Choosing a different destination means WolfP2P evaluates what already exists in that different folder.
If no chooser or permission dialog appears
Browsers embedded inside another application may expose file-access features without providing a working chooser or permission dialog. WolfP2P's capability check detects whether the interface is present; it cannot guarantee that the host application will display its dialogs. A missing dialog alone does not prove failure: permission may already be granted. Check whether the requested selection or access actually completed.
If access remains unavailable, try the action in a supported standalone browser. This applies to selecting source files or folders, granting destination write access, and renewing access to saved locations after reload or during resume. A successful source selection does not establish that destination write permission can also be granted.
Saved sessions, locations, and permissions belong to the browser profile that stored them. Opening WolfP2P in another browser may require a new tunnel and selecting the source and destination again. Preserve existing destination files and follow the transfer's verification and conflict decisions; switching browsers does not itself resume the old session.
Do not disable security protections to force a dialog to appear.
If access is denied or removed
- If the picker was closed without a selection, open it again and choose the intended file or folder.
- If destination permission was revoked, grant it again when prompted or choose another destination.
- If resume permission is denied, WolfP2P cannot continue writing to the saved destination.
- If the browser cannot provide folder access at all, review the browser compatibility limitations.
Do not change browser security settings merely to suppress a prompt you do not understand. Confirm which folder WolfP2P is requesting and whether you are sending or receiving.
If the browser refuses a protected folder
Your browser may refuse a folder with a message about system files or a protected location—even when you choose Documents (sometimes called My Documents). The restriction can apply to the whole folder, not just its contents. Create a subfolder such as Documents/WolfP2P Transfers and select that instead. If it is still refused, choose another ordinary folder you control. WolfP2P cannot override the browser's rules; do not change system files or weaken security settings to continue.
The File System Access specification lets browsers restrict sensitive locations. Chromium's folder-access rules distinguish selecting an entire Documents folder from selecting an otherwise-permitted subfolder. The exact restrictions vary by browser and platform. This can affect source selection as well as the receiving destination; the browser may close the picker without returning a distinct WolfP2P error.
Recover file or folder permission
Identify the requested access
Confirm whether WolfP2P needs to read a sender source or write to a receiver destination.
Reopen the picker from WolfP2P
Use the action shown in the current transfer rather than changing broad browser or operating-system permissions.
Choose the intended location
For recovery, select the same ordinary user-controlled location when it remains available. Choosing a different destination makes WolfP2P evaluate what exists there instead.
Confirm the resulting state
Return to the transfer and follow the next action shown. If the browser refuses the location again, choose a different non-system folder.
Permission does not mean server upload
Permission lets this browser tab read or save the selected files. It does not give the WolfP2P server access to their contents. Files travel directly browser-to-browser.
Related guidance
Error-specific help
Use the file, folder, and disk reference when WolfP2P displays a specific filesystem error.
Browser capabilities
Check whether the current browser supports folders, direct destination writing, and durable permissions.
Transfer recovery
Understand the difference between retrying permission and resuming verified transfer progress.