Send files directly. No cloud, no limits.
Chute sends a file straight from your machine to someone else's. There is no upload step, no account, and no copy of your file sitting on a server afterwards. The bytes leave your device and arrive at theirs, and that is the whole path.
Both sides open Chute and exchange a short peer ID. A rendezvous server introduces the two machines to each other, then steps out of the way: it only ever brokers the connection details, never the file itself.
From there the two devices talk over an encrypted WebRTC data channel. Chute deliberately ships without a relay server, so your data is never routed through infrastructure we operate. If a direct path can't be found, the transfer fails honestly instead of quietly falling back to someone else's hardware.
Direct connections are the hard part, so Chute tries every route at once: IPv6, multiple STUN servers, UPnP and NAT-PMP port mapping, mDNS for peers on the same network, and ICE over TCP where UDP is blocked. For the awkward case of two symmetric NATs, it predicts the ports the other side's router will hand out and aims at them.
Chute is free for personal use. There are no file size caps, no transfer quotas, and no bandwidth bill on our side to pass on to you, because your files never touch our bandwidth.
Native desktop builds for macOS (Apple Silicon and Intel), Windows (x64 and ARM64), and Linux. Grab the build for your machine from the download button above.
No. The file moves directly from sender to recipient over an encrypted channel between the two devices. We never receive it, store it, or have any way to read it.
Introductions only. The rendezvous server helps two peers find each other and swap the technical details needed to open a connection. Once that handshake is done it has no further involvement, and it never sees a single byte of file data.
No. Since there's no storage tier to fill up, transfer size is bounded only by your disk and how long you're willing to leave the window open.
Yes. A direct transfer needs both ends present, because there's no intermediate copy to hold the file while the other side catches up. That's the trade for never handing your data to a third party.
Yes, end to end. The data channel between the two peers is encrypted by default, and because there's no relay in the middle there is nowhere for an intermediary to decrypt it even in principle.
No. There's no sign-up, no email, and no profile. Open the app, share your peer ID, transfer.
Often, but not always. Chute tries hard, with IPv6, port mapping, and a TCP fallback for networks that block UDP, but a network that blocks direct peer connections outright will stop the transfer, since there's no relay to fall back on.
Yes, free for personal use. No subscription, no per-transfer fee, and nothing to unlock.
macOS (Apple Silicon and Intel), Windows (x64 and ARM64), and Linux x86_64 as an AppImage or a plain binary. A Linux ARM64 build isn't published yet.
Email contact@chute.to with what you were doing and what happened.
Chute enables direct file transfers between devices. Files are sent directly from sender to recipient, and we cannot see, access, or store any transferred content. You are solely responsible for the files you send and receive.
Do not use Chute for illegal purposes, including but not limited to transferring copyrighted material without authorization, malware, or any content that violates applicable laws. By using Chute, you agree to comply with all applicable laws and accept full responsibility for your actions. Chute and its developers assume no liability for misuse.