For video & photo professionals
Hand your client 500 GB tonight. Not tomorrow.
The deadline won’t move, so your footage has to. Blixt sends files straight from your machine to theirs — no upload step in the middle, no resending blocks that were already verified after an interruption, and no bill that grows with every gigabyte.
The messages you never want to see again
Three ways a delivery night goes wrong.
“File too large.”
You’ve seen it at 11 pm with a 9 am delivery. Blixt streams the file directly to your receiver instead of parking it on someone’s server. Free supports files up to 500 MB; every paid plan removes the per-file cap entirely.
“Transfer failed at 87%.”
Blixt checks its resume journal and re-sends only blocks marked missing. Hotel Wi-Fi kicked you off, the laptop slept, the line hiccuped: blocks already verified do not have to be sent again.
“I’m not installing anything.”
Fine — send a share link instead. It opens in a plain browser on any device, including a phone, with a password, an expiry date, and a download limit if you want them. Your client clicks, the files land.
Speed
Speed is deadline math.
A cloud service moves your footage twice — up to their server, then down to your client, throttled both ways. Blixt makes one trip and uses everything your connection can give. That’s the difference between delivering tonight and apologizing tomorrow.
One transfer, not an upload followed by a download.
A cloud handoff waits for the sender’s upload before the client can finish a separate download. Blixt streams from sender to receiver in one transfer; if a direct path cannot connect, a relay fallback keeps it moving without a cloud-storage step. Actual time depends on both connections, distance and network conditions. See the published method and measured results at /benchmarks.
Thin hotel uplink? Add your connections together.
Plug in Ethernet, keep Wi-Fi on, tether your phone — Blixt can distribute chunks across selected independent connections. The actual gain depends on the paths and their shared bottlenecks; if one path fails, missing work can continue on the remaining paths.Basic plan and up · direct transfers
The bill
Never a per-gigabyte invoice.
Media transfer services that bill by volume typically charge around $0.25 per gigabyte — at that typical rate, one terabyte of dailies is roughly $250, every single time you send it. A busy month of deliveries becomes a salary line.
Blixt is a flat subscription from $0 to $50 a month. Direct paths travel between the endpoints, and Blixt does not add a per-gigabyte transfer charge. If a direct connection cannot be made, an encrypted relay fallback can carry the traffic without turning it into a cloud-storage upload. See the plans →
The only jargon on this page: under the hood Blixt runs QUIC with BBR congestion control over TLS 1.3 with certificate pinning, verifies every chunk with BLAKE3, and shows both sides a 6-digit code to compare out loud. If your engineer wants the full story: the security model.
Tonight’s delivery can still make it.
Start now
Download, drop the footage, read six digits over the phone. First transfer in minutes.
Download freeCompare plans
Flat subscriptions from $0 to $50. The math next to a per-gigabyte bill is short.
See pricingReassure your client
When they ask where the file lives on the way over: nowhere. Show them how that works.
How security worksFAQ
Fair questions, straight answers.
Does my client need to install anything?
For a direct machine-to-machine transfer — yes, both sides run Blixt; that’s what makes it direct. If your client won’t install anything, send a share link instead: it opens in a plain browser on any device, no account and no install, with a password and expiry if you want them.
Can I send straight from my phone?
Android Preview 0.1.0 can send from Android 10+ arm64 devices. Distribution: Sideloaded debug APK. Use it for testing rather than sensitive production deliveries. iOS is planned. A bCloud share link still opens in any mobile browser; see mobile options.
Is the free plan enough for real footage?
For a real shoot — no. The free plan caps each file at 500 MB: enough to learn the flow, send selects, and run a test with a client. Every paid plan removes the per-file cap entirely, from $5/mo — see pricing.
What happens if the transfer drops overnight?
It checks the tamper-protected resume journal and continues with the blocks marked missing; blocks already verified are not re-sent.