Skip to main content
Floe transfers files directly between devices using WebRTC. Files are end-to-end encrypted and never stored on any server. The signaling server only brokers the initial connection setup. Once both peers are connected, it steps aside.

​
What Floe does

  • Direct, peer-to-peer transfers. Files travel straight from your device to the recipient’s device.
  • End-to-end encrypted. Every transfer is encrypted with DTLS. No one, including Floe’s servers, can read your files.
  • No accounts or storage. No sign-up, no uploads, no data retained after the transfer completes.
  • No size limit on direct transfers. Relay connections are capped at 2 GB per session to keep the service free.
  • Browser and CLI. Use the web app at floe.one or the floe command-line tool. Both are fully compatible with each other.
  • Open source and self-hostable. Run your own instance on your own infrastructure with Docker Compose.

​
Use Floe

Browser

Open floe.one in any modern browser. No installation required.

CLI

Install the floe binary for headless, scriptable transfers.

​
Common questions

Your files go directly to the recipient’s device. In most cases they never touch a server at all. When a direct path cannot be found (strict corporate firewalls, carrier-grade NAT), Floe automatically falls back to an encrypted TURN relay. Even then, the relay server sees only encrypted packets and cannot read your files.
Direct connections have no size limit. Relay connections are capped at 2 GB per session to keep the service free. See Why the 2 GB Limit? for details. Most home and mobile network transfers connect directly and have no limit.
No. Floe requires no account, no sign-up, and no registration. Open the site or run the CLI and share the link or short code with your recipient.
Transfer speed is limited only by the slower of the two connections involved. There is no artificial throttling. Direct transfers are as fast as your internet connection allows. Relay transfers may be slightly slower depending on server load, but encryption overhead is minimal.
Any modern browser with WebRTC support works: Chrome, Firefox, Safari, Edge, and most Chromium-based browsers. A secure context (HTTPS or localhost) is required. WebRTC is not available in some in-app browsers (such as those embedded in Facebook, Instagram, or TikTok). If this affects you, Floe will prompt you to open the page in Chrome or Safari instead.
Yes. The floe CLI is a self-contained binary for macOS, Linux, and Windows. It connects to the same infrastructure as the web app, and is fully compatible with browser clients. A CLI sender can transfer to a browser receiver, and vice versa. See CLI Installation to get started.
Yes. The full source for the client, server, and CLI is available on GitHub under the MIT license. You can also self-host your own instance.

​
Self-hosting

You can run your own Floe instance on your own infrastructure using Docker Compose. See the Self-Hosting section.