Wyrmhole is a desktop app for sending files directly between people using the Magic Wormhole protocol. The sender selects files or folders and shares a generated code; the recipient enters that code, reviews the offer, and accepts. The project says transfers are end-to-end encrypted and PAKE-secured, and lists Windows, macOS, and Linux support.
What is Wyrmhole?
Wyrmhole is a graphical file-transfer application built on the Rust implementation of Magic Wormhole. It adds a desktop interface around the transfer process, with a live progress view, transfer history, a configurable download location, relay URL settings, and options for handling tarballs. The project describes its frontend as React and its backend as Rust with Tauri. These are published project details, not independent compatibility or performance tests. See the Wyrmhole repository and README and the project website.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
zdyCGTime 5FT/1.8M FireWire 400 to FireWire 400 6-6 ilink Cable 6 Pin to 6 Pin Firewire DV iLink... | $8.99 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
How do you send files with Wyrmhole?
- Choose what to send. Select files or folders in the app. The project says folders can be packaged automatically as a tarball.
- Start the transfer. Wyrmhole generates a code for the transfer. Share that code with the intended recipient through a separate channel.
- Have the recipient enter the code. The recipient enters it in Wyrmhole, reviews the offered transfer, and accepts it.
- Check the received files. Files are saved to the configured download directory, and the transfer appears in file history. The project describes live progress tracking for sending and receiving.
This is the workflow documented by the project; it should not be read as a report of hands-on testing.
Recommended Free Tools
Is Wyrmhole secure?
The Wyrmhole README describes transfers as end-to-end encrypted and PAKE-secured over Magic Wormhole. PAKE, or password-authenticated key exchange, is the protocol mechanism named by the project for securely pairing peers through a shared code. These are descriptions of the project’s stated design, not evidence of an independent security audit or a guarantee that every transfer will work on every network.
#1 Best Overall
- Firewire Cable, IEEE 1394a 400 Mbps Firewire Cable, 6P to 6P
- Provides data transfer rates up to 400 Mbps
- Connects FireWire devices to each other for peer-to-peer communications
- Plug and play
- Application: Video presentation and editing, desktop and commercial publishing, document imaging.
Peer-to-peer does not necessarily mean that no service participates in connection setup. Magic-Wormhole documentation describes a mailbox protocol and a transit-relay protocol: both peers must use the same mailbox server to communicate, even when the file data travels over a direct connection rather than through a relay. Wyrmhole also documents an option to set a custom relay server URL. The ecosystem overview does not establish that users can avoid all infrastructure, or that every transfer will be direct. See the Magic-Wormhole ecosystem documentation, whose summary reflects its best knowledge as of April 2025.
What happens when you send a folder?
Wyrmhole’s project materials describe application-level folder packaging as a tarball, with settings for tarball handling such as automatic extraction and folder naming. That should not be confused with native directory transfer in the underlying protocol. In the April 2025 ecosystem overview, Rust file-transfer v1 support is listed as partial; the documentation says it does not support text messages or directory transfer as protocol features. It notes that a tarball can be produced, but is not automatically unpacked by the other side. The app’s own folder and extraction options sit above those protocol capabilities.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Which platforms and features does Wyrmhole list?
The project website lists Windows, macOS, and Linux. That is the project’s stated availability, not a separate check of every operating-system version or release. The README also lists:
- Progress tracking and transfer history, including metadata and JSON export.
- A configurable download directory and custom relay configuration.
- Tarball extraction and folder-naming settings.
The README mentions multi-recipient sends as experimental upstream work and system-level dark mode on its roadmap. Treat these as experimental or planned rather than established stable features. The project’s published build requirements are stable Rust, Node.js 18 or later, and the relevant platform’s Tauri prerequisites.
What protocol support should you keep in mind?
The Magic-Wormhole ecosystem overview lists the Rust implementation’s core support as full, reconnect as partial, file-transfer v1 as partial, Dilation as proof-of-concept, and dilated transfer as unsupported. These labels are from documentation dated to April 2025, not a live compatibility test of current releases. For a particular use case, distinguish what Wyrmhole’s desktop app can package or display from what the underlying protocol supports natively, and check current project releases and documentation.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
