On this page
A complete recovery set
Keep the n8n user folder, the actual database, deployment settings, and any external file or binary-data storage. Back up custom nodes when your workflows depend on them. Record the application version.
Preserve the encryption key
Credentials are encrypted. Recovering the database without its matching encryption key can leave those credentials unusable. Save the key securely outside the VPS; never paste it into a support ticket or AI chat.
Use a consistent backup
When using SQLite, copying a live database while writes continue can produce an inconsistent copy. Use the vendor's supported consistent backup approach. External PostgreSQL requires its own database backup. Workflow and credential exports do not include all users, settings, and execution history.
Verify recovery
Test on an isolated compatible instance before relying on the backup. Keep restored workflows from contacting real external systems during testing.