Original
Original file
Best quality
Private one-time transfer
A private file transfer with less left behind.
No profile, no public upload page, and no transfer history. Add a room password when the link or code will travel through a channel you do not fully control.
Start the transferEither way you get a code. Whichever device has a camera scans it.
Choose a file.
Scan this.
Or open the link, or type the name.
—
Locked
Enter the code.
Smart Send
Recipient ready.
Checking whether the original file is the best fit.
Recipient capabilities are approximate and temporary.
Recommended
Optimized version
Better compatibility
Technical details
FCShare never changes your original file. Optimization only happens after you choose it.
Save this?
Transferring
Moving now.
What should the sender prioritize?
The sender still chooses what is sent.
0%
—Speed
ConnectingPath
EncryptedIn transit
Delivered.
No copy was kept anywhere.
Stopped.
Ready
Room—
Route—
Payload—
The short answer
Privacy comes from reducing copies
FCShare minimizes the service-side data footprint: the room exists in memory, the signalling server coordinates two browsers, and the file payload is not stored. The optional password is transformed into a PBKDF2-derived token before the browser sends it to the room service.
Private does not mean anonymous under every threat model. Network operators can observe connections, endpoints still possess the file, and a compromised device or browser can expose what it can access. For highly regulated or adversarial use, apply your organization’s approved encryption and transfer policy.
How to do it
Three steps, in the browser.
- 1
Select the file
Choose only what you intend to send and verify the filename shown to the recipient.
- 2
Protect the room
Open Room options and add a password; share it through a separate channel when practical.
- 3
Confirm the recipient
Stay present, let the intended person join, and close the page after completion.
Best for
- Private drafts
- Direct client handoff
- Personal documents
- Temporary collaboration
What stays intact
- No service file archive
- Optional join password
- Encrypted WebRTC transit
- Ephemeral room state
Know before sending
- Endpoints must be trusted
- Not an anonymity network
- No malware scanning
- Policy requirements still apply
What the password does
The password locks room entry. The server compares derived tokens and rate-limits repeated failures; it does not receive the plaintext password. Use a unique password and avoid placing it in the same message as the room link if the file is sensitive.
What encrypted in transit means
WebRTC data channels use encrypted transport between endpoints. A TURN compatibility route can relay encrypted packets when necessary. The recipient ultimately receives a normal file, so protect the destination device and storage appropriately.
Questions people ask
Is there a public list of transfers?
No. FCShare has no browseable room directory or transfer history.
Should I encrypt the file itself?
For sensitive or regulated data, file-level encryption adds protection after delivery and may be required by policy. Share the decryption secret separately.
Does the room password encrypt the saved file?
No. It controls room admission. The saved file is a normal file on the recipient’s device.