Frequently Asked Questions

Answers to common questions about ShareWave and browser-to-browser file sharing.

What is ShareWave?

ShareWave is a browser-based file sharing service that allows users to transfer files directly between connected devices. No account or cloud storage is required.

Are my files uploaded to ShareWave?

ShareWave is designed for direct browser-to-browser file transfer. Files are not intentionally stored on ShareWave's central server as part of the normal transfer process.

Does ShareWave have cloud storage?

No. ShareWave does not provide cloud storage for the files you transfer. Files are transferred between the connected devices.

Why does ShareWave sometimes use a TURN server?

WebRTC normally attempts to establish a direct connection between the two devices. If a direct connection cannot be established because of network restrictions, firewalls, NAT, or other network conditions, a TURN relay may be used to help establish the connection.

Does using a TURN server mean my files are stored there?

No. A TURN server acts as a network relay for WebRTC traffic when a direct connection cannot be established. It is not cloud storage for your files.

Do I need to create an account?

No. ShareWave does not require registration or an account to use the file transfer service.

Can I transfer multiple files?

Yes. ShareWave is designed to support transferring multiple files during a sharing session, subject to browser, device, and network limitations.

Can I use ShareWave on a mobile phone?

Yes. ShareWave can be used from supported modern mobile browsers. The sender and receiver should keep the browser page open until the transfer is completed.

Is the connection encrypted?

WebRTC uses encrypted communication for WebRTC data channels. Connection establishment also uses signaling information to allow the participating browsers to negotiate the connection.

What information does the signaling server handle?

The signaling service is used to help the participating browsers establish a WebRTC connection. Depending on the implementation, signaling can include connection and session information, WebRTC negotiation data, and network information required to establish the connection.

What if the connection does not work?

Direct connections can sometimes be affected by strict firewalls, NAT configurations, VPNs, or other network restrictions. Try again, switch networks, or disable a VPN if appropriate. A TURN relay may be used when a direct WebRTC connection cannot be established.