blixtTips
Tips for fast transfers.
Blixt picks the fastest route it can on its own, but a few things on your side decide how fast that route is. Six checks, in the order they usually matter.
- Turn off VPNs and Cloudflare WARP. A VPN or WARP tunnel hides your real network path, which can make a direct peer-to-peer connection impossible and force the transfer through a slower relay. Switch them off for the fastest direct connection.
- Prefer QUIC and peer-to-peer connections; avoid relays. The fastest route is a direct QUIC connection between the two devices; direct HTTPS comes next. Relays exist so a transfer always gets through — they are the fallback, not the fast path.
- Don’t use Multiconnect on a single line. Multiconnect aggregates several physical links — say Ethernet plus LTE — into one transfer. Splitting a single physical line into parallel subflows adds overhead without adding bandwidth, so leave it off unless you really have more than one.
- Run the speed test and the hardware test. The Speedtest page in the app measures your link (QUIC, HTTPS, Multiconnect) and your machine (disk, hashing, encryption ceilings), so you can see whether the network or the hardware is your bottleneck before blaming either.
- Add a firewall exception for QUIC. QUIC runs over UDP, and a firewall that blocks its port silently pushes transfers onto slower paths. The desktop app offers to add the exception on first run — accept it, or add one manually if you skipped it.
- Use Compress only for data that compresses. Text, logs and raw datasets shrink well and travel faster compressed. Video, audio and archives are already compressed — recompressing them burns CPU without saving a byte, so skip Compress there.
New to Blixt?
The tutorial walks through a first transfer — the code, the 6-digit check and what happens in between. How Blixt works →