# Floe

## Docs

- [Changelog](https://www.floe.one/docs/changelog.md): Release history for Floe.
- [Floe CLI Flags Reference](https://www.floe.one/docs/cli/flags.md): Complete reference for every floe CLI flag, covering send, receive, self-hosted server URLs, output paths, timeouts, and verbose logging options.
- [Install the Floe CLI](https://www.floe.one/docs/cli/installation.md): Install the floe CLI in one command on macOS, Windows, or Linux to send and receive files peer-to-peer from the terminal without an account.
- [floe receive command](https://www.floe.one/docs/cli/receive.md): Use the floe receive command to accept files from a peer over an encrypted WebRTC connection using a share code, with no upload or account needed.
- [Use the Floe CLI with a Self-Hosted Server](https://www.floe.one/docs/cli/self-hosted-server.md): Point the floe CLI at your own self-hosted Floe signaling server instead of floe.one to send and receive files on your own infrastructure.
- [floe send command](https://www.floe.one/docs/cli/send.md): Use the floe send command to share files or folders peer-to-peer from your terminal over an encrypted WebRTC connection, with no upload or account.
- [Update the Floe CLI](https://www.floe.one/docs/cli/update.md): Keep the floe CLI up to date on macOS, Windows, and Linux using the built-in self-update command or by reinstalling the latest release binary.
- [floe version command](https://www.floe.one/docs/cli/version.md): Print the installed floe CLI version, build metadata, and platform to verify your install and share diagnostic details when reporting an issue.
- [Floe FAQ](https://www.floe.one/docs/faq.md): Answers to common questions about Floe: how peer-to-peer file transfer works, file size limits, privacy, WebRTC, and using Floe without an account.
- [The 2 GB Relay Limit](https://www.floe.one/docs/how-it-works/2gb-limit.md): Why Floe caps relayed transfers at 2 GB per session, how the limit protects the shared TURN server, and how direct peer-to-peer transfers avoid it.
- [Direct Peer-to-Peer Connection](https://www.floe.one/docs/how-it-works/direct-connection.md): How Floe uses STUN and ICE to open a direct WebRTC data channel between two peers so files transfer without ever touching a server.
- [End-to-End Encryption in Floe](https://www.floe.one/docs/how-it-works/encryption.md): How Floe uses WebRTC DTLS to end-to-end encrypt every file transfer so neither the signaling server nor the TURN relay can read your data.
- [TURN Relay Fallback Connection](https://www.floe.one/docs/how-it-works/relay-connection.md): How Floe falls back to a TURN server as an encrypted bridge when strict NAT or firewalls block a direct peer-to-peer WebRTC connection.
- [How Floe Signaling Works](https://www.floe.one/docs/how-it-works/signaling.md): How the Floe signaling server brokers the initial WebRTC handshake between sender and receiver without ever seeing the files being transferred.
- [Introduction to Floe](https://www.floe.one/docs/introduction.md): Floe is a secure, encrypted peer-to-peer file transfer tool that sends files directly between browsers over WebRTC with no accounts and no uploads.
- [Floe Quick Start](https://www.floe.one/docs/quickstart.md): Send your first file with Floe in under a minute using the web app at floe.one, with peer-to-peer WebRTC transfer and no signup or install required.
- [Floe Architecture Reference](https://www.floe.one/docs/reference/architecture.md): Reference for the Floe signaling protocol, HTTP endpoints, WebSocket events, and the WebRTC data-channel binary framing used for file transfers.
- [Security and Privacy](https://www.floe.one/docs/security-privacy.md): Learn what Floe's signaling server and TURN relay can see, how end-to-end DTLS encryption protects file bytes, and how to opt out of stats.
- [How the Client Finds the Signaling Server](https://www.floe.one/docs/self-hosting/build-time-url.md): How a self-hosted Floe web client resolves its signaling server address at runtime with SOCKET_URL, and when a rebuild is still required.
- [Self-Hosted Floe Configuration](https://www.floe.one/docs/self-hosting/configuration.md): Environment variable reference for a self-hosted Floe instance, covering client build-time URLs, CORS, TURN credentials, and stats persistence.
- [Container Images](https://www.floe.one/docs/self-hosting/images.md): The prebuilt Floe container images on ghcr.io: names, tags, how to pin a version or a digest, and which architectures are supported.
- [Self-Hosted Floe Operations](https://www.floe.one/docs/self-hosting/operations.md): Day-to-day operations for a self-hosted Floe instance: upgrading containers, viewing logs, monitoring transfers, backing up stats, and rotating TURN keys.
- [Self-Hosting Floe Overview](https://www.floe.one/docs/self-hosting/overview.md): Run your own Floe signaling server, web client, and optional TURN relay on your own infrastructure for full control over peer-to-peer file transfer.
- [Production Deployment for Self-Hosted Floe](https://www.floe.one/docs/self-hosting/production.md): Deploy a self-hosted Floe instance in production with HTTPS, a reverse proxy, custom domain, WebSocket support, and secure TURN relay credentials.
- [Self-Hosting Quick Start](https://www.floe.one/docs/self-hosting/quickstart.md): Spin up a local Floe instance with Docker Compose in a few minutes to try self-hosted peer-to-peer file transfer on your own machine before deploying.
- [Run Floe Behind One Domain](https://www.floe.one/docs/self-hosting/reverse-proxy.md): Serve the Floe web client and signaling server from a single domain with a reverse proxy, including copy-pasteable Caddy and nginx configuration for WebSocket support.
- [Add a TURN Relay to Self-Hosted Floe](https://www.floe.one/docs/self-hosting/turn-relay.md): Add a coturn TURN relay to a self-hosted Floe instance so peers behind strict NAT, CGNAT, or corporate firewalls can still complete file transfers.
- [Run Self-Hosted Floe Without Docker](https://www.floe.one/docs/self-hosting/without-docker.md): Run the Floe signaling server and web client directly with Node.js, pnpm, and Go instead of Docker Compose for custom self-hosted deployments.
- [Floe Troubleshooting Guide](https://www.floe.one/docs/troubleshooting.md): Fixes for common Floe issues: stuck connections, failed transfers, invalid room links, TURN relay problems, and self-hosting deployment errors.
- [Receiving Files with the Floe Web App](https://www.floe.one/docs/web-app/receiving.md): Open a Floe share link in your browser to receive files peer-to-peer over WebRTC, with no account, install, or server upload required.
- [Sending Files with the Floe Web App](https://www.floe.one/docs/web-app/sending.md): Send files from the Floe web app at floe.one by generating a share link, sending it to your recipient, and streaming files peer-to-peer over WebRTC.