Skip to main content
Your files never make a stop. Floe sends them straight from one device to another over an encrypted connection: no account, no upload, and nothing kept on a server.

Start here

Send a file right now

Under a minute, in a browser.

Run my own instance

Two commands with Docker Compose.

See how it is encrypted

What is protected, and by what.

Pick a Floe

All three send to each other in any direction, so this is a question of convenience rather than compatibility.

Web app

Nothing to install. Open floe.one, drop a file, share the link.

Desktop app

Windows, in beta. Sends folders, pastes screenshots, saves where you choose.

CLI

macOS, Windows, Linux. One binary for servers and scripts.
Not sure which? Compare the three.

What you should know

Encrypted end to end. Every transfer runs over an encrypted WebRTC data channel, so nobody in between can read it, Floe’s own servers included. See Security and privacy, and what Floe does not protect against for the honest other half. No accounts, no uploads. The signaling server introduces the two devices and then steps out of the way. File data never reaches it. See How a transfer works. No size limit on a direct connection. Most transfers connect directly. When a network makes that impossible and the transfer falls back to a relay, it is capped at 2 GB per session to keep Floe free. See File size limits.

Going further

Self-hosting

Run the whole stack on your own infrastructure.

Reference

The architecture, the HTTP API, and the wire protocol.

Changelog

Every release across web, desktop, and CLI.