Where Does Wallabag Store Articles and Images?
Wallabag persists articles in /var/www/wallabag/data in Docker, with saved images under web/assets/images. Back up both.
Last updated
Wallabag splits persistence in a way the compose file makes clear. The data volume holds config and the article database. A second volume holds downloaded article images. Skip the second one and your restores look complete until every picture 404s.
Host paths are your choice at deploy time. The official examples use /opt/wallabag/data and /opt/wallabag/images, but any host folder works. What matters is that both container paths are covered by a volume.
Where Wallabag stores this, by platform
/var/www/wallabag/data (inside container)
Container-side data volume. Holds config, parameters, and the SQLite file under data/db when SQLite is used.
/var/www/wallabag/web/assets/images (inside container)
Cached article pictures. Mounted separately in compose examples, commonly to /opt/wallabag/images on the host.
Frequently asked questions
How do I back up self-hosted Wallabag?
Copy /var/www/wallabag/data for the database and web/assets/images for cached pictures. MySQL and Postgres users also need a database dump. SQLite users already carry the .sqlite file inside data/db.
Where are Wallabag article images stored?
They live under web/assets/images, which is why the official compose file mounts it as a separate volume. Without it, restores show broken image icons on older entries.
Notice an outdated path? Let us know.