Where Does Self-Hosted Mautic Store Data?
Which Docker volumes hold Mautic config, logs, and media files, and what a full migration backup includes..
Last updated
Mautic's Docker images persist three volumes: config for local PHP settings, logs for app logs, and media for uploads and generated files. Database and queue services hold the rest outside the images. Bind mounts or named volumes both work with the same container paths.
Migrations copy volumes plus a database dump plus compose files for credentials. Cron helpers mount the same tree for scheduled sends. Keep media backups versioned; re-uploading thousands of assets by hand is nobody's idea of fun.
Where Mautic stores this, by platform
/var/www/html/config
Local PHP config plus logs and media trees in the official images. Database and queue persist in their own services outside these volumes. Back up volumes plus a DB dump and compose credentials together.
Frequently asked questions
how do I back up self-hosted Mautic
Back up the config, logs, and media volumes plus a database dump with the stack stopped. Media holds uploads while config holds local.php settings. Restore into matching volume names on the target host.
bind mounts or named volumes
Mount host folders onto the config, logs, and media container paths for direct file access. Named volumes work identically and survive better across hosts. Cron sidecars mount the same tree for scheduled jobs.
do volumes cover the database
No. The database and queue live outside these images in their own services. Dumps cover contacts and campaigns; volumes cover files and settings. Document the database credentials from compose beside the backup.
Notice an outdated path? Let us know.