Browser folder permissions

WolfP2P asks the browser for access only when a person chooses a source or destination. The browser—not WolfP2P—shows and enforces the permission 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.

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.

The receiver chooses where accepted files are written. WolfP2P needs write access to create the destination files, preserve supported nested paths, compare existing files, and save durable checkpoints.

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.

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 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.

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.

Permission allows the local browser tab to read or write the selected files. It does not grant the WolfP2P coordination server access to those file contents. During normal transfers, file bytes move over the direct WebRTC data channel between the two browser peers.