> For the complete documentation index, see [llms.txt](https://www.one.thezero.club/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.one.thezero.club/guide/installation/updating.md).

# Updating

We take great care to make Zero One updates as safe and straightforward as possible. In most cases, updating is simply a matter of replacing a few folders and files.

{% hint style="info" %}
Before updating, always check the [changelog](/changelog.md) for release-specific instructions.
{% endhint %}

{% hint style="warning" %}
If you are updating from a version older than the oldest version documented in the changelog, please [get in touch with us](/support.md) before updating.
{% endhint %}

{% hint style="danger" %}

## Before You Update

### Create a Backup

Before any update, create a backup of your website files.

If you are unsure about any update step, having a backup allows you to quickly revert to a working version.

### Never Overwrite Your Content

**Never overwrite the `content/` folder.**

This folder contains your website content, pages, files, and uploaded media.

### Review Custom Changes

Be careful when updating:

* `site/config/` website configuration files
* `site/languages/` website language(s)
* `site/theme/` [custom overrides](/guide/theme-extending.md) (if you have any)

If you made custom modifications to these files, compare them with the new version before overwriting anything.
{% endhint %}

### Understanding Updates

Not all updates are the same.

Each release in the [changelog](/changelog.md) is marked with an update type.

#### 🟢 Standard Update

A routine update that usually only requires replacing the files and folders listed in the changelog.

No additional manual steps are required unless stated otherwise.

#### 🟡 Configuration Update

Requires one or more manual configuration changes in addition to updating files.

Examples include:

* new configuration options
* updated configuration settings
* new panel options
* asset-related settings

Configuration Updates should not be skipped.

#### 🔴 Migration Update

Requires manual changes beyond normal file and configuration updates.

Examples include:

* structural theme changes
* template or blueprint changes
* plugin migrations
* asset restructures
* compatibility-related changes

{% hint style="danger" %}
Migration Updates must never be skipped.
{% endhint %}

```
Quick rule:
 
🟢 Standard Update = update files
 
🟡 Configuration Update = update files + configuration
 
🔴 Migration Update = update files + structural changes
```

***

### Which Instructions Should I Follow?

When updating from an older version:

1. Complete all 🔴 **Migration Updates** released after your current version.
2. Follow the instructions from all 🟡 **Configuration Updates** released after your current version.
3. Finally, update to your target version.

**Example**

**Current version:** `5.1.0`\
**Latest version:** `5.4.1`

**Required Updates**

1. 🔴 Update to **5.2.0** (Migration Update)
2. 🟢 Update to **5.4.1** (Standard Update)

**Additional Instructions Required**

Before updating to **5.4.1**, also follow:

* 🟡 Configuration Update instructions from **5.3.0**
* 🟡 Configuration Update instructions from **5.4.0**

**Important**

* 🔴 Migration Updates must be completed in order.
* 🟡 Configuration Updates do not require installing that version, but their instructions must be followed.
* 🟢 Standard Updates can be safely skipped unless they are your target version.

***

### Standard Update Procedure

Most Zero One updates require updating some or all of these:

* **`assets/`**
* **`kirby/`**
* **`site/plugins/`**
* **`composer.json`**

The exact files and folders are always listed in the [changelog](/changelog.md) entry.

Simply follow the update instructions for the specific version you are installing.

***

### After Updating Assets

If the update includes changes to the `assets/` folder:

1. Open the Site Styling section in the Panel.
2. Enable Style Compiler.
3. Save.
4. Open or refresh any frontend page.
5. Wait for the stylesheet to be regenerated.
6. Disable Style Compiler.
7. Save again.

***

### Alternative Update Method

Some users prefer updating by starting with the new Zero One version and moving their existing content into it.

The process is:

1. Download the latest Zero One version.
2. Create a backup.
3. Copy your existing `content/` folder into the new installation.
4. Review any custom configuration changes before going live.

This is entirely optional but can be useful when performing larger upgrades.

***

### Need Version-Specific Instructions?

All release-specific instructions, migration steps, fixes, and new features are documented in the Changelog.

👉 [**Read the changelog**](/changelog.md) **before every update.** 

**👉** [**Get in touch with us**](/support.md) **for specific instructions.**