Update n8n by running npm update -g n8n for npm installs or docker pull docker.n8n.io/n8nio/n8n for Docker. Always update incrementally through major versions to avoid breaking changes. Check your current version with n8n --version before updating and review the release notes for migration steps.
How to Update n8n to the Latest Version
Keeping n8n up to date ensures you have the latest nodes, bug fixes, security patches, and performance improvements. The update process differs depending on whether you installed n8n via npm or Docker. The most important rule is to never skip major versions — always update incrementally (e.g., from 0.x to 1.0, then 1.0 to 1.x) to ensure database migrations run correctly.
Prerequisites
- A running n8n instance installed via npm or Docker
- Access to the terminal or command line on your server
- A backup of your n8n database and workflows before updating
- Node.js 18+ installed if using npm
Step-by-step guide
Check your current n8n version
Check your current n8n version
Before updating, you need to know which version you are running. This determines whether you can jump straight to the latest version or need to update incrementally through major releases. Run the version check command and compare the output with the latest release on the n8n GitHub releases page or npm registry.
1# For npm installations2n8n --version34# For Docker installations5docker exec <container_name> n8n --version67# Check the latest available version on npm8npm view n8n versionExpected result: You see your current version number printed in the terminal, such as 1.42.0, and can compare it to the latest available version.
Back up your data before updating
Back up your data before updating
Always create a backup before updating n8n, especially before major version upgrades. If you are using the default SQLite database, back up the .n8n folder in your home directory. For PostgreSQL, create a database dump. This ensures you can roll back if something goes wrong during the update.
1# Back up the .n8n directory (SQLite)2cp -r ~/.n8n ~/.n8n-backup-$(date +%Y%m%d)34# Back up PostgreSQL database5pg_dump -U n8n_user -d n8n_db > n8n_backup_$(date +%Y%m%d).sql67# For Docker with a named volume8docker run --rm -v n8n_data:/data -v $(pwd):/backup alpine tar czf /backup/n8n_data_backup.tar.gz /dataExpected result: A timestamped backup of your n8n data directory or database is created and stored safely.
Update n8n via npm
Update n8n via npm
If you installed n8n globally via npm, updating is a single command. For minor and patch updates within the same major version, you can update directly. For major version jumps, you must update to the last release of each major version first, then move to the next major version. This ensures all database migrations run in the correct order.
1# Update to the latest version (same major)2npm update -g n8n34# Update to a specific version (for incremental major upgrades)5npm install -g n8n@1.0.067# After installing, restart n8n8n8n startExpected result: npm downloads and installs the specified n8n version. When you run n8n start, the new version launches and any pending database migrations run automatically.
Update n8n via Docker
Update n8n via Docker
For Docker installations, pull the latest image and recreate the container. Make sure your workflow data is stored in a Docker volume or an external database so it persists across container restarts. If you need to update incrementally, pull a specific tag instead of latest.
1# Pull the latest n8n Docker image2docker pull docker.n8n.io/n8nio/n8n34# Pull a specific version for incremental updates5docker pull docker.n8n.io/n8nio/n8n:1.0.067# Stop and remove the old container8docker stop n8n && docker rm n8n910# Start a new container with the updated image11docker run -d --name n8n \12 -p 5678:5678 \13 -v n8n_data:/home/node/.n8n \14 docker.n8n.io/n8nio/n8nExpected result: The new container starts with the updated n8n version. Open http://localhost:5678 and verify the version number in the bottom-left corner of the n8n UI.
Verify the update and test workflows
Verify the update and test workflows
After updating, confirm the new version is running and test your critical workflows. Open the n8n editor, check the version number displayed in the UI footer, and manually execute your most important workflows to confirm they still work correctly. Pay attention to any deprecation warnings in the execution output.
1# Verify version from command line2n8n --version34# Check the n8n health endpoint5curl http://localhost:5678/healthzExpected result: The version command returns the expected new version number. Your test workflows execute successfully without errors. The health endpoint returns a 200 OK response.
Complete working example
1#!/bin/bash2# n8n Update Script — safe incremental update with backup34set -e56echo "=== n8n Update Script ==="78# Step 1: Check current version9CURRENT_VERSION=$(n8n --version 2>/dev/null || echo "not installed")10echo "Current n8n version: $CURRENT_VERSION"1112# Step 2: Check latest available version13LATEST_VERSION=$(npm view n8n version)14echo "Latest n8n version: $LATEST_VERSION"1516if [ "$CURRENT_VERSION" = "$LATEST_VERSION" ]; then17 echo "Already on the latest version. No update needed."18 exit 019fi2021# Step 3: Back up the .n8n directory22BACKUP_DIR="$HOME/.n8n-backup-$(date +%Y%m%d-%H%M%S)"23echo "Creating backup at $BACKUP_DIR"24cp -r "$HOME/.n8n" "$BACKUP_DIR"25echo "Backup created successfully."2627# Step 4: Stop n8n if running as a service28if systemctl is-active --quiet n8n 2>/dev/null; then29 echo "Stopping n8n service..."30 sudo systemctl stop n8n31fi3233# Step 5: Update n8n34echo "Updating n8n to version $LATEST_VERSION..."35npm update -g n8n3637# Step 6: Verify the update38NEW_VERSION=$(n8n --version)39echo "Updated to n8n version: $NEW_VERSION"4041# Step 7: Restart n8n service if it was running42if systemctl is-enabled --quiet n8n 2>/dev/null; then43 echo "Restarting n8n service..."44 sudo systemctl start n8n45 echo "n8n service restarted."46fi4748echo "=== Update complete ==="49echo "Backup location: $BACKUP_DIR"50echo "Please test your workflows to confirm everything works."Common mistakes when updating n8n to the Latest Version Safely
Why it's a problem: Skipping major versions during update (e.g., jumping from 0.200 to 1.30)
How to avoid: Update to the last release of each major version first (e.g., 0.x → 1.0.0 → 1.x latest), then proceed to the next major version so all database migrations run in order.
Why it's a problem: Not backing up before updating and losing workflow data
How to avoid: Always run a backup of your .n8n directory or database dump before any update. Store the backup in a separate location from your server.
Why it's a problem: Using docker pull without recreating the container
How to avoid: After pulling a new image, you must stop and remove the old container, then create a new one. The existing container still uses the old image until replaced.
Why it's a problem: Updating n8n while workflows are actively executing
How to avoid: Wait for all running executions to complete or pause them before updating. Interrupted executions may leave data in an inconsistent state.
Best practices
- Always back up your database and .n8n directory before updating, especially before major version upgrades
- Update incrementally through major versions — never skip from 0.x directly to the latest 1.x release
- Read the release notes and changelog for each major version to understand breaking changes
- Test your critical workflows immediately after updating to catch any compatibility issues early
- Pin your Docker image to a specific version tag in production instead of using latest
- Schedule updates during low-traffic periods when workflows are not actively executing
- Keep your Node.js version up to date — n8n requires Node.js 18 or higher
Still stuck?
Copy one of these prompts to get a personalized, step-by-step explanation.
I need to update my n8n instance from version [CURRENT] to the latest version. I installed it via [npm/Docker]. What is the safest step-by-step process including backup and incremental major version updates?
Help me write a shell script that checks my current n8n version, creates a backup, and updates to the latest version safely with rollback support.
Frequently asked questions
Can I skip major versions when updating n8n?
No. You must update incrementally through each major version. For example, if you are on version 0.236, first update to 1.0.0, then to the latest 1.x release. Skipping major versions can cause database migration failures and data loss.
Will updating n8n delete my workflows?
No, updating n8n preserves your workflows and credentials as long as your data is stored in a persistent location such as the .n8n directory or an external PostgreSQL database. Always back up before updating as a precaution.
How do I roll back to a previous n8n version?
For npm, install the specific version with npm install -g n8n@VERSION. For Docker, pull the specific tag with docker pull docker.n8n.io/n8nio/n8n:VERSION. Restore your database backup before starting the older version to avoid migration conflicts.
How often should I update n8n?
Check for updates monthly. Apply security patches immediately. For major version updates, wait a week after release for any hotfixes, then update during a maintenance window.
Do I need to update community nodes separately?
Yes. Community nodes are managed independently. After updating n8n, go to Settings, then Community Nodes to check for available updates. Some community nodes may need updates to remain compatible with the new n8n version.
What happens if an update fails halfway through?
If the update process is interrupted, restore your backup and try again. For npm, reinstall the previous version with npm install -g n8n@PREVIOUS_VERSION. For Docker, run the container with the previous image tag.
Talk to an Expert
Our team has built 600+ apps. Get personalized help with your project.
Book a free consultation