Is Lightning P2P compatible with Magic Wormhole codes?

No. Lightning P2P uses iroh tickets, which are a different format. You cannot paste a Magic Wormhole code into Lightning P2P. The two tools solve a similar problem with different primitives.

Does Lightning P2P need a server like the Wormhole rendezvous?

Lightning P2P uses iroh discovery and relays for NAT traversal. Direct QUIC paths are preferred, relay fallback helps connectivity, and transferred bytes are verified locally with BLAKE3.

Lightning P2P

A GUI Magic Wormhole alternative for Windows and Android.

Magic Wormhole alternative

A GUI Magic Wormhole alternative for Windows and Android.

Direct answer

Magic Wormhole is a strong CLI file transfer tool. Lightning P2P serves users who want a graphical Windows and Android app with link and QR handoff, iroh connectivity, and BLAKE3 verification.

Magic Wormhole is a great CLI for moving files peer-to-peer with short codes. Lightning P2P brings a similar direct-transfer model to a Windows desktop app and Android sideload APK with QR/link handoff and nearby discovery.

Both tools keep transfers peer-to-peer. Lightning P2P adds a full GUI, QR-scannable tickets, a transfer history, and an Apache-2.0 licensed Rust codebase on GitHub.

Magic Wormhole pioneered the idea that short human-readable codes, PAKE, and direct file streams can replace cloud upload links. Lightning P2P keeps that spirit while targeting Windows and Android users who want a graphical app rather than a Python command line.

Like Magic Wormhole, Lightning P2P does not create a hosted cloud file bucket. The sender keeps the file on disk, the receiver pulls it over QUIC, and relay fallback helps when a direct path is blocked. Content is verified with BLAKE3 on the receiver before it is written to disk.

Where Lightning P2P differs: the app ships native Windows installers and an Android APK, generates copyable receive links and QR codes, keeps a local transfer history, and can include signed updater metadata on production releases. It is built on iroh and iroh-blobs, which are maintained Rust libraries for P2P QUIC transport and content-addressed blob transfer.

If you are comparing file transfer tools, also see the Lightning P2P benchmark plan, which lays out the test matrix for publishing honest speed comparisons across cloud upload, browser transfer, LAN-only apps, and command-line baselines.

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.

Frequently asked questions

Is Lightning P2P compatible with Magic Wormhole codes?: No. Lightning P2P uses iroh tickets, which are a different format. You cannot paste a Magic Wormhole code into Lightning P2P. The two tools solve a similar problem with different primitives.
Does Lightning P2P need a server like the Wormhole rendezvous?: Lightning P2P uses iroh discovery and relays for NAT traversal. Direct QUIC paths are preferred, relay fallback helps connectivity, and transferred bytes are verified locally with BLAKE3.