Understanding n8n archive location?

The n8n archive location is the folder or volume where n8n saves archived workflows and related data. For many setups this is the n8n data directory or a Docker volume mapped to the container data path. This explanation helps people starting with automation to know where files live and why that matters.

n8n archive location overview

The n8n archive location usually refers to the data directory used by n8n. It can hold archived executions, workflow exports, and metadata. In Docker setups the archive often lives in a named volume or a host folder. In direct Node.js installs it is usually inside the user data folder for n8n.

How n8n stores data and archives

n8n keeps runtime data in a data directory. This includes workflow definitions, execution history, and any archived items. The system can store items in a database or as files, depending on configuration. Archiving means older executions are kept for reference or export.

Common Docker and Node.js setups

With Docker, many people map a host folder or use a named volume for persistence. That mapped volume becomes the effective archive location. With Node.js, n8n uses the local user data directory by default. Cloud or managed platforms may store archives in external storage or databases.

How to locate your n8n archive location

Check how n8n is deployed. If you use Docker, look for volumes or bind mounts in your container configuration. If you run Node.js directly, check the n8n config or the user data directory. If a database is used, archived execution details may be inside that data store.

Practical notes for beginners

Keep backups of the data directory or Docker volume to protect archives.
Use clear volume names or host paths so you can find archives later.
Document your deployment method so others know where archives are stored.

Summary

Knowing the n8n archive location helps you manage backups and recover workflows. For Docker it is usually a volume or bind mount. For Node.js it is the user data folder. Check your deployment settings to confirm the exact path.

Written by Neil

Neil is a true n8n geek who lives and breathes workflow automation. He dives deep into nodes, triggers, webhooks, custom logic, and self-hosting setups, sharing everything he learns about n8n on AutomationCompare.com. As part of a broader team of automation specialists, Neil focuses purely on mastering n8n and helping others unlock its full potential.