How To Update n8n to the Latest Version

Keeping your instance of n8n updated is crucial to take advantage of the latest features, performance improvements, security patches, and bug fixes. Whether you're self-hosting on Docker, Linux, Windows, or macOS, this step-by-step guide will show you how to update n8n to the latest version safely and efficiently. If you’ve ever asked yourself how to update n8n version, this guide has all the answers you need.

Why You Should Keep n8n Updated

Maintaining an up-to-date version of n8n ensures your workflows remain stable and secure. Here's why updating regularly is a good idea:

• Access new nodes and features: n8n frequently adds support for new apps and integrations.
• Get bug fixes: Improve stability and get rid of known issues.
• Enhanced performance: Speed and reliability often improve with new versions.
• Security patches: Critical for protecting your infrastructure, especially in cloud or public deployments.

What to Know Before You Update

Before we walk through how to update n8n version, let’s cover a few checks to keep everything running smoothly.

Backup Existing Workflows

Always backup before you upgrade.

• Export your workflows manually from the "Workflows" page.
• Or, automate it using cron and API calls. You can follow this workflow backup guide to backup n8n workflows automatically.

Check Current Version

You can find the current version of your n8n instance:

• Go to Settings inside the n8n UI (for hosted setups)
• Or run the following command in the terminal:

  n8n --version
  

How to Update n8n Version Based on Installation Type

n8n can be run in several environments. Let’s walk through how to update it for the most popular setups.

Docker Users

If you set up n8n using Docker, updating is relatively straightforward.

Step-by-step: Update n8n with Docker

1. Stop the running container

   docker stop n8n
   

2. Remove existing container (this won’t delete data if you've mounted volumes):

   docker rm n8n
   

3. Pull the latest n8n image

   docker pull n8nio/n8n
   

4. Start a new container with the latest image
   Make sure to reuse your original volume and environment variables:

   docker run -d 
     --name n8n 
     -p 5678:5678 
     -v ~/.n8n:/home/node/.n8n 
     -e N8N_BASIC_AUTH_USER=user 
     -e N8N_BASIC_AUTH_PASSWORD=password 
     n8nio/n8n
   

If you're using Docker Compose, just update the image and run:

docker-compose pull
docker-compose down
docker-compose up -d

For more persistent setups, learn how to install n8n in Docker with auto-restart and data volume.

Linux/Node.js (Manual Installation)

If you installed n8n via npm globally, here’s how to update it.

Step-by-step: Update Node/NPM n8n Installation

1. Stop the n8n process (if running as a service or PM2):

   pkill -f n8n
   

2. Update n8n globally:

   npm install -g n8n
   

3. Verify the update:

   n8n --version
   

   It should now show the latest version installed.

4. Start n8n again, either manually or using your process manager:

   n8n
   

For systemd-controlled services, make sure to reload the service.

Windows or macOS Users

If you're running n8n locally for testing or development, you can usually update it from your terminal.

Windows/macOS – Installed via npm

1. Open your terminal or Command Prompt

2. Run:

   npm install -g n8n
   

   If you see permission errors, try:

   sudo npm install -g n8n
   

3. To confirm:

   n8n --version
   

If you’re only running n8n temporarily for a test, check this guide to run n8n locally without a full server setup.

Updating n8n in a Cloud Environment

If you're hosting n8n on a cloud platform such as DigitalOcean or Google Cloud, your update process depends on the deployment method:

• In DigitalOcean App Platform, redeploy the Droplet or container using the new Docker image.
• On Google Cloud, SSH into the VM instance and use the appropriate Linux or Docker instructions.

Here’s a helpful DigitalOcean guide if that’s your platform.

Verifying a Successful Update

After updating, you should:

• Log into your n8n instance
• Visit the "Settings" → "Usage & Settings"
• Check the version number displayed at the bottom

You can optionally run this command:

n8n --version

Optional: Test Existing Workflows

To make sure updates didn't break automations:

• Run a few workflows manually
• Check for deprecated nodes or warnings in the logs
• Review failed executions in the execution history

Troubleshooting Common Issues After Update

Sometimes things break after an update—and that's normal. Here are a few quick fixes:

• Workflows not starting: Check environment variable changes in the latest release.
• Missing packages or nodes: If you rely on community nodes, you may need to reinstall community packages.
• Permissions issue (especially in Linux): Use sudo to ensure correct file ownership.

A restart often resolves minor glitches. Still stuck? Check the top n8n troubleshooting issues to fix problems fast.

Best Practices for Updating n8n

To maintain n8n with fewer headaches in future updates:

• Use persistent storage: Always mount volumes (~/.n8n) in Docker.
• Create backup automation: Schedule regular backups with a cron job and n8n API.
• Check changelogs before updating: Review breaking changes in n8n’s GitHub releases.
• Version pinning (optional): Useful for stability in production environments.

FAQ

How often should I update n8n?

Ideally, check for updates at least once a month or when a major new feature is released. Keeping current reduces technical debt and makes future updates smoother.

Will I lose my workflows after the update?

No, as long as your data directory (~/.n8n) is properly mounted or kept during an update, your workflows are preserved. Still, always make a backup.

What’s the safest way to update n8n in production?

Use Docker or Docker Compose with mounted volumes and environment variables. This setup isolates your app and makes rolling back easy if needed.

How do I roll back to a previous version?

If you use Docker, simply pull the previous version:

docker pull n8nio/n8n:0.228.1

Replace 0.228.1 with the version you want. Then recreate the container using that tag.

Does updating n8n change the database schema?

Sometimes, yes. Major updates may alter how data is stored. Always read the release notes and backup before updating.

Updating n8n ensures you get the most value out of this powerful workflow automation tool. Whether you're a solo developer, small team, or tech-savvy marketer, knowing how to update n8n version with confidence sets you up for long-term success.