Original file
Best quality
Two browsers meet through a temporary room. The signalling service introduces them; the transfer payload is sent over WebRTC and is never stored by FileCarpenter.
Start the transferEither way you get a code. Whichever device has a camera scans it.
Or open the link, or type the name.
—
Checking whether the original file is the best fit.
Best quality
Better compatibility
FCShare never changes your original file. Optimization only happens after you choose it.
No copy was kept anywhere.
The server is used to match a room and exchange the connection information WebRTC needs. It does not receive the selected file, build a download page, or retain a transfer history. Once the connection is ready, the file is divided into ordered chunks and sent through the browser data channel.
Networks do not always permit a direct path. When the operator configures TURN and the browsers cannot connect directly, encrypted traffic may be relayed so the transfer can complete. A relay carries packets but does not turn the session into stored cloud sharing.
Either the sender or receiver can create it, so the device with a camera can do the scanning.
The browsers exchange encrypted connection details through the signalling service.
Files move over the live data channel; closing the room ends access.
The status area reports the route the browsers negotiated. “Local network” means both endpoints found a local path. “Direct” means a non-relayed internet path. “Relayed (TURN)” means a relay was required by network restrictions; the file is still encrypted in transit and not stored.
An optional room password is derived into a token in the browser with PBKDF2. The plaintext password is not sent to the signalling server. The password controls who can join; WebRTC transport encryption is used with or without it.
No. There is no completed server-side file waiting for the recipient. The sender must remain connected while bytes move.
The application server does not receive the file payload. As with any web app, use the served code and deployment you trust, and use HTTPS in production.
Some corporate, carrier, or restrictive NAT configurations block a direct WebRTC path. TURN supplies a compatibility route for encrypted traffic.