GPT Image 2.6: A Two-Stage Pipeline for Consistent Animated Stickers A developer outlined a two-stage pipeline for generating consistent animated stickers with GPT Image 2.6, using Ace Data Cloud's image generation and edit APIs. The approach first generates and human-approves a single static character reference, then produces each GIF animation as an edit with explicit PRESERVE and CHANGE prompt sections to prevent identity drift. The examples were illustrative and not executed, and the writeup notes documented GIF limits of 2–16 frames with a recommended 512x512, 9-frame, 200ms preset. GPT Image 2.6 can produce native GIF output, but generating twelve animated stickers in one loosely specified batch is still a reliability trap. A more maintainable approach is a two-stage pipeline: first approve one static character reference, then create each animation as an edit that is allowed to change motion but not identity. This article turns that idea into an API workflow with validation, acceptance checks, and failure handling. It uses the Flare variant in the examples; use Sunburst as an alternate candidate when you want to compare render behavior on the same locked prompt. The important engineering decision is not the variant name—it is keeping the reference and invariants stable across the set. Disclosure: This article was prepared for an Ace Data Cloud promotional task and draws on Ace Data Cloud's public documentation and first-party tutorial. I am not presenting the tutorial author's results as my own testing. The requests below are illustrative and were not executed for this article. AI assistance was used to organize and edit the draft. Do not start with animation. Generate a static square reference that makes identity easy to inspect: front-facing pose, uncluttered silhouette, fixed clothing, and a small color palette. curl -X POST 'https://api.acedata.cloud/openai/images/generations' \ -H 'Authorization: Bearer YOUR ACE API TOKEN' \ -H 'Content-Type: application/json' \ -d '{ "model": "gpt-image-2.6-flare", "prompt": "Design one friendly capybara sticker character, front view, clay texture, round head, yellow rain boots, neutral pose, plain background. No text and no additional characters.", "size": "1024x1024", "quality": "high", "output format": "png", "response format": "url", "n": 1 }' This is an unexecuted example using a placeholder credential. The generation API documentation https://platform.acedata.cloud/documents/openai-images-generations is the source of truth for current fields. Before accepting the result, store both the returned asset and a small manifest: { "character id": "capybara-v1", "reference url": "https://YOUR STORAGE.example/capybara-v1.png", "locked": { "material": "clay", "head shape": "round", "boots": "yellow", "palette": "brown", "cream", "yellow" , "characters": 1 } } Copy the generated file into storage you control rather than treating a transient result URL as your system of record. Keep the prompt, model, response metadata, and manifest beside it. Human approval at this stage is cheap; discovering identity drift after twelve animations is not. Use the approved image as the single reference for every sticker. The edit prompt should contain two separate sections: preserve and change . This makes review criteria explicit and discourages accidental redesign. curl -X POST 'https://api.acedata.cloud/openai/images/edits' \ -H 'Authorization: Bearer YOUR ACE API TOKEN' \ -H 'Content-Type: application/json' \ -d '{ "model": "gpt-image-2.6-flare", "image": "https://YOUR STORAGE.example/capybara-v1.png", "prompt": "PRESERVE: the only character, clay material, brown-and-cream palette, round head, facial features, yellow rain boots, and body proportions. CHANGE ONLY: animate a cheerful two-handed wave with a clean seamless loop. Keep the character centered. No text, props, camera movement, or extra characters.", "size": "512x512", "quality": "high", "output format": "gif", "frame count": 9, "frame duration ms": 200, "response format": "url", "n": 1 }' GPT Image 2.6 Flare and Sunburst expose native GIF output in the current docs. GIFs have their own limits: frame count accepts 2–16, and the documentation recommends 512x512 , 9 frames, and 200ms per frame as a practical preset. Do not describe or configure this as “4K GIF”; the documented 4K presets apply to static generation and editing, while GIF size and frame limits are separate. See the editing API documentation https://platform.acedata.cloud/documents/openai-images-edits . Reject malformed jobs locally. Validation should cover more than JSON types: js function validateStickerJob job { const allowedModels = new Set "gpt-image-2.6-flare", "gpt-image-2.6-sunburst" ; if allowedModels.has job.model throw new Error "unsupported model" ; if /^https:\/\//.test job.image throw new Error "HTTPS reference required" ; if job.output format == "gif" throw new Error "GIF required" ; if job.size == "512x512" throw new Error "unexpected GIF canvas" ; if Number.isInteger job.frame count || job.frame count < 2 || job.frame count 16 { throw new Error "frame count must be 2..16" ; } if job.frame duration ms < 20 throw new Error "frame duration too short" ; } Also allow-list reference hosts or resolve uploaded assets to internal object IDs. Otherwise, accepting arbitrary URLs can turn an image endpoint into an SSRF surface. Cap prompt length, attach an idempotency key in your own job table, and never log bearer tokens. A successful HTTP response is not a passed sticker. Decode the GIF and verify mechanical properties first: expected MIME type, dimensions, frame count, nonzero duration, and a file-size ceiling chosen for your delivery channel. Then run a preservation review against the manifest: Some checks can be automated, but identity and loop quality still deserve a human gate. Mark each output accepted , retryable , or rejected ; do not silently place failed assets into a published pack. For errors, separate permanent failures invalid parameters, blocked content, bad credentials from transient failures rate limits or server errors . Retry only transient classes with exponential backoff and jitter. If an asynchronous request returns a task ID, persist it and poll that same task rather than submitting the generation again. A one-shot batch is faster to describe, but difficult to debug: the model is simultaneously inventing identity, motion, composition, and style. The two-stage flow adds an approval step and storage overhead, yet gives you a stable artifact, smaller retry scope, and an auditable definition of “same character.” You can prototype the visual flow in Ace Data Cloud Studio https://studio.acedata.cloud/ before wiring the API. The first-party animated sticker tutorial https://platform.acedata.cloud/blog/create-wechat-stickers-with-gpt-image-2-6?lang=en shows the reference-first idea with a capybara set. It is inspiration, not evidence that any pack created from this article has passed WeChat review; check the destination platform's current submission rules before shipping.