Skip to main content

​
Global flags

Available on all commands (send, receive, update, version).

​
Environment variables

If you run your own signaling server, set it once in your environment instead of passing --server on every command. A flag always beats its variable, so you can override the setting for a single command without unsetting anything:
On Windows PowerShell:
Trailing slashes are trimmed, so https://floe.example.com/ and https://floe.example.com behave the same. Set FLOE_WEB only when your web app runs on a different host than your signaling server. Leave it unset and share links point at the same host, which is what you want when one domain serves both.

​
floe receive flags

Specific to the receive command.

​
Opting out of the global counter

After a successful transfer, the receiver sends only the total byte count to Floe’s signaling server to power the public “transferred globally” counter on the homepage. No file names, contents, or identity are included, and reporting is always fire-and-forget (it never blocks or slows a transfer). The sender never reports. To opt out for a single transfer, pass --no-report:
To opt out permanently, set FLOE_NO_STATS=1 in your environment (for example in your shell profile):
When opted out, no request is sent to the server and the global counter is not incremented for that transfer. The transfer itself is unaffected.

​
Examples

Use a local dev server for both sender and receiver:
Disable relay fallback (direct connections only):
Point the browser link at a custom web client:
Save received files to a specific folder and auto-accept:
See Against a Self-Hosted Server for more server configuration examples.