FileJaunt

FileJaunt

Encrypted file transfer, straight between two machines.

  • End-to-end encrypted: SPAKE2 pairing, AES-256-GCM data channels.
  • Nothing uploads — files stream from one machine straight to the other.
  • Every file is SHA-256-verified on arrival.
  • No account, no FileJaunt server, no database.
A — your machine sends field-notes.pdf

passphrase — spoken, not sentamber tiger orbit wax copper lantern

B — their machine receives field-notes.pdf · verified
FIG. 1 — the jump: two machines, one passphrase, nothing in between.

The jaunt pad

Pick a side, trade two pastes, and your files cross machine to machine. The passphrase travels by voice — never through the network. Files cross only while both tabs stay open.

Pairing

pick a side to begin

Passphrase — say it, don't send it

Read it aloud or send it over a channel you already trust. It is never part of the pairing blob.

Outbound

Nothing uploads. Files are read chunk by chunk as they cross.

    After a drop, the same passphrase resumes where it stopped.

    Inbound

    Without a picked folder, received chunks land in this browser's private storage (on this machine only) — that's what lets a dropped connection resume. Pick a folder to write straight to disk.

      
        
      
      
      

      
      

      
      
        Advanced
        
      
          
      
            
            
            empty means LAN only
          
      
          
      
            
            
          
      
          
      
            
            
          
      
          
      
            
            
          
      
        
      
        
      
          
          
        
      
      
      

      
    
      
  
      

  
      
    
      Three moves, one jump.
      
    
        
      
      1. 
        01
        
        Drop the files
        
        
        The sender picks files or a folder and gets a passphrase plus the first pairing blob.
        
      
        2. 
      
      2. 
        02
        
        Trade the blobs
        
        
        The receiver pastes that blob with the passphrase, spoken aloud or sent over a channel you already trust. The passphrase itself never travels inside the blob.
        
      
        3. 
      
      3. 
        03
        
        Watch them land
        
        
        Chunks stream over a direct WebRTC channel, every file hashed with SHA-256 on the way out and verified on arrival.
        
      
        4. 
    
      
  
      

  
      
    
      What FileJaunt never sees.
      
    
      
      
      encryption
      
      
      End to end, before anything crosses. Pairing runs SPAKE2 over the pasted blobs; the session keys never leave the two machines.
      
      
      your files
      
      
      Never uploaded, never stored by FileJaunt — there is no FileJaunt server. The page you are reading is static files; the transfer core runs in your browser.
      
      
      transport
      
      
      WebRTC data channels: direct when the network allows, otherwise a TURN server you supply. No FileJaunt server is involved at any point.
      
      
      integrity
      
      
      Every file is hashed with SHA-256 before it leaves and verified again on arrival.
      
      
      resume
      
      
      A dropped connection picks up with the same passphrase. Chunks already received stay on the receiving machine, so nothing restarts from zero.
      
      
      license
      
      
      AGPL-3.0-only. The transfer core is Rust compiled to WebAssembly; this pad is plain HTML on top of it. Read the security model.
      
    
      
  
      

  
      
    
      Six words, two pastes, one jump.
      
    
      No sign-up. No file ever touches a server.
      
    Start a jump