Skip to main content
Joins an existing transfer session as the receiver. Accepts either a short code (e.g. olive-tiger-castle) or the full browser link. After connecting, Floe prompts you to confirm the incoming transfer and then downloads the files.

Examples

Receive using a short code:
Receive using a full link:
Save to a specific directory:
Auto-accept without a confirmation prompt:

Output

Running floe receive olive-tiger-castle -o ~/Downloads:
With no -o flag, files save to the current directory.

Confirmation prompt

When the first file’s metadata arrives, Floe shows a summary of what is incoming and asks for confirmation:
  • Press Enter, y, or Y to accept and begin receiving.
  • Type n or no to decline. The transfer is cancelled and the connection closes.
Pass -y to skip this prompt and accept automatically.

Flags

See Flags Reference for global flags (--server, --no-relay) and full opt-out documentation.

Notes

  • Received files are saved to the output directory. Existing files are never overwritten: if a name is already taken, the incoming file is saved with a numbered suffix before the extension (report.pdf, then report (1).pdf), the same way browsers de-duplicate downloads. The progress line shows the name actually written.
  • Directory structure is preserved when the sender sends a folder. Files land at the same relative paths inside your output directory.
  • On Windows, received files are tagged with the mark of the web (a Zone.Identifier stream), so SmartScreen and Office Protected View treat them like browser downloads when opened.
  • Press Ctrl+C to cancel the transfer at any time.
  • Short codes expire 10 minutes after the sender starts the session. After that, only the full link works (and only while the sender is still connected).
  • After the transfer completes, the receiver posts only the total byte count to the signaling server for the public global counter. No file names or contents are included. Use --no-report or FLOE_NO_STATS=1 to skip this. The sender never reports.