Large file transfer

Send large files free, with no signup.

Choose the file, share the QR code or link, and keep both browsers open. The bytes move during the live session instead of waiting in cloud storage.

Start the transfer

Either 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.

—

Enter the code.

Smart Send

Recipient ready.

Checking whether the original file is the best fit.

Recipient capabilities are approximate and temporary.
Original

Original file

Best quality

Technical details

FCShare never changes your original file. Optimization only happens after you choose it.

Save this?

    Transferring

    Moving now.

    0%
    0 B of 0 B —
    —Speed
    ConnectingPath
    EncryptedIn transit

    Delivered.

    No copy was kept anywhere.

    Stopped.

    Ready
    Room—
    Route—
    Payload—
    The short answer

    A large-file transfer without an upload queue

    FCShare is useful when an attachment limit or free-plan cap is the only thing stopping you. It does not impose a service-level file-size ceiling because it does not store the file first. The sender reads it in small chunks and sends those chunks over an encrypted WebRTC connection.

    That design removes the upload-then-download cycle, but it changes the tradeoff: the sender and receiver must be online at the same time, both pages must stay open, and the transfer is only as reliable as the two devices and networks. For extremely large files, desktop browsers with direct disk writing are the safest choice.

    How to do it

    Three steps, in the browser.

    1. 1

      Choose Send

      Select one file or several files. Nothing is uploaded when you choose them.

    2. 2

      Share the room

      Let the other person scan the QR code, open the link, or type the short room name.

    3. 3

      Keep both pages open

      The receiver accepts a save location and the live browser-to-browser transfer begins.

    Best for

    • Multi-gigabyte archives
    • RAW photo batches
    • Project exports
    • One-time live delivery

    What stays intact

    • Original filenames
    • Original file bytes
    • Original video quality
    • Multiple-file selection

    Know before sending

    • No resumable transfer yet
    • Both people must be online
    • Free disk space still matters
    • Older browsers may still use memory

    What “no size limit” means here

    FCShare sets no product-plan or server-upload cap. Browsers, RAM, storage, battery life, bandwidth, and connection stability still create practical limits. If the receiving browser supports direct file-system writing, the file can be written as it arrives; otherwise it may need to be assembled in memory before download.

    Why it can feel faster

    A cloud transfer normally sends the whole file to a storage server and then makes the recipient download it. A live peer transfer removes that waiting stage. It does not make either internet connection faster, and the slower upload/download path still determines throughput.

    Questions people ask

    Can I send a 10 GB, 50 GB, or 100 GB file?

    There is no FCShare plan cap, but success depends on both browsers, available storage, and a stable connection. Test a smaller file first and prefer desktop-to-desktop for very large transfers.

    Does the recipient need an account?

    No. They only need the room link or code and a current browser.

    Can the recipient download later?

    No. This is a live transfer, not a stored download link. Both pages must remain open until it finishes.