Does TunnelTransfer upload my files to a server?

The web transfer is designed for P2P delivery. The file is sent directly to the receiver and this site does not use cloud storage for file contents. PeerJS signaling only helps devices find each other; contents are encrypted before transfer.

Do both devices need to stay online?

Yes. In the web version, sender and receiver pages must remain open until the transfer finishes. The extension is more resilient because it can continue transfer work in its background/offscreen context.

Can I send multiple files?

Yes. If you select more than one file, the browser packages them into a standard ZIP and sends that ZIP as one encrypted transfer. The first implementation stores files in the ZIP without compression, which is fast and dependable for every file type.

Why can Brave, Firefox, or mobile browsers behave differently?

WebRTC depends on browser privacy and network settings. Brave Shields, WebRTC IP policies, enterprise firewalls, or strict UDP blocking can prevent direct connections. Adjusting site shields or WebRTC policy may be required.

How sensitive is the share code?

The code contains both the peer ID and the encryption key. Anyone with the complete code can connect and decrypt the file during the transfer. Treat it like a temporary password.

Is there a file size limit?

The practical limit is set by browser memory, device performance, and network stability. For very large transfers, keep both devices awake and use a stable network.