github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-08 21:09:41 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #13696] issue: Picture Display issue when switching to "High" quality with gpt-image-1 (in Azure) #17001

New Issue
Closed
opened 2026-04-19 22:47:34 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-19 22:47:34 -05:00
Owner
Copy Link

Originally created by @pierrelouisbescond on GitHub (May 8, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/13696

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.7

Ollama Version (if applicable)

No response

Operating System

Ubuntu 24.04.2

Browser (if applicable)

Chrome 135.0.7049.115, Edge 136.0.3240.50

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have listed steps to reproduce the bug in detail.

Expected Behavior

Whatever the picture quality chosen when using gtp-image-1 Azure API, the UI should display the picture(s) generated properly.

Actual Behavior

When using Azure GPT Image 1, the UI properly displays pictures generated in "low" and "medium" qualities, but fails to display them when the output from gpt-image-1 model is set to "high" quality.

Image

However, switching to another conversation and returning to the original conversation where the picture was initiated solves the problem. The UI then correctly displays the picture.

I'm wondering if this can come from the time needed to generate the "high" quality pictures, as their weight remains more or less in the same range:

Pictures generated in:

  • Low quality: 14.78 seconds, 1.2MB
  • Medium quality: 27.61 seconds, 1.4MB
  • High quality: 49.08 seconds, 1.7MB

Image
Image
Image

Steps to Reproduce

  • Import Azure GPT Image 1
  • Set all required parameters (Azure endpoint, api key, version, etc.) in the valves
  • Expose the corresponding model "gpt-image-1"
  • Generate the pictures with different qualities (low, medium, and high), set thourhg the valves parameters

Logs & Screenshots

No relevant information in logs showing any errors, the script is executed smoothly, whatever the selected quality.

Additional Information

Container has 4CPUs and 16Gi

Originally created by @pierrelouisbescond on GitHub (May 8, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/13696 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.7 ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu 24.04.2 ### Browser (if applicable) Chrome 135.0.7049.115, Edge 136.0.3240.50 ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have listed steps to reproduce the bug in detail. ### Expected Behavior Whatever the picture quality chosen when using **gtp-image-1** Azure API, the UI should display the picture(s) generated properly. ### Actual Behavior When using [Azure GPT Image 1](https://openwebui.com/f/pierrelouis/azure_gpt_image_1), the UI properly displays pictures generated in "low" and "medium" qualities, but fails to display them when the output from gpt-image-1 model is set to "high" quality. ![Image](https://github.com/user-attachments/assets/cb9ae5f4-3d04-4266-81d5-4ebc3295ce22) However, switching to another conversation and returning to the original conversation where the picture was initiated solves the problem. The UI then correctly displays the picture. I'm wondering if this can come from the time needed to generate the "high" quality pictures, as their weight remains more or less in the same range: Pictures generated in: - Low quality: 14.78 seconds, 1.2MB - Medium quality: 27.61 seconds, 1.4MB - High quality: 49.08 seconds, 1.7MB ![Image](https://github.com/user-attachments/assets/475fcfa0-6e2a-4a77-a60b-b6d34f7ac791) ![Image](https://github.com/user-attachments/assets/7a1a3528-77fb-476c-a420-3f42de7ab414) ![Image](https://github.com/user-attachments/assets/db5cdf2b-34c9-4bca-92fd-7a36f4adf254) ### Steps to Reproduce - Import [Azure GPT Image 1](https://openwebui.com/f/pierrelouis/azure_gpt_image_1) - Set all required parameters (Azure endpoint, api key, version, etc.) in the valves - Expose the corresponding model "gpt-image-1" - Generate the pictures with different qualities (low, medium, and high), set thourhg the valves parameters ### Logs & Screenshots No relevant information in logs showing any errors, the script is executed smoothly, whatever the selected quality. ### Additional Information Container has 4CPUs and 16Gi
GiteaMirror added the bug label 2026-04-19 22:47:34 -05:00
GiteaMirror commented 2026-04-19 22:47:35 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (May 8, 2025):

Must be addressed from the Function.

<!-- gh-comment-id:2863888545 --> @tjbck commented on GitHub (May 8, 2025): Must be addressed from the Function.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#17001
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?