> For the complete documentation index, see [llms.txt](https://docs.n8n.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.n8n.io/build/manage-workflows/view-change-history.md).

# View change history

{% hint style="info" %}
**Feature availability**

* Full workflow history is available on Enterprise Cloud and Enterprise Self-hosted.
* Versions from the last five days are available for Cloud Pro users.
* Versions from the last 24 hours are available for all users.
  {% endhint %}

Use workflow history to view and restore previous versions of your workflows.

## Understand workflow history <a href="#understand-workflow-history" id="understand-workflow-history"></a>

n8n creates a new version when you:

* Save your workflow.
* Restore an old version. n8n saves the latest version before restoring.
* Pull from a Git repository using [Source control](/administer/use-source-control-and-environments.md). Note that n8n saves versions to the instance database, not to Git.

Changes to workflow settings do not create a new version.

{% hint style="info" %}
**Workflow history and execution history**

Don't confuse workflow history with the [Workflow-level executions list](/build/understand-workflows/understand-executions/view-executions-for-a-single-workflow.md).

Executions are workflow runs. With the executions list, you can see previous runs of the current version of the workflow. You can copy previous executions into the editor to [Debug and re-run past executions](/build/understand-workflows/understand-executions/debug-executions.md) in your current workflow.

Workflow history is previous versions of the workflow: for example, a version with a different node, or different parameters set.
{% endhint %}

## View workflow history <a href="#view-workflow-history" id="view-workflow-history"></a>

To view a workflow's history:

1. Open the workflow.
2. Select **Workflow history** <img src="/files/EoOEXVrD6oXZnYDxkyaA" alt="Workflow history icon" data-size="line">. n8n opens a menu showing the saved workflow versions, and a canvas with a preview of the selected version.

## Restore or copy previous versions <a href="#restore-or-copy-previous-versions" id="restore-or-copy-previous-versions"></a>

You can restore a previous workflow version, or make a copy of it:

1. On the version you want to restore or copy, select **Options** <img src="/files/u571i29h1qOyVdUCmDJP" alt="Options icon" data-size="line">.
2. Choose what you want to do:
   * **Restore version**: replace your current workflow with the selected version.
   * **Clone to new workflow**: create a new workflow based on the selected version.
   * **Open version in new tab**: open a second tab displaying the selected version. Use this to compare versions.
   * **Download**: download the version as JSON.
   * **Name version**: give the version a name and description. Named versions are protected from automatic pruning. Refer to [Naming versions](/build/understand-workflows/save-and-publish-workflows.md#naming-versions) for more details. Available on Pro and Enterprise plans.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.n8n.io/build/manage-workflows/view-change-history.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
