Use TURN Servers?

In addition to true peer-to-peer connections, WebRTC supports a fallback to using a TURN server instead. This server acts as a proxy, connecting to both clients and forwarding the data that would otherwise be sent directly.

This app uses the public TURN servers hosted by PeerJS, another great library for doing WebRTC stuff! File data is generally still end-to-end encrypted by the browser.

Microphone permissions

WebRTC was originally designed to support peer-to-peer audio and video calls. For that reason, granting microphone permissions causes browsers to be less picky about the routes and IP addresses they expose to javascript, making it more likely to successfully establish a connection.

No actual audio is ever being recorded or sent to another computer or server, but the microphone will be activated for a few seconds while connecting.

Persistent File Ids

Enabling this checkbox will re-use the same file id for every subsequent upload. This means that the share link for all files will be the same, and can be for example be bookmarked.

Enabling this setting decreases security a bit, since it increases the time-frame a single link is valid. Of course, files can still only be downloaded while the sender also has that browser tab open.

Toggling this setting off and on will re-generate the ID.

Send in background

A page is considered to be invisible if another tab is focused, or the browser is minimized. Having another window (other than the browser) focused is usually fine.

Enabling this will allow you to send files to the same browser for example, or continue working while you share a file in the background.