Managed n8n Handles Large Files Without Crashing Its Database
A large file in a workflow now fails only the execution that handled it, instead of running your n8n database out of memory.
What's changed
- The files your workflows store are capped at a size your plan's database can safely hold, and an oversized file fails its own execution with n8n's file-too-large error instead of crashing the database
- The cap grows with your plan's database, so larger plans can store larger files
- n8n and its workers get a memory heap sized to their container, instead of topping out at about a quarter of it
- This applies to every managed n8n instance automatically