Where Does Moonraker Store Config and Data?
Moonraker organizes everything under ~/printer_data: config in config/moonraker.conf, state in database/moonraker-sql.db, and logs in logs/moonraker.log.
Last updated
Moonraker keeps one data folder and everything hangs off it. The default is ~/printer_data on the Pi or host. Config, database, gcodes, logs, and backups each get a subfolder. Prebuilt images like MainsailOS and FluiddPi follow this layout, so guides written for one image transfer to others.
Two files matter most day to day. config/moonraker.conf is the service configuration next to printer.cfg. database/moonraker-sql.db holds persistent state including history and job data. Logs sit beside them, which makes one folder the whole story when something breaks.
Where Moonraker stores this, by platform
~/printer_data
Default data path with config, database, gcodes, logs, and backup beneath it. Older guides may show ~/klipper_config or ~/.moonraker_database instead, which are the same content under previous layouts, often as symlinks.
Frequently asked questions
How do I back up Moonraker?
Copy the whole printer_data folder with Moonraker and Klipper stopped. It holds config, database, gcodes, and logs in one tree. Restore goes to the same path on the new host, then fix any user name differences in paths before starting services.
Where is the Moonraker database?
The database is SQLite at database/moonraker-sql.db inside the data folder. Use the Moonraker API backup endpoints rather than copying the live file, and fetch the backup over SSH or SMB since Moonraker never serves database files over HTTP.
Notice an outdated path? Let us know.