How to enable image generation in Open WebUI

Open WebUI image generation lets the web interface call a separate image backend when users need generated images beside normal chat work. Enabling it is useful when an organization already has an OpenAI-compatible image provider, hosted image API, or local image service and wants the same Open WebUI workspace to handle text and image prompts.

The Admin Panel → Settings → Images page controls the global image switch, provider engine, default image model, output size, and provider credentials. The Default (Open AI) engine sends requests to an OpenAI-compatible /v1/images/generations endpoint, while ComfyUI, Automatic1111, and Gemini use their own provider fields.

Use a provider URL that the Open WebUI server or container can reach, not only a URL that works from the administrator's browser. After saving, a signed request to the Open WebUI image endpoint should return an uploaded file URL, and native chat-based generation also needs the selected model profile to allow the Image Generation capability.

1. Sign in to Open WebUI as an administrator.
2. Open Admin Panel → Settings → Images.
3. Turn on Image Generation.
4. Keep Image Generation Engine set to Default (Open AI) for an OpenAI-compatible image backend.
5. Enter the default Model and Image Size for generated images.

   The model name must match the provider-side image model. Common OpenAI-compatible examples include dall-e-3, gpt-image-1, or a model name exposed by an image API proxy.

6. Enter the provider OpenAI API Base URL and OpenAI API Key.

   Use a base URL shaped like https://llm.example.com/v1. For Azure OpenAI image deployments, use the deployment endpoint and set OpenAI API Version to the API version required by that deployment.

7. Leave Additional Parameters as {} unless the provider requires extra JSON options such as quality, style, or deployment-specific fields.
8. Click Save.
9. Confirm the target chat model allows image generation when users will generate images from chat.

   Open Admin Panel → Settings → Models, select the target model, and check its Capabilities if the model has a custom profile. Native tool-based generation needs both the global Image Generation setting and a model that allows the image-generation capability.

10. Store an Open WebUI API key for a smoke test.

    $ read -r -s OPEN_WEBUI_API_KEY

    Related: How to enable API keys in Open WebUI

11. Set the Open WebUI base URL for the image request.

    $ export OPEN_WEBUI_URL="https://openwebui.example.com"

12. Send a test image prompt through Open WebUI.

    $ curl --fail-with-body --silent --show-error "$OPEN_WEBUI_URL/api/v1/images/generations" \
      -H "Authorization: Bearer $OPEN_WEBUI_API_KEY" \
      -H "Content-Type: application/json" \
      --data '{"model":"dall-e-3","prompt":"A compact server rack drawn as a clean icon","n":1,"size":"1024x1024"}'
    [
      {
        "url": "/api/v1/files/090e2360-e181-40b6-a89e-7dd1d6a6ce54/content"
      }
    ]

    A returned /api/v1/files/.../content URL proves Open WebUI accepted the request, called the configured image backend, and stored the generated image. A 400 response usually points to the provider URL, API key, model name, image size, API version, or provider-side image-model availability.