Where Is the AdGuard Home Config File?
AdGuard Home stores settings in AdGuardHome.yaml in its working dir, editable only while stopped.
Last updated
AdGuard Home writes AdGuardHome.yaml into its working directory on first run: the binary's folder for manual installs, /etc/adguardhome on OpenWrt, or the confdir volume for Docker. Query logs, stats, and filters live beside it in the work dir. Flags -c and -w relocate either piece.
The stopped-edit rule is the gotcha the wiki states plainly. Editing while running loses, every time, because shutdown persists memory over disk. Syntax errors are the top startup failure, so validate YAML before restarting remote boxes you cannot easily reach.
Where AdGuard Home stores this, by platform
<install-dir>/AdGuardHome.yaml
AdGuardHome.yaml plus query logs and filters in the work dir. -c and -w flags relocate. Docker splits confdir and workdir volumes.
<install-dir>/AdGuardHome.yaml
Same file and flags on macOS installs. Stop the service before editing.
<install-dir>\AdGuardHome.yaml
Same layout for Windows service installs. Edit stopped, then restart the service.
Frequently asked questions
My AdGuardHome.yaml edits keep reverting. Why?
Stop the service first, edit, then start. The running process overwrites the file on shutdown with its in-memory state, silently discarding hand edits made while it runs.
How do I run AdGuard Home with custom paths?
Pass -c for the config path and -w for the working directory. Docker setups split them into confdir and workdir volumes. The OpenWrt package defaults to /etc/adguardhome and /var/lib/adguardhome.
Notice an outdated path? Let us know.