Generating and rendering images in Dify consumes a lot of storage space.

[wbext]

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.

Generating and rendering images in Dify consumes a lot of storage space. Could you tell me which folder in Dify these rendered images are stored in?

2. Additional context or comments

No response

[dosubot[bot]]

Generated and rendered images in Dify are stored in the directory mapped to ./volumes/app/storage on your host machine, which is mounted as /app/api/storage inside the Docker container. This is the main storage location for all user files, including images, when using the default local storage backend. You can change the storage backend (for example, to S3 or another cloud provider) by adjusting the STORAGE_TYPE and related configuration options if you want to manage storage differently or offload it from your server [docker-compose.yaml] [storage config].

There are configuration options for image upload limits and file sizes, but there are no built-in automated retention or cleanup features for old images. To manage storage space, you may need to periodically review and manually clean up files in the storage directory or use external scripts/tools to automate this process.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[wbext]

Where exactly are they stored?

[dosubot[bot]]

Generated and rendered images are stored in the main storage directory configured for your Dify deployment. By default, if you're using Docker, this is the ./volumes/app/storage folder on your host machine (mapped to /app/api/storage inside the container) reference. Dify does not use a dedicated subfolder for images—files are saved directly under this storage directory, with filenames and paths determined by the tool or workflow that generates them reference.

If you switch to a cloud storage backend (like S3 or Azure), the logical structure remains the same, but the files are stored in your configured bucket or container. If you need to manage storage space, you can review or clean up files directly in this directory.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}