Higgsfield's headphone commercial is a good example of where AI advertising is heading. Not because one prompt made a polished ad. The opposite. The workflow looks real because it borrows from real production: pre-production, asset testing, shotlists, continuity, iteration, and editing.
The tutorial builds a cinematic product ad with GPT Image 2, Soul Cinema, a custom Claude skill, and Seedance 2.0 4K inside Higgsfield. The practical lesson is simple: the best AI ads are not random generations. They are systems.
Source Note
This post uses Higgsfield's video and official written tutorial as the workflow source. The official blog post was published on June 22, 2026 and explains how the headphones commercial was built in Higgsfield with Seedance 2.0. It also lists the prompts, what each prompt does, and where to run it.
Product claims are checked against Higgsfield's Seedance 2.0, Soul Cinema, Cinema Studio, and Skills pages, plus OpenAI documentation for GPT Image 2 and ByteDance's Seedance 2.0 page. Treat the result as a production pattern, not a guarantee that every prompt will produce broadcast-ready footage on the first try.
Link Map
| Resource | Link | Status | Builder takeaway |
|---|---|---|---|
| Higgsfield tutorial video | Watch on YouTube | Source walkthrough | Shows the full commercial and the three-stage production process. |
| Full prompts and skill | Higgsfield blog | Official source | Use this as the prompt library and implementation companion. |
| Higgsfield AI | YouTube, X | Creator credit | Primary source for the tutorial and workflow. |
| Seedance 2.0 on Higgsfield | Higgsfield page, ByteDance page | Product/model source | The video generation layer for the final scenes. |
| Soul Cinema | Higgsfield Soul Cinema | Product source | Used for cinematic character and image references. |
| Cinema Studio | Cinema Studio | Product source | Relevant for scene shaping, camera style, lighting, and Elements. |
| Higgsfield Skills | Skills page | Official source | Shows how Higgsfield connects to agent workflows with CLI, MCP, and skills. |
| GPT Image 2 | OpenAI launch, model docs | Official source | Used for product sheets, asset edits, and layout maps in the workflow. |
The Main Takeaway
The finished commercial is the visible output. The real product is the production system behind it.
Higgsfield's process avoids the common AI-video trap: typing a giant prompt, hoping for a miracle, then spending credits chasing randomness. Instead, it separates the job into repeatable parts:
- Build the product, character, location, and prop references.
- Test references before using them in final scenes.
- Use a Claude skill to turn the script into a connected shotlist.
- Generate scenes in Seedance 2.0 with named elements and a shared style prefix.
- Edit the best seconds from many generations into one ad.
That last line matters. The secret is not that every generation works. The secret is that the workflow produces enough controlled attempts that the editor can find the keeper seconds.
The 3-Step Workflow
| Stage | Goal | Tools | Why it matters |
|---|---|---|---|
| 1. Build and test assets | Create product, characters, locations, props, outfits, and maps. | GPT Image 2, Soul Cinema, Higgsfield Canvas. | Reference quality controls video quality. |
| 2. Create the shotlist | Turn a script into named Seedance prompts. | Claude plus a custom skill. | One connected document is easier to edit than scattered prompts. |
| 3. Generate and iterate | Run each scene, diagnose failures, rewrite prompts, and keep the best seconds. | Seedance 2.0 in Higgsfield. | Iteration becomes controlled instead of random. |
Stage 1: Build And Test The Assets
The first mistake in AI ads is skipping pre-production. Higgsfield starts with assets: the headphones, hero character, boss, locations, props, outfits, and scene references.
The product sheet is built with GPT Image 2 so the model sees the headphones from multiple angles. That reduces mid-scene hallucination when the headphones rotate, move, or appear in closeup.
The hero character is built as a sheet, not a single face. The tutorial uses a close-up plus full-body views on a gray background. The gray background matters because it removes clutter, and the model can focus on the person. The workflow also tests multiple hero candidates in motion before locking one, because a still face can look good and fail once animated.
Location references use the same discipline. Generate multiple kitchens, stadiums, streets, and offices. Test one variable at a time. Same prompt, different reference. The winner moves to the top of the canvas and becomes locked.
Stage 2: Turn The Script Into A Connected Shotlist
The most important part of the workflow is not the model. It is the shotlist document.
Higgsfield uses a Claude skill to turn the script and locked assets into Seedance prompts. The key idea is that this is one connected document, not twenty loose prompts. It has:
- A style prefix: lighting, camera, color, and commercial look applied across the full ad.
- Named prompts: scene IDs like
1A,1B,2C, so you can ask Claude to edit only one shot. - Named assets: product sheet, hero sheet, kitchen, stadium, boss, mug, moka pot, street map, and music track.
- Scene-level overrides: the kitchen can be soft morning light while the stadium gets harsh midday sun.
STYLE PREFIX:
Bright commercial realism, clean camera movement, product-forward framing,
consistent hero, headphones visible, crisp 4K finish.
SCENE 1A - Kitchen entrance
Use: hero_sheet, headphones_sheet, kitchen_b
Goal: morning routine, headphones on, first music beat.
SCENE 1B - Coffee montage
Use: moka_cream, mug_cream, kitchen_b
Goal: fast commercial closeups, cut on action.
SCENE 2C - Product rig shot
Use: athletic_hero, headphones_sheet, stadium_a
Goal: headphones locked center while the track blurs behind him.
This is why the workflow scales. If the whole ad is too shadowy, change the style prefix once. If the coffee montage is bad, rewrite only prompt 1B. You are editing a production document, not yelling at a prompt box.
Stage 3: Generate, Diagnose, Rewrite, Repeat
Higgsfield is honest in the tutorial: the first try rarely works. The workflow is built for diagnosis.
Scene one reveals lighting and camera problems, so the style prefix changes from moody backlight to clean morning light. The coffee moment is doing too much in one shot, so it becomes its own prompt. The mug and moka pot drift, so they become locked prop references.
Scene two needs a different outfit, so the hero gets a dry athletic version and a wet post-run version. That is a subtle but important production trick. If a character changes state, create a new reference image instead of asking the video model to improvise the change.
Scene three is the hard one: street geography, dancing, sky dancer, backpack, traffic, and music all at once. The fix is a layout map. GPT Image 2 creates a schematic showing where the hydrant and sky dancer sit. Claude rewrites the prompt around the map. The model now has geometry, not just words.
The dance motion uses the same principle. "He dances" is not direction. The prompt names the moves: head bob, shoulder roll, knee dip, finger snap, quarter spin, footwork, locking poses. Specific choreography beats generic motion.
Production Tricks Worth Stealing
- Use product sheets: front and three-quarter views reduce object drift.
- Use gray-background character sheets: fewer distractions, better face lock.
- Erase duplicate faces from full-body sheets: one face in the reference gives the video model less to confuse.
- Test stills in motion: a great still can fail as soon as the character moves.
- Change one variable at a time: same prompt, different reference, then compare.
- Use layout maps: text often cannot pin object size and location. A schematic can.
- Create state-specific references: dry hero, wet hero, casual outfit, athletic outfit.
- Name every asset: if Claude and Higgsfield use the same names, scene setup becomes faster.
- Use keeper seconds: one final scene may come from the best seconds of several generations.
JQ AI SYSTEMS Builder Checklist
If I were building this workflow for a client campaign, I would use this checklist:
- Define the product promise. What does the ad make the viewer feel or do?
- Write the script first. One beat per scene. Keep the story simple.
- Create the asset board. Product sheet, hero, side characters, locations, props, maps, outfits.
- Test references before final scenes. Do not trust stills until you see motion.
- Create the shotlist file. Style prefix, named prompts, asset names, scene overrides.
- Generate draft resolution first. Use 4K for finalists, not blind exploration.
- Edit like a human. Pull keeper seconds, cut on action, and remove weak AI behavior.
- Review legal risk. Product claims, likeness, music, brand use, source references, and disclosure.
- Archive the system. Save prompts, locked assets, rejected assets, final edit notes, and cost.
The final takeaway is both exciting and grounding: AI can now make a commercial that looks expensive, but the quality comes from production discipline. The creator is still directing, testing, selecting, and editing.
Sources
- Higgsfield AI video: 3-Step Workflow To Make Ultra-Realistic AI Ads
- Higgsfield AI on YouTube
- Higgsfield on X
- Higgsfield: 3-Step Workflow To Make Ultra-Realistic AI Ads
- Higgsfield Seedance 2.0
- ByteDance Seedance 2.0
- Higgsfield Soul Cinema
- Higgsfield Cinema Studio
- Higgsfield Skills
- Higgsfield Seedance 2.0 prompting guide
- OpenAI: Introducing ChatGPT Images 2.0
- OpenAI GPT Image 2 model docs
- OpenAI image generation guide