What makes eMule Qt different
eMule Qt is not a reskin. The client was rebuilt from the ground up on Qt 6 and modern C++23, and that rebuild made room for capabilities the original could never have — while staying fully compatible with the same ED2K servers and the same Kademlia network you already use.
Everything listed below exists in eMule Qt and not in the original eMule.
| Feature | What it gives you |
|---|---|
| Cross-Platform | One codebase running natively on Windows, macOS and Linux. The original is MFC and Windows-only. |
| Daemon + GUI Split | A headless core you can run on a server or NAS, with the GUI attaching locally or over the network. |
| IPv6 Everywhere | Dual-stack ED2K, so IPv6-only and CGNAT users can take part as full peers instead of second-class ones. |
| Encrypted HTTP Cache | When several peers want the same part, spend your upstream once and hand the rest an encrypted URL. |
| Automatic Port Mapping | Three port-forwarding protocols raced at startup, graded on whether your exact port was really granted. |
| REST API & CLI Control | A JSON API and shell commands for scripts, dashboards and home automation. |
| Nothing Is Lost on Restart | Download sources, upload-queue positions and statistics history all survive a restart. |
All of it is free and open source under the GPL. The code, the protocol specifications and the issue tracker live on GitHub — and if something is broken, please send us a report.