DashBeam: Peer-to-Peer File Transfer Without Cloud Storage

What DashBeam Does and Who Uses It

Most file-sharing tools route data through a cloud server. The sender uploads to the server, the recipient downloads from it, and the service provider has access to the bytes in transit. DashBeam takes the opposite approach: it moves files directly from the sender's device to the recipient's using peer-to-peer networking.

The README positions this against WeTransfer, Dropbox, and Google Drive. The practical cases are large files that hit cloud upload limits, sensitive files where cloud transit is unacceptable, and high-speed local transfers where a LAN connection is faster than any upload-download cycle.

The tool runs on Windows, macOS, Linux, Android, and as a CLI binary. A browser version at app.dashbeam.net works without any install, though the README notes it has limited throughput compared to the native apps.

Three Ways to Send a File

DashBeam documents three sending methods, and the README describes all three as moving bytes the same way: directly, end-to-end encrypted.

The first method generates a link or QR code for the transfer. The recipient opens it on any device; the browser version requires no install. This is the lowest-friction method for one-time transfers to someone who has not installed DashBeam.

The second method uses paired devices. After an initial pairing with a verification code shown on both screens, subsequent transfers go directly without generating a new link. The README describes this as a remote paired-device workflow.

The third method uses LAN auto-discovery. Devices on the same network appear automatically under Nearby in the Send list. The first contact involves a pairing code. After that, the README describes a Pair and Send option that pairs and starts the transfer in a single step. Discovery uses mDNS, which the README notes is often blocked on guest Wi-Fi and VPNs.

A Trusted Devices feature (added in v0.7.1) lets a paired device auto-accept incoming files without a prompt.

Installing DashBeam on Desktop, Mobile, and CLI

Version 0.7.1 is the current release. Desktop installers are available for direct download from GitHub Releases:

Windows: DashBeam_0.7.1_x64-setup.exe (~10 MB), with MSI and portable ZIP alternatives. MacOS: DashBeam_0.7.1_universal.dmg (~15 MB), with separate Apple Silicon and Intel DMGs. Linux: DashBeam_0.7.1_amd64.deb (~13 MB), with RPM and AppImage alternatives. Android: DashBeam-v0.7.1-arm64.apk (~50 MB).

The CLI binary is available from the downloads page at dashbeam.net. The browser-based version at app.dashbeam.net (~2 MB) requires no download.

The repository uses a Tauri build system with TypeScript (Vite, React) for the frontend and Rust for the native backend. The development build commands in `package.json` are:

pnpm dev

for the Tauri desktop app, and

pnpm dev:web

for the browser version. Building the browser version requires building the WASM bridge first with `node ./scripts/build-wasm-bridge.js --release`.

Encryption, Verification, and Privacy

DashBeam uses TLS 1.3 end-to-end encryption on every transfer. File integrity is verified with BLAKE3, a fast cryptographic hash function. The README lists "no accounts, tracking, or ads" and "direct device-to-device" as explicit privacy properties.

Tickets (links and codes) are authenticated. The Dial by key feature lets devices connect by device identity rather than IP address, which means transfers continue even when the IP changes during a transfer. The README calls this roaming: switching between Wi-Fi, cellular, or networks mid-transfer does not drop the connection.

The underlying P2P networking comes from the iroh library. DashBeam self-hosts relay infrastructure. The README documents a self-host relay option in Settings under Infra, which removes throughput limits on remote transfers for teams running their own relay.

Real-World Transfer Figures from the README

The README includes a table of transfer metrics reported by users:

| Metric | Reported | |---|---| | Largest transfer | 452 GB | | Fastest large transfer | 54 GB at 123 MB/s (~1 Gbps) | | High-speed bulk transfer | 328 GB at 93 MB/s | | Peak speed measured | 125 MB/s (1 Gbps) |

The README adds a note: throughput depends on device, network, and connection path. These figures are user reports, not controlled benchmarks. LAN transfers between two devices on the same gigabit switch are the scenario most likely to approach these numbers. Remote transfers through a relay will be slower.

Limitations and Cases Where DashBeam Does Not Fit

The LAN discovery mechanism uses mDNS, which is blocked on many enterprise and guest Wi-Fi networks and on VPNs. Users in those environments need to use the link/QR code method or rely on a paired device connection.

The browser version has limited throughput compared to the native app. It is suitable for one-off transfers when installing the app is not an option, but not for large regular transfers.

DashBeam is licensed under AGPL-3.0. This is a copyleft license: any software that incorporates DashBeam's code and is distributed to users must also be distributed under AGPL-3.0. Teams building proprietary tools that want to embed DashBeam's transfer functionality need to review this constraint.

Transfers require both devices to be online simultaneously. There is no store-and-forward mode for asynchronous delivery, unlike email or cloud file sharing.

Editorial conclusion

DashBeam is the right choice when file size, privacy, or speed makes cloud-relay services like WeTransfer or Dropbox impractical. The BLAKE3 verification and TLS 1.3 encryption run on every transfer by default. The AGPL-3.0 license requires that derivative software also be distributed under AGPL, which matters for teams considering embedding DashBeam in a commercial product. Web transfer throughput is limited compared to the desktop app. The self-hosted relay option in Settings removes throughput caps on remote transfers, but requires a separate relay server. The last push was on 2026-09-01.

Frequently asked questions

Official sources

1. License: AGPL-3.0
2. Project website
3. README
4. Releases
5. tonyantony300/dashbeam on GitHub