Where Does Zipline Store Uploads and Settings?
Zipline self-hosted uploads folder, database file and env config on Linux.
Last updated
Zipline keeps three things in its data directory: the uploads folder with every shared file, the database file with users, URLs and stats, and the config (usually environment variables or a settings file beside compose). The dashboard edits most behavior, but the files are what you back up.
Uploads keep their random names on disk with metadata in the database mapping them to your links and folders. Copying the uploads folder alone restores bytes without links. Back up the directory whole, database included, with the service stopped or the database checkpointed.
Where Zipline stores this, by platform
./uploads and database file in your Zipline data directory
Mounted beside compose (exact host path from your volume lines; confirm with docker inspect). Settings live in env or the dashboard database. Keep the folder ownership matching the container user to avoid failed writes.
Frequently asked questions
where are Zipline uploaded files on disk
In the uploads folder of the data directory, under generated names. The share links, folders and expiry live in the database file next to it. Restore both together or links point nowhere.
how do I move Zipline to a new server
Copy the full data directory (uploads plus database) and the compose/env with secrets. Bring the stack up, check ownership on the uploads mount, and test an old link before updating DNS.
Notice an outdated path? Let us know.