[GH-ISSUE #13450] feat: Support storing images from conversations to S3 and directly using S3 links when reading #120225

New Issue

2026-05-20T21:48:51-05:00

GiteaMirror commented

2026-05-20 21:48:51 -05:00

Originally created by @CookSleep on GitHub (May 3, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/13450

Check Existing Issues

I have searched the existing issues and discussions.

Problem Description

I often need to upload many screenshots to the model for error diagnosis/casual chat, but some images I don't want to compress in quality or resolution, as that would make it difficult for the model to see the content clearly (such as images generated from long screenshots).

Open WebUI only converts images into Base64 URLs stored in conversation files, which are ultimately saved in the database. However, for most people's servers, quickly transferring large Base64 URLs is impossible, resulting in extremely slow loading of conversations, as well as sending and receiving requests.

Desired Solution you'd like

Support storing images from conversations to S3 and directly using S3 links when reading, instead of loading from the server, which will significantly improve the loading speed of conversations and the speed of sending and receiving requests

Alternatives Considered

I've looked at the source code implementation for S3 storage, and it doesn't support uploading images from conversations to S3.

Additional Context

No response

Originally created by @CookSleep on GitHub (May 3, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/13450 ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description I often need to upload many screenshots to the model for error diagnosis/casual chat, but some images I don't want to compress in quality or resolution, as that would make it difficult for the model to see the content clearly (such as images generated from long screenshots). Open WebUI only converts images into Base64 URLs stored in conversation files, which are ultimately saved in the database. However, for most people's servers, quickly transferring large Base64 URLs is impossible, resulting in **extremely slow** loading of conversations, as well as sending and receiving requests. ### Desired Solution you'd like Support storing images from conversations to S3 and directly using S3 links when reading, instead of loading from the server, which will significantly improve the loading speed of conversations and the speed of sending and receiving requests ### Alternatives Considered I've looked at the source code implementation for S3 storage, and it doesn't support uploading images from conversations to S3. ### Additional Context _No response_

GiteaMirror closed this issue

2026-05-20 21:48:52 -05:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#120225