---
title: Image Feed Settings
description: "Image feeds are created under **Form Settings -> AI Image** and use OpenAI. ## Model lifecycle GPT Image 2.6 Flare is the recommended default for a new feed. GPT Image 2.6 Sunburst is the model of the pair for detailed…"
url: "https://brightleafdigital.io/docs/image-feed-settings/"
updated: "2026-11-17"
category: GravityOps AI Feed / Settings Reference
---

# Image Feed Settings

Image feeds are created under **Form Settings -> AI Image** and use OpenAI.

## Model lifecycle

GPT Image 2.6 Flare is the recommended default for a new feed. GPT Image 2.6 Sunburst is the model of the pair for detailed visual work and is worth choosing when precision matters more than speed; OpenAI charges both at the same token rates as GPT Image 2.5. Both 2.6 models accept Extra High and Maximum quality. Custom sizes remain limited to the model IDs whose support OpenAI explicitly documents; choose a GPT Image 2.5 model when a feed needs a custom size.

GPT Image 2.5 Flare and GPT Image 2.5 Sunburst remain current and selectable. OpenAI has not replaced them with 2.6, and the historical GPT Image 1 shutdown row still names them as its replacement. A feed that uses 2.5 does not show a migration notice.

GPT Image 2 is deprecated and retires on February 10, 2027. It is not offered for new selections. A feed that already uses it keeps showing it with a warning until that date, then stops generating images until an administrator explicitly selects and saves a supported model. OpenAI names GPT Image 2.6 Flare and GPT Image 2.6 Sunburst as the replacements. The plugin never moves a feed to a different model on its own.

GPT Image 1 (`gpt-image-1`) retired on October 23, 2026. An existing custom feed using that ID cannot generate images until an administrator selects and saves a supported model. GPT Image 2.6 Flare is the recommended migration option.

GPT Image 1.5 and GPT Image 1 Mini are deprecated and are not offered for new selections. A feed that already uses one keeps showing it with a warning until OpenAI's December 1, 2026 retirement date. On that date the feed stops generating images until an administrator explicitly selects and saves a supported model. The plugin never moves a feed to a different model on its own, because model behavior, capabilities, and pricing can differ.

## Prompt

Describe the image to generate. The merge-tag button inserts current form values. Good prompts state the subject, setting, composition, visual style, colors, orientation, intended use, text that must appear, and important exclusions.

Example: `Create a clean square event illustration featuring {Event subject:3}. Use {Brand colors:4}, leave clear space at the top for a headline, and do not include logos or written text.`

All merged values are sent to OpenAI. Provider safety policies can reject a prompt even when its format is valid.

## Target File Upload Field

Choose a File Upload field from the current form. The generated image is saved there so Gravity Forms and connected add-ons can treat it as an entry file.

For an after-submission feed, the target File Upload field must be optional. Gravity Forms checks required fields before the feed can generate the missing file. Frontend generation also needs the target field so the verified temporary image can be associated with the submitted entry.

## Conditionally Hidden Target

Shown for frontend image feeds and enabled by default. Leave **Attach the generated image even when conditional logic hides the target field** selected when the generated image is an output of the feed rather than a visitor-supplied upload. Gravity Forms normally omits conditionally hidden fields while creating an entry; the plugin attaches the verified generated image immediately after the entry is saved so later feeds and notifications receive it.

Clear this setting when hiding the File Upload field should also prevent the generated image from being attached. The visitor can still generate and preview the image, but it is not added to the entry if the target is hidden when the form is submitted. This setting does not change the field's conditional logic or make it visible.

Gravity Forms must create an entry before the plugin can attach the image. If the hidden target is the only field with a value, Gravity Forms treats the submission as empty and displays **At least one field must be filled out**. Ensure the form submits a value from at least one other visible field; the generated image cannot satisfy this check because its hidden target is attached only after the entry is created.

## Size

- **Automatic** sends `auto`; OpenAI chooses the size according to the selected model and service behavior.
- **1024 x 1024** creates a square request and is the default for a new feed.
- **1536 x 1024** creates a landscape request.
- **1024 x 1536** creates a portrait request.
- **Custom size** reveals Custom Size. It requires GPT Image 2.5 Flare, GPT Image 2.5 Sunburst, or an existing GPT Image 2 selection. New feeds cannot select GPT Image 2.

Automatic does not mean the plugin inspects the form or preview area. The decision is delegated to OpenAI.

## Custom Size

Enter `WIDTHxHEIGHT`, such as `1280x720`. Both edges must be divisible by 16. The aspect ratio cannot exceed 3:1, no edge can exceed 3,840 pixels, and the total must be between 655,360 and 8,294,400 pixels. This setting is accepted only for GPT Image 2.5 Flare, GPT Image 2.5 Sunburst, and GPT Image 2. OpenAI treats resolutions above 2560 x 1440 as experimental.

Larger images can take longer and may cost more. Confirm current provider pricing before using large dimensions on public forms.

## Quality

- **Automatic** sends `auto`; OpenAI chooses the quality.
- **Low**, **Medium**, and **High** request an explicit quality level and are accepted by every image model.
- **Extra High** and **Maximum** request the two higher levels supported by GPT Image 2.5 and GPT Image 2.6 Flare and Sunburst. Choosing one with any other model reports an error on the Quality setting when the feed is saved.

OpenAI's [image generation guide](https://developers.openai.com/api/docs/guides/image-generation#calculating-costs) lists both families' supported quality levels in its cost calculator.

Higher quality can increase generation time and cost. OpenAI bills image output per token, and Extra High and Maximum spend several times what High does on the same prompt, so confirm current pricing before putting either on a public form. Automatic does not inspect the prompt or site design locally; it delegates the choice to the provider.

## Output Format

Choose PNG, JPEG, WebP, or Animated GIF. PNG is the default and is useful for lossless graphics. JPEG is often smaller for photographic images. WebP can offer smaller modern web images but may be less suitable for external systems that expect PNG or JPEG.

Animated GIF requires GPT Image 2.6 Flare or Sunburst and provider access to the GIF preview. Describe the subject, motion, and desired loop in the prompt. Choose Automatic size when starting an animation; OpenAI applies model-specific frame and total pixel limits, and a fixed size may require fewer frames. The plugin preserves the returned GIF bytes through previews and entry attachments, so it does not flatten the animation into a still image. The target File Upload field must allow the `gif` extension.

## Complexity

GPT Image 2.6 Flare and Sunburst accept Low, Medium, or High planning complexity. This controls planning before rendering separately from Quality. Higher complexity can help with dense text and layouts, but can increase latency or change more details.

Provider default leaves the parameter out and currently uses High. Selecting High explicitly sends High even if the provider later changes its default. Feeds saved before this control was added keep that behavior. A saved complexity value is ignored for models outside the reviewed support list, including older models and unknown custom IDs.

## GIF Frame Count And Duration

These controls appear only when Output Format is Animated GIF. Frame Count accepts 2 through 16; leaving it empty uses the provider default of 9. Frame Duration accepts 20 through 2,000 milliseconds per frame and rounds to the nearest 10 milliseconds; leaving it empty uses 200. Changing timing changes playback speed. More frames can increase generation time and cost.

The controls are validated before generation and sent only for GIF output. Switching to a still format leaves saved frame settings inactive. Provider-specific combined size limits are enforced by OpenAI; use Automatic size or reduce the frame count if the provider rejects the combination.

See OpenAI's [GIF guide](https://developers.openai.com/api/docs/guides/image-generation#generate-animated-gif-output) for the documented frame controls and preview requirements in the API reference.

## Content Filter

OpenAI screens every image prompt against its own content policy, before and after generation. This setting chooses how strictly it does so.

- **Standard (provider default)** sends nothing extra and accepts OpenAI's normal filtering.
- **Less restrictive** asks OpenAI to relax filtering to the extent it permits.

Less restrictive is not a bypass. OpenAI's policies still apply, it can still decline a prompt, and you remain responsible for what your forms ask it to produce. The setting is sent only for models that support it; a custom model ID does not receive it.

Reach for it when legitimate prompts are being declined — descriptions of humanitarian, medical, or emergency work are the common case. Rewriting the prompt usually helps more than changing this setting. See the image generation troubleshooting page.

## Content Refusal Message

The opening sentence shown to the visitor when OpenAI declines a prompt under its content policy. Leave it empty to use the default.

Write it for the route forward this form actually offers. A form whose only option is to try again should not tell visitors to upload a file, and a form that accepts uploads should say so.

A sentence about the likely cause is added after it automatically. Visitors are only ever asked to change their own answers; when the cause came from this feed's prompt they are told to contact the administrator instead, and the cause is recorded on the Overview tab for you.

Visitors can see this text. Do not put internal notes, provider details, or contact information that should stay private into it.

## Who Can Use The Frontend Button?

Shown only for a frontend trigger. Public access allows anyone who can view the form to request an image, subject to signed tokens and rate limits. Administrator-only access requires a logged-in user with Gravity Forms full access. See the trigger/access reference.

## Stuck? Ask in GravityOps Help

Search past answers or post your question, tagged "ai-feed".

- [GravityOps AI Feed: a feed did not run on submission](https://brightleafdigital.io/community/gravityops-help/4147/)GravityOps Help - 0 replies - 2 weeks ago
- [GravityOps AI Feed is live: Claude and OpenAI as Gravity Forms feeds](https://brightleafdigital.io/community/announcements/3931/)Announcements - 0 replies - 4 weeks ago

[Ask in GravityOps Help](https://brightleafdigital.io/community/gravityops-help/?gofrm_tag=ai-feed)[Open a support request](https://brightleafdigital.io/support/)

GravityOps Weekly

[This iframe contains the logic required to handle Ajax powered Gravity Forms.](about:blank)
