All articles

ChatGPT Ads With Multiple Images: An API Handoff Checklist

OpenAI documents 4–6-image ads for enabled accounts. Prepare one shared message, an ordered asset manifest and deliberate update checks before testing.

Ceramic coffee cup on a mint pedestal with abstract advertising cards against pale blue tiles

Enabled accounts can now use the ChatGPT Advertiser API to create one ad with 4–6 square images sharing a title, body and destination. The useful preparation is a single-message creative brief and a precise asset handoff—not six unrelated offers. OpenAI’s API changelog dates this capability October 26, 2026; GPTAd observed the documentation change on October 28.

October 31 update: OpenAI’s current Ads Manager guidance describes Multiple images as an open beta introduced from October 26 for standard Reach, Clicks and Conversions campaigns. This UI availability is distinct from the API account and bidding conditions below. Open beta is not general availability; check the workflow you actually use.

Check access before commissioning assets

The documentation requires an account enabled for multiple images and a standard Reach, Clicks or Conversions campaign. Fixed bidding is the default requirement unless the account is separately enabled to use multiple images with automatic bidding. These instructions do not establish general availability, a country-by-country rollout or access for every advertiser in Vietnam.

The format still uses creative.type: "chat_card". It is not a product-feed template or a Sponsored Agent. For the broader distinctions, see our format overview.

Compare ChatGPT ad formats and Sponsored Agents

Build a handoff that preserves the intended sequence

The Files reference specifies separately uploaded, distinct square images in display order, all under the same ad account. The Ads reference accepts their IDs through creative.file_ids; do not combine this array with file_id, image_crop, price or business_agent_id. All images use the same destination.

GPTAd recommends an asset manifest with five columns: position, approved source filename, uploaded file ID, claim or visual purpose, and reviewer. Keep the account and destination beside that manifest. This is an editorial workflow, not an extra OpenAI API requirement.

Before handing the package to engineering, ask whether every image supports the same promise and whether the landing page substantiates it. If one image needs a different offer or destination, resolve that conflict in the brief instead of assuming the API provides a separate link for it.

A hypothetical four-image brief

Imagine a furniture maker promoting one compact desk. A possible sequence shows the complete desk, its dimensions, a storage detail and the desk in a small room. One shared message and one desk page can support that sequence. Use accurate measurements and your own licensed images; this example is a creative-planning exercise, not evidence of better advertising performance.

The review question is concrete: could a customer understand what is being offered from any image without encountering a contradictory promise on the destination page? Record the answer and unresolved issues before upload. Do not add two weak images merely because the maximum is six.

Use the creative and landing-page review checklist

Treat later edits as deliberate changes

When updating a multi-image creative, include type, title and body. Omitting file_ids preserves the images; supplying it replaces them with the complete new array. Omitting target_url preserves the destination, while an explicit value applies to every image. Converting an existing single-image ad requires a new ad rather than sending a singular file_id to a multi-image creative.

Keep a before-and-after manifest for each proposed revision. For a copy-only change, check that the outgoing request does not accidentally include an old asset array. For an image replacement, review the complete resulting sequence rather than only the newly uploaded file. These checks help make the team’s intended change auditable.

The response contains an ordered creative.images array; file_id and image_url may be null. Retrieve the ad to resolve image URLs, and retain uploaded file IDs as the creation inputs. Creation or a preview does not prove serving eligibility, and creative updates start another review.

Separate three decisions: whether the creative package is correct, whether review and account conditions allow delivery, and whether a controlled test meets your business objective. More images alone answer none of the last two questions. GPTAd is independent of OpenAI; this checklist is not account approval or a performance guarantee.

References

OpenAI: Advertiser API overview and October 26 changelog

OpenAI: Campaign management and multi-image workflow

OpenAI: Ads API reference—creation, responses and updates

OpenAI: Files API reference—uploading multiple images

OpenAI: Creating ads in Ads Manager, including the multi-image open beta

Good questions open new possibilities.
Put these ideas to work

Your next step.
Handled together.

Talk to our team about SEO, AI discovery and ChatGPT advertising, or get early access to the workspace behind our work.

Where we can help
  • Technical SEO and content
  • AI discovery on ChatGPT, Perplexity and Gemini
  • ChatGPT ads, when they fit