Original file
Best quality
No upload. No signup. Direct when possible. When a file may not suit the other device, Smart Send can recommend a compatible copy made locally on the sender.
Either 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.
Send or Receive — either puts a code on screen.
Or opens the link, or types the name.
Device to device. Nothing is uploaded.
FCShare exists for the moment when two people are already talking and simply need to move a file. No account, no drive to organise, no upload queue, no archive waiting afterward.
Either device can show the code and either can scan it, so the one with a camera always does the scanning — whichever direction the file is going. Your browser then reads the file in small pieces and sends them straight to the other browser over an encrypted connection. Our signalling server introduces the browsers. If a direct WebRTC path cannot be established, encrypted packets may travel through a TURN relay, but FCShare does not keep a stored file copy.
Direct when possible. If networks block a direct path, encrypted WebRTC traffic can use a TURN relay without becoming stored cloud sharing.
The transfer exists only while both pages stay open.
No profile, library, or history to maintain.
FCShare does not impose one. The practical limits are the browsers, devices, available disk space, and network connection. Where supported, incoming data is written to the chosen file or temporary browser storage as it arrives; older browsers may still need to assemble it in memory.
Whichever one has a camera. Both Send and Receive show a code, so a phone can scan a laptop's code and then send it a file — the laptop never has to scan anything or type anything.
No. Choosing the file is immediate. Transfer begins only after both devices connect and the receiver accepts.
Your browser turns the password into a token using PBKDF2, with the room name as salt, before anything is sent. Only that token reaches the server, so the password itself never leaves your device. It controls who may join — the transfer is encrypted in transit either way.
No. Both people need to keep their pages open for the entire transfer, and interrupted transfers cannot resume.
Select every file inside it and they will arrive together. Folder structure is not preserved yet.
No. FCShare stores neither the file nor a history of completed transfers.