AMule files

From AMule Project FAQ
Jump to: navigation, search

English | Deutsch | Magyar | Nederlands

Most of aMule's config files and data are the same as or are compatible with eMule's.

Have in mind that you might not have all of them on your hard disk, since they are generated when needed.

Program Files

Here is a list and the usage of each of them (On Mac OS X the "~/.aMule" folder corresponds to "~/Library/Application Support/aMule"):

See also: Category:Program Files


  • ~/.aMule/aMule.tmpl: This was the template file which aMule WebServer used in version prior to aMule 2.0.0.
  • ~/.eMule: aMule's old personal configuration file (version prior to aMule 2.0.0). It was renamed to ~/.aMule/amule.conf.
  • ~/.aMule/known2.met: This file stored in older aMule versions the verified AICH hashes of your shared files.
  • ~/.aMule/muleconn: This file is a socket for aMule communications. It is no longer used since 2.1.0
  • ~/.aMule/server_met.old: Backup of server.met file.

Temporary Files

In the Temp directory (which is ~/.aMule/Temp by default but can be set to any other in Preferences), aMule will create, for each download in queue, the following files:

  • *.part: This file contains the downloaded parts (not chunks, since not completed chunks are also stored here) of the download. As aMule is able to download from more than one user at the same time, this file has the size of the complete file. The missing parts are filled with zeros.
  • *.part.met: This file contains information on the downloaded parts of the download, the verified chunks, the hash values of the remaining chunks, etc.
  • *.part.met.bak: This are backups of the *.part.met files. Every now and then aMule creates this backups since without the *.part.met file, a download has no meaning for aMule. If any *.part.met file "disappeared, you should rename the *.part.met.bak to *.part.met.
  • *.part.met.backup: This are temporal *.part.met while the data is being stored. As soon as aMule finishes writting the file, it is renamed to *.part.met.
  • *.part.met.seeds: This file only exists if you have enabled to store the IPs of sources of rare files in the preferences, so that aMule can try to connect to these sources again after a restart.


The directories in ~/.aMule/ have the following use:

  • ~/.aMule/Incoming/: By default, the directory where aMule stores the completed downloads (except on MacOS X).
  • ~/.aMule/Temp/: By default, the directory where aMule stores the non-completed downloads (temporary files).
  • ~/.aMule/webserver/: This directory contains the skins for aMuleWeb.
  • ~/aMule Downloads: The directory where aMule stored the completed downloads on Windows in old versions (previous to aMule 2.1.0).
  • ~/Documents/aMule Downloads: By default, the directory where aMule stores the completed downloads on MacOS X and Windows (since aMule 2.0.0).
  • <app_dir>/Incoming: In MacOS X and Windows, if aMule cannot determine the user's Documents folder, it will store the downloaded files here.