Where Does pyLoad Store Config and Downloads?
pyLoad keeps pyload.conf and its link database in ~/.pyload, with downloads in ~/Downloads/pyLoad. Paths and Docker mapping.
Last updated
pyLoad centers on a home folder with pyload.conf for core settings, a files database for links and accounts, plus plugin configs and extraction passwords. Downloads default to ~/Downloads/pyLoad, temp files to a platform scratch dir. The web UI edits most of it, but hand-editing the conf files works when the service won't start.
Docker installs split the same tree into /config and /downloads host mounts. Override either side permanently with --configdir and --changedir. Windows keeps user data under AppData Roaming instead of a dot folder, the one real platform difference.
Where pyLoad stores this, by platform
%APPDATA%\pyLoad
pyload.conf, plugins.conf and the files database here. Downloads default to %USERPROFILE%\Downloads\pyLoad. Edit conf files with the service stopped.
~/.pyload
Same contents as Windows despite the dot-folder style. Extraction passwords live in unrar_passwords.txt beside pyload.conf. Docker users map this tree to /config.
~/.pyload
Mirrors macOS exactly. Arch documents plugins.conf and unrar_passwords.txt in the same spot. Run with --configdir to relocate, --changedir to make it permanent.
Frequently asked questions
Where does pyLoad save downloaded files?
In ~/Downloads/pyLoad by default, settable in pyload.conf or the web settings. Docker maps it to the /downloads host volume. Point it at a big disk early since queues grow quietly.
How do I edit pyLoad settings when it won't start?
Open pyload.conf in the home folder above with a text editor while the service is stopped. Fix the offending key, then start normally. The web UI writes the same file, so both stay in sync.
Notice an outdated path? Let us know.