Where Does Self-Hosted Overleaf Store Data?
Self-hosted Overleaf keeps project data in container volumes with host paths from the Toolkit config, plus Mongo and Redis beside them.
Last updated
Self-hosted Overleaf splits persistence three ways. Project filesystem with history and compiles, Mongo for users and projects, Redis for sessions and live edits. The Toolkit maps host folders into fixed container paths per its rc file.
Host locations vary by configuration while container paths stay constant. Legacy compose mounts differ from Toolkit defaults, so check the rc file before assuming. S3 can substitute for the filesystem leg without changing the other two.
Where Overleaf stores this, by platform
/opt/overleaf-toolkit/config/overleaf.rc
Toolkit variables mapping host data folders into container paths, with env and version files beside the rc. Legacy compose mounts use home-directory variants. Check configured paths before archiving.
/var/lib/overleaf
In-container project store with history and compiles, mounted from Toolkit-configured host data. Mongo and Redis persist beside it. S3 backends replace this leg when configured.
Frequently asked questions
How do I back up self-hosted Overleaf?
Archive the filesystem volume with Mongo and Redis persistence together. The Toolkit maps host data folders into container paths per its rc file, with legacy compose using home-directory mounts. Back up all three stores or restores come back hollow.
Where is the Overleaf Toolkit config?
Edit the Toolkit rc file for top-level variables with env and version files beside it. Host data paths configure there rather than in container files. Compose overrides extend the stack without touching the base.
Is /var/lib/overleaf on my host?
Inside containers only. The bare host path names the mount target rather than a host folder, with the host side varying by rc settings and compose volumes. S3 backends can replace the filesystem store entirely.
Notice an outdated path? Let us know.