Where Does Self-Hosted Padloc Store Data?
Where a self-hosted Padloc server keeps vault data, attachments, and logs, and which variables move them.
Last updated
A self-hosted Padloc server splits state three ways: vault data under PL_DATA_DIR, attachments under PL_ATTACHMENTS_DIR, and logs under PL_LOGS_DIR. Docker deployments bind these to named volumes, with attachments and logs as separate mounts. Defaults point beside the project for quick trials.
SMTP configuration enables verification mails that hosted Padloc otherwise provides. Backups need the data directory plus compose and env files; attachments reattach by path. Client apps encrypt everything before it ever reaches these folders.
Where Padloc stores this, by platform
/data
Server vault data controlled by PL_DATA_DIR, defaulting to ./data beside the project (/data is the common Docker choice). Bind to a named volume in production for clean upgrades. Back up together with attachments, compose file, and env file. SMTP variables live outside the data tree.
Frequently asked questions
how do I back up self-hosted Padloc
Stop the stack, then archive the data directory plus attachments and logs if wanted. Vault contents stay encrypted client side, so the backup guards availability rather than secrecy. Keep the compose file and env file with the backup for faithful restores.
how do I move Padloc data directories
Set PL_DATA_DIR, PL_ATTACHMENTS_DIR, and PL_LOGS_DIR to the desired paths before starting. Docker setups bind these to named volumes or host folders. Defaults sit beside the compose project, which suits testing more than production.
is self-hosting Padloc free
Yes for personal and non-profit use; commercial deployments need a license. The server handles sync and storage while encryption stays on clients. SMTP settings enable the account verification mails self-hosting otherwise skips.
Notice an outdated path? Let us know.