Hi,
I have 2 upload fields in my trigger, one for a video file and one for an audio file.
The video files are usually 100-300MB and this seems to be breaking the form upload. It loads and loads and then gives me a “Problem submitting response” page with no additional feedback. When I upload smaller files (<50MB) it works fine. This happens on the test & production URL. I could not find any mention of max. file upload size in the docs, so I’m wondering if I can do anything about it.
Thank you!
@danielkurz
You can look at
Endpoints environment variables | n8n Docs.
| Variable | Type | Default | Description |
|---|---|---|---|
| N8N_PAYLOAD_SIZE_MAX | Number | 16 | The maximum payload size in MiB. |
| N8N_FORMDATA_FILE_SIZE_MAX | Number | 200 | Max payload size for files in form-data webhook payloads in MiB. |
Also if using a reverse proxy (e.g., Nginx or Traefik), you also may need to configure its client_max_body_size or equivalent to allow larger uploads.
Samuel
Thank you! I’m on the cloud version though, not self hosted. Not sure this applies too because I’ve uploaded audios with 60MB
@danielkurz hmm, cloud version u can’t control this, and am not sure of the limits on cloud for these settings, you can try using google drive, and upload there first, then pull the file test and see if it handles 100mbs okay etc, if ure using basic version of n8n cloud u maybe hitting limits
for exmaple if ure on starter
Current plans:
Legacy plans:
if your on starter only running 320mb ram, maybe hitting these limits. I would personally try the google drive way see if ure instance can handle the 100mb okay, if okay then either use that way, or try reachout to n8n cloud support see if any other limits maybe happening.
Hope that helps,
Samuel
If you wanted to dig bit deeper, u can open dev tools in browser, and try see the actual reponse ure getting, may indicate timeout or something and not just the generic error message etc. It may show why let me know how you get on, maybe a simple issues.
yeah I’m getting a “413 Request Entity Too Large” error, so I might have to upgrade my plan.
AM not sure if upgrading will help, but worth a try this limit isn’t ram specify but more service based 413 limit is enforced by n8n Cloud’s internal infrastructure, they may allow larger on next plan but am not 100 percent sure, personally alot of people just use s3, onedrive or google drive, it should work fine with that, ie ure form u just provide the url, and have a node that downloads it maybe best workaround.
Samuel
yeah those are good ideas. I’ll reach out to the cloud support first.
thanks for getting back to me so quickly! cheers man
ure welcome 
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.