Lightning P2P
Share files straight from this tab.
Send from this browser
Share files straight from this tab.
Direct answer
Drop files on the page and this tab serves them to whoever opens your link - their browser, desktop app, or terminal. Content is not uploaded to cloud storage; encrypted relay traffic may carry the connection. Browser sending is beta: files live in tab memory (best under 500 MiB, hard limit 2 GiB), browser peers use encrypted relay transport, and the tab must stay open while peers download. Browser receiving streams verified chunks to disk when the File System Access API is available; otherwise it has a 128 MiB aggregate memory limit. The native app streams from disk.
Drop files on the page and this tab serves them to whoever opens your link - their browser, desktop app, or terminal. Content is not uploaded to cloud storage; encrypted relay traffic may carry the connection.
Browser sending is beta: files live in tab memory (best under 500 MiB, hard limit 2 GiB), browser peers use encrypted relay transport, and the tab must stay open while peers download. Browser receiving streams verified chunks to disk when the File System Access API is available; otherwise it has a 128 MiB aggregate memory limit. The native app streams from disk.
Sending from the browser runs the identical iroh + iroh-blobs Rust core as the desktop app, compiled to WebAssembly. Files are imported into an in-memory store, the tab answers iroh-blobs requests over the relay, and every receiver verifies BLAKE3 hashes as bytes arrive.
The share link is a normal HTTPS receive link with the ticket in the URL fragment. Browsers omit the fragment from the HTTP page request, but page scripts can read it. Anyone opening it can receive in their own browser tab, the desktop app, or the CLI.
Browser peers cannot hole-punch, so browser-to-anywhere transfers use the iroh relay. The relay forwards encrypted frames and does not host files for later download.
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.9.33.
Key facts
- Product
- Lightning P2P
- Category
- peer-to-peer file transfer and account-free chat app
- Platform
- Windows stable release, Android 10+ sideload release
- Stable release
- v0.4.6
- Experimental release
- v0.9.33 with Lightning Chat, BBR congestion control, Warp mode, and swarm receive
- 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 chat uses internet relays; nearby Bluetooth mesh and media are native-only.
- Public speed leadership claims require repeatable benchmark results.
Frequently asked questions
- Does sending from the browser upload my files anywhere?
- No cloud upload is used. Files stay in the sender tab's memory and are served while that tab is online. The iroh relay can forward encrypted frames when needed; it is a connectivity service, not file storage.
- How big can a browser share be?
- Browser sending stores files in tab memory, warns past 500 MiB, and refuses past 2 GiB. Browser receiving streams verified chunks to a chosen file in supported browsers; otherwise it has a separate 128 MiB aggregate memory limit. Use the native app for larger sends or when the browser cannot stream to disk.
- Can I close the tab after sharing the link?
- No - the tab is the sender. Keep it open until the receiver finishes, exactly like keeping the desktop app running during a transfer.