Skip to main content
Starts a transfer session as the sender. Floe registers a short code with the signaling server, prints a sharing panel, then waits for a peer to connect. Once connected, it streams all files over an encrypted WebRTC data channel.

​
Examples

Send a single file:
Send multiple files at once:
Send an entire folder (transferred recursively):

​
Output

After running floe send, Floe shows a summary of what will be sent, then prints a sharing panel:
Once the recipient connects, Floe negotiates the WebRTC connection and streams each file with a live progress bar:
Share the code with CLI recipients or the link with browser recipients. The short code is valid for 10 minutes. The room link stays active until the session ends or you press Ctrl+C.

​
Folder transfers

When you send a folder, Floe walks it recursively and preserves the directory structure on the receiving end. The recipient gets the same relative paths inside their output directory.

​
Flags

See Flags Reference for --server, --no-relay, and --web.

​
Notes

  • Relayed transfers are capped at 2 GB per session; direct connections have no size limit. When the selected route runs through the TURN relay and the queued files total more than 2 GB, floe send blocks the transfer before any file data moves. See The 2 GB Relay Limit.
  • Press Ctrl+C at any time to cancel the transfer and close the session.
  • If the short code cannot be registered (for example, the signaling server is unreachable), Floe prints a warning and continues with the link only.
  • Files are streamed in the order they are listed. For multiple files, progress is shown per file.
  • The sender never reports to the global transfer counter. Only the receiver does. To opt out on the receiving side, the receiver uses --no-report or sets FLOE_NO_STATS=1.