FileCarpenterFCShare
AboutPrivacy
Large-file P2P

Send large files peer-to-peer, with a smarter preflight.

The existing fast DataChannel path stays the default. Smart Send only steps in when compatibility, size or storage may matter.

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
    P2P first, adaptation only when useful
    
      
    Generic files such as PDF, ZIP and Office documents are not processed simply because Smart Send exists. They remain on the original fast path.
    Large media can use the same transfer engine after a short receiver-aware preflight. This keeps the product simple while preventing avoidable playback or storage failures.
    
    
    

    
    
      
    How to do it
    Three steps, in the browser.
    
      
      
      
    1. 1
      Choose files
      Ordinary files stay on the direct path immediately.
      2. 
      
    2. 2
      Connect the peer
      The route uses WebRTC with TURN as fallback.
      3. 
      
    3. 3
      Accept and save
      Existing bounded backpressure and disk batching remain unchanged.
    
    
    

    
    
      
    Best for
    • Large archives
    • Project folders selected as files
    • Media delivery
    • Cross-network transfers
    
      
    What stays intact
    • No account
    • No plan size cap
    • Same chunk/backpressure engine
    • Same QR/share link
    
      
    Know before sending
    • Folder hierarchy not preserved
    • No resume
    • Browser/device practical limits
    • One sender and one receiver per room
    
    
    

    
    
      
    Why not optimize everything
    Processing compatible files would waste CPU, battery and time. Smart Send deliberately bypasses adaptation for generic binaries.
    
      
    Why TURN remains
    Strict NAT and corporate networks can block direct paths. TURN keeps the session working without creating a stored cloud file.
    

    
    
      
    Questions people ask
    
      
    
      
    Are ZIP files transformed?
    No.
    
      
    Does Smart Send slow down normal PDF transfer?
    No media optimization is loaded for ordinary document transfers.
    
      
    Can I see the route?
    Yes, when browser WebRTC statistics expose enough information.
    
    
    

    
    
      
    Related jobs
    
      
    Large file transferSend large files free, with no signup.Send large files free between two browsers with no signup and no server upload. No service size cap; both devices stay connected during transfer.
Browser P2P transferPeer-to-peer file transfer, without installing an app.Use a browser-based peer-to-peer file transfer. Files move over encrypted WebRTC; the server coordinates the connection but does not store the payload.
Direct browser transferSend files directly when the networks allow it.Send files directly between browsers when WebRTC can establish a peer route, with encrypted TURN relay fallback and no stored FileCarpenter payload.
    
      Browse all file-transfer guides →