"n8n 3.0 is due in October 2026: what changes for a self-hosted install?"

We pay for the servers and plans we use. Links marked as affiliate links earn us a commission at no cost to you; it never changes what we recommend. Details.

n8n has published a list of what changes in version 3.0, and it is long enough that a self-hosted install should not take the upgrade on autopilot. This is the part that matters if you run n8n yourself on a small server: how you installed it, which nodes go away, which defaults tighten, and what to check before you change the image tag.

Watch it instead

The same list as a 3-minute video: n8n 3.0 breaking changes for self-hosted installs (YouTube). In 30 seconds each: npm installs end in 3.0 and the Code node gets 1 minute, not 5.

Is n8n 3.0 out?

Not yet. On 4 Oct 2026 the npm registry listed latest and stable as 2.41.6 (published 2 Oct) and beta as 2.42.2, and n8n's GitHub releases had no 3.x tag. You can check the same thing yourself:

npm view n8n dist-tags

If you run n8n in Docker, the version is in the image tag. Coolify's n8n template, for example, pins it: version 4.3.23 of the template uses image: n8nio/n8n:2.10.2, the version our n8n on a $6 server test ran. A pinned tag means 3.0 will not arrive on its own; you decide when to change it.

If you installed with npm or npx

This is the biggest change. n8n's page: "Self-hosted n8n will require a Docker-based deployment. n8n 3.0 will no longer support installations run using npm or npx n8n." The same page says step-by-step migration guidance "will be coming soon".

If your n8n runs from npm install -g n8n on a VPS, plan the move to Docker while you are still on 2.x, where both work. Back up first: the database and the .n8n folder, which holds the encryption key your saved credentials need (we explain why in our backup test).

Nodes that go away

n8n 3.0 "removes older nodes, modes, and helpers that newer patterns have replaced". The ones most likely to sit in an older self-hosted workflow, with the replacement n8n gives:

The full list is longer (AI memory and vector store nodes, SerpApi, Orbit and others). AI Transform nodes are migrated to Code nodes automatically. n8n's advice: "Before you update, Settings > Migration Report lists the affected nodes."

New defaults that can break a working setup

These change behaviour without any node being removed:

• Code node time limit. "The default for N8N_RUNNERS_TASK_TIMEOUT drops from 300 (5 minutes) to 60 (1 minute). Code node tasks that run longer fail." Set the variable back to 300 if you have long-running Code nodes.
• Community packages. "The default for N8N_UNVERIFIED_PACKAGES_ENABLED changes from true to false." Unverified community nodes stop being installable unless you turn it back on.
• Binary data folder. "On first start, n8n 3.0 renames ~/.n8n/binaryData to ~/.n8n/storage." If you mount a volume at the old path, mount it at the new one. "If both directories exist, n8n doesn't start." Nothing changes if you use the default paths without a separate mount.
• Compression node limits. The maximum decompressed size "drops from 2 GiB to 256 MiB" and the maximum number of zip entries from 5,000 to 1,000.
• SSRF protection. When SSRF protection is on and the block list contains default, 3.0 also blocks the shared address space 100.64.0.0/10 (used by carrier-grade NAT and by some VPNs, such as Tailscale) and IPv6 transition ranges. A workflow that calls a host there needs it added to N8N_SSRF_ALLOWED_IP_RANGES or N8N_SSRF_ALLOWED_HOSTNAMES.
• Chat Hub. n8n 3.0 turns the Chat Hub module off by default, and n8n 4.0 removes it.

A checklist before you change the tag

1. Note your current version and image tag.
2. Back up the database and the .n8n data (with the encryption key) and keep the backup off the server.
3. Open Settings > Migration Report and replace every listed node while still on 2.x.
4. Search your Code nodes for anything that runs over a minute, or set N8N_RUNNERS_TASK_TIMEOUT=300.
5. If you use unverified community nodes, decide whether to re-enable N8N_UNVERIFIED_PACKAGES_ENABLED.
6. Upgrade a copy first if you can. On a small server, a second n8n container for an hour costs almost nothing; see DigitalOcean droplet pricing for what an hourly droplet costs.

Would rather not run upgrades at all? n8n Cloud is the hosted version; n8n handles the version moves there.

FAQ

When is n8n 3.0 released?

n8n's breaking-changes page says it is scheduled for October 2026. On 4 Oct 2026 the latest stable release was 2.41.6 and there was no 3.x release on npm or GitHub.

Can I still install n8n with npm after 3.0?

No. n8n says 3.0 will no longer support installations run with npm or npx, and self-hosted n8n will require a Docker-based deployment.

Will my Function and Cron nodes still work in n8n 3.0?

No. Both are removed. Replace Function and Function Item with the Code node, and Cron and Interval with the Schedule Trigger node. Settings > Migration Report lists the affected nodes before you upgrade.

Why do my Code nodes time out after upgrading to n8n 3.0?

The default task timeout drops from 300 seconds to 60. Set N8N_RUNNERS_TASK_TIMEOUT back to 300, or split the work into shorter steps.

Sources

• n8n: v3.0 Breaking changes (read 4 Oct 2026)
• n8n on npm and n8n releases on GitHub (checked 4 Oct 2026)
• Coolify's n8n template, v4.3.23