Where Does FlareSolverr Store Data?
FlareSolverr keeps no persistent data. Sessions live in memory and config arrives through environment variables, not files.
Last updated
FlareSolverr is stateless by design. It holds no database, no config file, and no cache directory. Active browser sessions live in memory and disappear when the container stops. Configuration arrives as environment variables (log level, timezone, port, browser timeout) in the compose file or run command.
That changes the backup story: there is nothing to back up. Recreate the container with the same environment and port mapping (default 8191) and it behaves identically. If challenges start failing after an update, check available RAM and the libseccomp version on Debian hosts before blaming config, since each solve spins up a real browser.
Where FlareSolverr stores this, by platform
(no data directory: stateless)
No data directory exists. Sessions are in-memory only; LOG_LEVEL, TZ, PORT, and BROWSER_TIMEOUT arrive as container environment. Nothing persists across recreates, and nothing needs to.
Frequently asked questions
what happens to flaresolverr sessions on restart
Nothing. Sessions exist in memory inside the running container and vanish on restart. The *arr apps request fresh solves as needed, so a restart only costs a few seconds of re-solving.
can i configure flaresolverr without a config file
Yes. LOG_LEVEL, TZ, PORT, HEADLESS, and BROWSER_TIMEOUT cover normal tuning through the compose file or docker run flags. There is no config file to mount, which keeps the container stateless by design.
Notice an outdated path? Let us know.