Where Does FileFlows Store Its Data?
FileFlows keeps its database and server.config in a Data directory. Docker mounts it at /app/Data; back up that folder.
Last updated
FileFlows centers on a Data directory holding the SQLite database (FileFlows.sqlite), server.config, plugins, and working state. The Docker image expects it at /app/Data, mapped to whatever host path you choose. Bare installs use a Data folder under the application directory instead.
Logs live nearby but matter less. Losing logs costs history context, while losing the Data directory costs the whole setup. Before upgrades, copy FileFlows.sqlite and server.config at minimum. The web console backup bundles database contents, key settings, and plugins into one snapshot, which is the easiest pre-upgrade habit.
Where FileFlows stores this, by platform
/app/Data (Docker volume)
FileFlows.sqlite plus server.config and plugins. Bind this tree to a host folder. Temp and logs directories are configured separately and do not need the same backup care.
%APPDATA%\FileFlows\Data
Same database and server.config layout as Docker. Copy FileFlows.sqlite and server.config before upgrades. The exact folder follows your install location.
Frequently asked questions
how do i back up fileflows docker
Copy the whole Data directory with FileFlows stopped (FileFlows.sqlite plus server.config). Restore by mounting it at the same container path. The built-in backup tool under Config admin covers the same files.
does fileflows need a persistent volume
Yes. Map the Data directory to a host folder or named volume. Without the mount every recreate starts with a blank server: no flows, no libraries, no history.
Notice an outdated path? Let us know.