n8n 3.0 Beta Review 2026: Breaking Changes Self-Hosted Workflows Pricing and Migration Limits

n8n 3.0 beta arrived on October 27, 2026, with Docker images only. The release prioritizes reliability and security through legacy removal and stricter defaults rather than added features. Self-hosted users face a one-way upgrade that blocks rollback without a full backup restore.

n8n 3.0 Beta Review 2026: Self-Hosted Workflow Changes

Deployment now requires Docker. The npm and npx install methods no longer work, though Kubernetes and Helm setups remain supported. In-memory binary data handling has been removed, forcing use of filesystem or external storage such as S3. Manual executions in queue mode now run exclusively on workers.

Code node timeouts dropped from five minutes to one minute by default. Decompression limits tightened to 256 MiB maximum size and 1,000 zip entries. Encryption key rotation stays enabled at all times, the SSRF block list expanded, and unverified community packages are disabled by default.

Many legacy nodes have been deleted. Workflows containing Function, Function Item, Item Lists, Cron, Interval, older OpenAI nodes, legacy AI Agent modes, HTML Extract, Read Binary Files, Write Binary Files, Read PDF, iCalendar, or Workflow Trigger nodes will fail to activate. The $getPairedItem helper is also gone. Automatic migration assists cover some replacements through the Code node or Split Out and Aggregate nodes.

Migration Limits and Process for n8n 3.0

The migration report in Settings becomes available from version 2.39 onward. It scans workflows and flags problems by severity: upgrade blocked, executions fail, behavior changes, or capability removed. Users can apply suggested fixes, mark items as won’t fix, export a CSV, and track compatibility progress.

Recommended sequence starts with an update to the latest 2.x release, followed by report review and fixes. A full backup must precede any staging test. Production upgrade occurs only after successful staging validation. One.x reaches end of support on December 31, 2026, with no direct path to 3.x. Version 2.x receives security fixes for twelve months after the stable 3.x launch expected in early December.

Execution counts remain unchanged by the 3.0 beta. Community edition stays free with server hardware as the only constraint. Cloud plans retain their existing quotas, and AI Assistant credits saw a 30 percent reduction in late September. No migration-specific pricing or execution caps appear in the current release notes.

Practical Steps Before Upgrading to Stable 3.x

Test the beta on non-production instances immediately. Review the full list of removed nodes against active workflows and apply replacements where available. Confirm that all external storage references point to filesystem or S3 instead of in-memory mode. Schedule the final upgrade only after the migration report shows zero blocking issues and staging tests complete without errors. Follow official release notes for any post-beta adjustments before the early December stable release.