aMule

aMule is an eMule-like client for the eDonkey and Kademlia networks.

Forum | Documentation | FAQ

Overview

aMule is a multi-platform client for the eD2k / Kad file-sharing network, originally a fork of the Windows client eMule (via xMule and lMule). aMule started in August 2003.

Supported platforms today: Linux, FreeBSD, OpenBSD, macOS, and Windows (MSYS2 / mingw-w64), on both x86_64 and ARM64.

aMule aims to stay close to eMule in look-and-feel so users moving between the two have minimal friction. New eMule protocol-level features are generally adopted into aMule shortly after.

---

Distributions

---

Development Statistics:

Features

• amule — all-in-one GUI client.
• amuled — headless daemon, no GUI.
• amulegui — remote GUI; connects to a local or remote amuled over the EC (External Connection) protocol.
• amuleweb — HTTP interface to a running amuled.
• amulecmd — interactive CLI for a running amuled.

Compiling

aMule uses CMake. Quick start:

cmake -B build -DBUILD_MONOLITHIC=YES -DBUILD_REMOTEGUI=YES
cmake --build build -j"$(nproc)"
sudo cmake --install build

See docs/INSTALL.md for the full list of dependencies, build options (BUILD_DAEMON, BUILD_AMULECMD, ENABLE_NLS, ENABLE_UPNP, ENABLE_IP2COUNTRY, etc.), and platform-specific notes. The CI workflow .github/workflows/ccpp.yml is the authoritative reference for the exact deps and flags used to build aMule on Linux, macOS, and Windows.

Setting Up

aMule comes with reasonable default settings and should be usable as-is. However, to receive a HighID you need to open aMule's ports on your firewall and/or forward them on your router. See the network connectivity guide for details.

Reporting Bugs

If you find a bug or miss a feature, please open an issue on GitHub (preferred) or report it on the forum. A good bug report includes the exact aMule version (amuled --version), the platform you're on, and steps to reproduce. See the bug report guide for detailed instructions on attaching backtraces and reproducer steps.

Contributing

Contributions are always welcome!

See the contributing guide for how to get involved. In short:

• Code — fix a bug, implement a feature, improve performance. The preferred path is a pull request on GitHub; patches on the forum also work.
• Translation — translate aMule, its documentation, or its website into your language.
• Documentation — help improve the project documentation at amule-org.github.io/docs.