How to Update OpenClaw: Every Method Explained [2026]

Pre-Update Checklist

Before updating OpenClaw, run through this checklist to minimize risk. Most updates are seamless, but taking 5 minutes for preparation can save you hours of troubleshooting if something goes wrong.

1. Check the changelog. Read the release notes for the version you are updating to. Look for breaking changes, deprecated features, or known issues. The changelog is available on the OpenClaw GitHub releases page.

2. Back up your data. This is the most important step. Copy your data directory, configuration files, and .env file to a safe location:

# Create a timestamped backup
BACKUP_DIR=~/openclaw-backup-$(date +%Y%m%d-%H%M%S)
mkdir -p $BACKUP_DIR

# Copy essential files
cp -r ~/openclaw/data $BACKUP_DIR/
cp ~/openclaw/.env $BACKUP_DIR/
cp ~/openclaw/docker-compose.yml $BACKUP_DIR/ 2>/dev/null
cp -r ~/openclaw/config $BACKUP_DIR/ 2>/dev/null

echo "Backup created at $BACKUP_DIR"

3. Note your current version. Record the version you are running before updating, so you know what to rollback to if needed:

openclaw --version

4. Check community reports. Wait 24-48 hours after a release before updating production instances. Check the OpenClaw GitHub issues, Discord, and Skool community for reports of problems with the new version.

5. Schedule a maintenance window. Don't update during business hours if your agent handles important tasks. Update during a low-activity period and verify everything works before returning to normal operations.

Method 1: Docker Update

Docker is the safest and most common update method. The process takes about 30 seconds and involves zero data loss because your data lives in mounted volumes separate from the container.

# Navigate to your OpenClaw directory
cd ~/openclaw

# Pull the latest image
docker compose pull

# Recreate the container with the new image
docker compose up -d

# Verify the update
docker compose exec openclaw openclaw --version

# Check logs for startup errors
docker compose logs -f --tail=50 openclaw

What happens during this process:

1. docker compose pull downloads the latest OpenClaw image from Docker Hub. This does not stop your running container.
2. docker compose up -d stops the old container, creates a new one from the updated image, and starts it. Your mounted volumes (data, config) are attached to the new container automatically.
3. The downtime is typically 5-15 seconds — the time between stopping the old container and starting the new one.

If the new version has database migrations or schema changes, OpenClaw runs them automatically on first startup. Check the logs for migration messages.

Method 2: npm Update

If you installed OpenClaw via npm (without Docker), update using npm:

# Stop OpenClaw first
sudo systemctl stop openclaw  # if using systemd
# or
openclaw stop

# Update the global package
npm update -g openclaw

# Verify the new version
openclaw --version

# Start OpenClaw
sudo systemctl start openclaw
# or
openclaw start

If npm update -g does not install the latest version (npm can be conservative about major version bumps), use install instead:

npm install -g openclaw@latest

For nvm users: If you installed Node.js via nvm, omit sudo from all npm commands. nvm installs packages in your home directory where you already have permissions.

Method 3: Mac App Update

The OpenClaw Mac app supports automatic updates. When a new version is available, you will see a notification in the menu bar.

Automatic updates (default): The app downloads the update in the background and prompts you to install it. Click "Install Update" and the app restarts with the new version. Total downtime is under 10 seconds.

Silent auto-updates: In Preferences, enable "Install updates automatically." The app will download and apply updates during low-activity periods without prompting you.

Manual update: If automatic updates are disabled, download the latest version from the OpenClaw releases page, open the .dmg file, and drag the new app to your Applications folder to replace the old version. Launch the app and it will migrate your data automatically.

Check for updates manually: Click the menu bar icon, then "Check for Updates."

Method 4: Hostinger Docker Manager

If you deployed OpenClaw through Hostinger's Docker Manager (a popular managed hosting option for non-technical users), the update process is done through Hostinger's control panel.

1. Log into your Hostinger dashboard
2. Navigate to Docker Manager
3. Find your OpenClaw container
4. Click "Update" or "Pull Latest Image"
5. Click "Recreate Container"

Hostinger preserves your volumes and environment variables during the recreation. Check the OpenClaw web dashboard after the update to verify everything is working.

Version Pinning

By default, openclaw/openclaw:latest always points to the newest release. For production stability, consider pinning to a specific version:

# docker-compose.yml
services:
  openclaw:
    image: openclaw/openclaw:3.23.2  # pinned version
    # ... rest of config

With a pinned version, docker compose pull only downloads that specific version, protecting you from unintended updates. When you want to update, change the version tag and run docker compose pull && docker compose up -d.

For npm:

# Install a specific version
npm install -g openclaw@3.23.2

Version pinning is recommended for production deployments. Use latest for development and testing where you want to stay on the cutting edge.

How to Rollback

If an update causes problems, rollback to the previous version immediately. Don't try to fix a broken update in production — rollback first, then investigate.

Docker rollback:

cd ~/openclaw

# Stop the current container
docker compose down

# Edit docker-compose.yml to use the previous version
# Change: image: openclaw/openclaw:latest
# To:     image: openclaw/openclaw:3.22.1  (your previous version)

# Pull and start the old version
docker compose pull
docker compose up -d

npm rollback:

openclaw stop
npm install -g openclaw@3.22.1  # your previous version
openclaw start

Mac app rollback: Download the previous version from the GitHub releases page. Install it over the current version.

Restore data if needed: If the update ran database migrations that changed your data format, you may need to restore from your pre-update backup:

# Stop OpenClaw
docker compose down

# Restore backup
cp -r ~/openclaw-backup-20260324-120000/data ~/openclaw/data

# Start with old version
docker compose up -d

Reading the Changelog

Before every update, check what changed. The OpenClaw changelog is available on GitHub at the Releases page. Here is what to look for:

• Breaking Changes: These require action on your part — configuration changes, deprecated features removed, or API changes that affect custom skills.
• Security Fixes: Update promptly when security patches are released. These fix vulnerabilities that could be exploited.
• New Features: Nice to have but not urgent. Update at your convenience.
• Bug Fixes: If the fix addresses a bug you are experiencing, update. Otherwise, treat as a normal feature update.
• Dependencies Updated: Usually safe, but occasionally a dependency update introduces compatibility issues. Wait for community feedback.

Recommended Update Schedule

Here is a practical update schedule that balances staying current with maintaining stability:

• Security patches: Update within 24-48 hours of release. These are typically small changes with minimal risk of breakage.
• Minor versions (e.g., 3.22 to 3.23): Wait 2-3 days for community feedback, then update during a planned maintenance window.
• Major versions (e.g., 3.x to 4.x): Wait 1-2 weeks for the community to identify and report issues. Read the migration guide carefully. Test on a non-production instance first if possible.
• Maximum lag: Never fall more than 2 minor versions behind the current release. Being too far behind makes eventual updates harder due to accumulated breaking changes.

Set up notifications for new OpenClaw releases. You can "Watch" the GitHub repository (select "Releases only") to receive email notifications when new versions are published.