Most users never need queue mode. Knowing what it is helps you decide.
Normal mode
One n8n process runs the editor, triggers and executions. This is fine for many small and medium workloads.
Queue mode
The main instance receives triggers and puts jobs in a queue. Separate worker processes pick up jobs and run them. Queue mode uses Redis for the queue and a proper database such as PostgreSQL.
When to consider it
- Many executions at once.
- Long or heavy workflows slowing others.
- A need for more reliability and horizontal scaling.
Before scaling
Optimise first: batch large lists (looping), split heavy tasks (sub-workflows) and prune execution data.
Cost of complexity
More parts mean more to monitor and secure. Do not adopt it for a handful of workflows.
Verify
Check n8n’s current documentation for requirements and settings.
Quick answers
What is queue mode?
A setup where a main instance queues jobs and workers run them.
What does it need?
Redis and a proper database such as PostgreSQL.
Do I need it?
Most small setups do not.
Related reading
- How to Self-Host n8n with Docker: A Practical Overview
- n8n Security Checklist: Credentials, Webhooks and Access
- How to Back Up and Update n8n Safely
Ready to turn n8n into a real skill?
Join a practical, trainer-led n8n course with projects like lead capture, notification flows, an AI step and a tool-using agent. Ask for a free counselling call to see if it fits your goal.
See the 15-day n8n training | Find your city | Book free counselling