Help: Any method on how to increase the user input's file list (multiple files upload)?

[maassaam213-lab]

Self Checks

• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

Hi I'm a beginner and learning how to use Dify here.

I have a case where user would like to upload multiple files (Maximum of 80 files) and cross check with criteria listed in knowledge base file. The files contain information team members previous work experience, and knowledge base file contains a list of keywords to help Dify screens the person with right work experience.

The user input nodes have a limit of 10 files, are there a way to increase the limit of number of files? (Given that I will be using the cloud edition).

Best Regards

2. Additional context or comments

No response

[dosubot[bot]]

Hi @maassaam213-lab! I'm Dosu and I’m helping the dify team.

Unfortunately, on the Dify cloud edition, the 10-file upload limit cannot be increased — environment variables are not accessible to cloud users [1].

If you need to support up to 80 files, your options are:

1. Switch to self-hosted Dify — This gives you full control. You'd need to:

• Set the WORKFLOW_FILE_UPLOAD_LIMIT environment variable to your desired max (e.g., 80) and restart containers [2]
• Then open each workflow in the UI, go to the file upload settings, drag the slider up to the new maximum, and save the workflow — this persists the limit to the database [3]

Note: the env var only controls the UI slider's max value; the actual runtime enforcement is per-workflow and stored in the database, so both steps are required.

2. Workaround on cloud edition — You could split the workflow into multiple batches (e.g., upload 10 files at a time across multiple runs), then aggregate results in a downstream step. This is less elegant but works within the current constraint.

For your use case (screening 80 résumés against a knowledge base), the self-hosted route with an increased limit would be the most straightforward path. The self-hosted edition is free and open-source — you'd just need to manage the infrastructure yourself.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.