Lightning P2P
Speed claims need repeatable numbers.
Benchmark-backed claims
Speed claims need repeatable numbers.
Direct answer
Lightning P2P is designed for high-throughput direct transfer, but public speed claims should be tied to repeatable benchmark reports.
Lightning P2P is built for high-throughput transfers, but public claims should be tied to hardware, network route, file size, app version, and measured results.
The benchmark page defines the test matrix before publishing strong speed claims, so users can trust the comparison instead of reading hype.
Download the recommended Velopack one-click installer, the classic NSIS setup installer, or the MSI installer. Android users can sideload LightningP2P-android-latest.apk and verify it with SHA256SUMS-android.txt. Signing status, SmartScreen notes, Android sideload notes, and SHA256 checksums are available on GitHub Releases. App version: v0.5.1.
Key facts
- Product
- Lightning P2P
- Category
- peer-to-peer file transfer app
- Platform
- Windows stable release, Android 10+ sideload release
- Stable release
- v0.4.6
- Experimental release
- v0.5.1 speed modes + reliability (carries v0.5.0 BLE/NFC)
- License
- Apache-2.0
- Account required
- no
- Cloud upload
- no
- Artificial file-size cap
- no
- Transfer model
- direct-first P2P
- Transport
- iroh / QUIC
- Verification
- BLAKE3
- Source code
- GitHub
- Cost
- free
Important caveats
- Sender must stay online until the receiver finishes.
- Tickets are capability tokens and should be treated as secrets.
- Relay fallback helps connectivity, but it is not cloud storage.
- Browser website is receive handoff and marketing, not the transfer engine.
- Public speed leadership claims require repeatable benchmark results.