Where Does slskd Store Config and Downloads?
slskd reads slskd.yml in its app directory with downloads and shares in folders the config names.
Last updated
slskd configures from a YAML file in its application directory. Credentials, shares, and limits live in slskd.yml with environment overrides for containers. Downloads and incomplete files land in the folders it names.
Docker installs map these paths through volumes, which moves the real bytes onto host disks. Shares point at existing media folders by absolute path. Back up the YAML with any API keys stored beside it.
Where slskd stores this, by platform
~/.local/share/slskd/slskd.yml
Credentials, shares, and limits in one YAML file. Downloads follow the folders it names. Docker volumes remap these paths, so inspect mounts.
Frequently asked questions
Where do slskd downloads go?
Into the downloads folder named in slskd.yml, with incomplete parts beside it. Shares stay separate so uploads never mix. Point both at dedicated disks.
How do I run slskd in Docker?
Mount config, downloads, and shares as volumes from the host. Environment variables override YAML values. Keep the YAML in version control without secrets.
Notice an outdated path? Let us know.