What is eMuleBB Rust?
eMuleBB Rust is an open-source client for the eD2K and Kad file-sharing networks, written in Rust. A background application handles connections, searches and transfers, while you operate it through a browser console. An authenticated REST API is available for integrations.
The console lets you search, follow downloads and uploads, and manage the folders you choose to share. This can suit a computer that runs continuously while you use another device to check its progress. The project is developed by the eMuleBB community. Read the project overview.
Beta status and eMule versions
eMuleBB Rust has its own builds and documentation. The eMuleBB organisation also maintains a Windows client, while the familiar eMule stable and Community branches have their own releases. Check which project a download belongs to before following setup instructions. eMuleBB project map.
The Rust client is in active beta. Its API and profile database can change between builds, so testers should read compatibility notes and preserve the stopped profile and matching application before an upgrade. This overview follows the public project documentation reviewed on 18 November 2026.
Platforms and downloads
Choose a package for the computer that runs the client. The device displaying the browser console can be different. Prebuilt native packages do not require a Rust compiler. The project documents these choices.
- Windows has x64 and ARM64 ZIP packages.
- Linux has x64 and ARM64 packages, including DEB, AppImage and musl archives.
- macOS has packages for Intel and Apple Silicon.
- Docker / OCI images are available for Linux amd64 and arm64.
- Android has an experimental APK and native shell packages. Read the current platform-specific limitations before trying them.
Use the maintained nightly releases and compare the selected package with its published checksums. Check system requirements and the installation procedure in the platform and download guide.
Before your first launch
- Choose a separate profile for testing. Keep your existing client settings and unfinished downloads backed up. Follow the selected build's profile instructions.
- Keep the complete package together. The browser console needs the accompanying WebUI files. Launch the application using the instructions for your platform.
- Review access to the console. Configure your own API key and restrict access to trusted devices. The control interface handles client settings and transfers.
- Check networks and shared folders. Inspect eD2K and Kad states, the selected interface and the directories the client will share. Use a small folder whose contents you have reviewed for an initial test.
- Stop cleanly before updating. Preserve the profile, downloaded data and matching old application. Read compatibility warnings before starting a newer beta.
The project's getting-started guide explains authentication, network status, sharing and update precautions.
Contribute or report a problem
The maintainers welcome contributions to the client, browser console, tests and documentation. Read the contribution guide and coordinate the scope of a change through the project's public work items. A useful issue identifies the build, platform and steps that reproduce the problem. Review diagnostic information before posting it publicly. Contribution guide · Issue tracker.
