> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gooseworks.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating ads

> Remix a starting ad into a finished, on-brand creative

The **Create** page is where you remix a starting ad into your brand's version. You choose a starting point, pick what to feature, set your generation options, and Goose produces finished creatives you can download and run.

## Pick a starting point

Every creative starts from a source. You have a few ways to choose one:

| Starting point | Best for |
| - | - |
| **My Ads** | Remixing one of your own uploaded or previously generated ads. |
| **Competitor Ads** | Using a competitor's live ad as inspiration for a fresh, on-brand creative. |
| **Community gallery** | Remixing a creative someone else has shared. See [Community](/ad-remixer/community). |
| **Bring your own ad** | Uploading or pasting an ad you already have or one you admire. |

<Tip>
  No idea where to start? **Surprise Me** seeds your selection with a few brand-relevant ads from the Community gallery.
</Tip>

### Bring your own ad

On the create flow you can upload or paste a source ad you like. You'll first confirm that you **own or have the right to use** the image — don't upload a competitor's ad or copyrighted work you don't have rights to. Uploads are private to your workspace unless you choose to share them to the Community. Goose then analyzes the ad and remixes it through the same pipeline, applying your brand to its layout and style.

### Organize with tags

Add your own **tags** to uploaded templates and to generated ads (the **Add tags** control below each one). Tags are free-form labels — like `q1-launch`, `holiday`, or `paused` — that let you filter your uploads and your gallery from the **Tags** row at the top. You can also manage them from your coding agent with the `set_ad_creative_tags` and `set_user_ad_template_tags` MCP tools.

## Choose what to feature

Once you've picked a starting point:

1. **Select a product** from your [brand kit](/ad-remixer/brands) to feature in the ad.
2. **Add reference images** if you want to guide the look — extra product shots, lifestyle photos, or anything that should appear.
3. **Add a prompt** (optional) describing what you want — a headline angle, a setting, a mood.

## Generation settings

Before you generate, set how the batch should run. These settings change both the look of your ads and how many credits a batch uses:

| Setting | Effect |
| - | - |
| **Number of variants** | More variants = more completed images = more credits. |
| **Aspect ratios** | Each requested ratio (1:1, 4:5, 9:16, 16:9) is generated separately. |
| **Generation engine** | Different engines have different per-image costs. |
| **Quality / effort tier** | Higher tiers produce sharper, more detailed creatives and cost more per image. |

Generate, and Goose fans out the work — composing each creative, placing your product and logo, and checking the result before it ships it to you.

<Tip>
  Start with one or two variants to check direction before generating a larger batch. If a single creative misses, regenerate just that one rather than re-running the whole batch.
</Tip>

## Remix modes

Ad Remixer supports three ways to remix, depending on how much you want to change:

<AccordionGroup>
  <Accordion title="Variation — restyle into your brand" icon="palette">
    The default. Takes the template's layout and rebuilds it in your brand — your product, logo, colors, and copy. Use this to turn a proven ad into your own.
  </Accordion>

  <Accordion title="Edit — change one thing" icon="pen">
    Starts from an existing creative's image and applies a targeted instruction (for example, "make the background blue" or "swap in the new product photo") while keeping everything else the same.
  </Accordion>

  <Accordion title="Exact — your prompt, verbatim" icon="bullseye">
    Uses your prompt exactly as written against the source image, with no restyling. Use this when you know precisely what you want.
  </Accordion>
</AccordionGroup>

## How Goose keeps it on-brand

Every creative is automatically checked before it reaches you. Goose verifies that:

* Your **real logo** appears correctly (it's placed pixel-perfect, not redrawn).
* Your **product** matches your reference images everywhere it appears.
* The template's **original product and branding were fully replaced** — not just relabeled.
* No leftover text from the source ad (watermarks, attribution, spec callouts) survived.

If a creative doesn't pass, Goose automatically retries once with notes on what to fix. You can always regenerate any creative you're not happy with.

## Video ads

<Info>
  **Starting a video from your coding agent?** Asking Claude Code, Codex or Cursor for a video ad has its own page: [Video ads](/ad-remixer/video-ads). The section below covers the app's video composer. Both are made on your own machine.
</Info>

Ad Remixer also makes **video** creatives from curated video templates. Pick one proven format, then use the video composer to set a shared product, audience, offer, CTA, style, references, and production choices. The template declares which controls it supports, so voice, character, captions, music, duration, ratio, and end-card controls only appear when that recipe can use them.

A video run defaults to **three independently reviewable concepts**. You can choose one to four and customize each concept's hook, angle, message, and production note. Planning creates a video batch and one project per concept; it does not render a final video or spend final-render credits.

### Brand Video Kit

The Brand Video Kit stores reusable, typed production assets. V1 begins with approved end cards and supports the same abstraction for intro and mid cards, caption presets, music, sound effects, and character anchors. A selected approved end card is pinned to each concept by asset ID and treated as a locked composition input—the local agent uses the original asset instead of recreating its typography. Replacing it requires an explicit action.

### Review before render

Video generation runs locally in your own MCP-capable coding agent. At the start of a video project, the agent calls `catalog_fetch(type: "skill", slug: "goose-video-local")` on the GooseWorks MCP and follows the returned recipe; no local `goose-video-local` skill file is required. The agent prepares every concept's script and visual/audio ingredients, mirrors them into the project, and stops. The agent shows you the ingredients in the chat, and you can also review your recipe ingredients in the project in the app. Approve in the chat: the agent records your approval and renders. The backend rejects a render until the current ingredients are approved, and saving new ingredients clears an earlier approval.

Every finished master must then pass the visible quality loop:

`Rendering → Watching & checking → Repairing (if needed) → Re-checking → Ready`

The report covers source, brand, product, hook and scene order, speech/script agreement, captions, end card and CTA, duration and ratio, and visual artifacts. Standard polish permits one objective repair pass; Extra polish permits two. When the budget is exhausted or the issue needs subjective direction, the project becomes blocked and the agent stops spending. Only a candidate with a passing structured report can be pinned final.

## Generate from your coding agent

Prefer to work from Claude Code, Cursor, or Codex? You can drive the same remix pipeline from your coding agent using the GooseWorks MCP tools:

* `ads_generate(dry_run: true)` — preview the credit cost of a batch before running it.
* `ads_generate(mode: "generate", dry_run: false)` — start the approved generation request.
* `job_get(kind: "ads_batch")` — check status and fetch results.
* `ads_creative_edit` — edit or re-roll a creative.

For local video batches, use the video-native protocol:

* `create_ad_video_batch` — validate the template controls and create one to four reviewable concept projects (three by default).
* `get_ad_video_batch` / `update_ad_video_batch` — resolve the complete batch context and report its visible lifecycle.
* `list_brand_video_assets`, `create_brand_video_asset`, and `update_brand_video_asset` — read or save typed Video Kit assets.
* `get_ad_project` — resolve the concept's creative brief, batch, selected typed assets, approval state, and latest quality report.
* `update_ad_project_script` — mirror all review ingredients and stop for approval.
* `update_render_status` — report the quality stage, bounded repair count, and structured final report. A batch render cannot complete without a passing report.

See [Coding agents](/concepts/cli) and [MCP servers](/concepts/mcp-servers) for setup.

## Credits

Each completed image consumes credits. The amount depends on the engine, quality tier, number of variants, and aspect ratios you choose. When a batch starts, Goose may reserve the estimated credits up front and then bill only the images that actually complete — any reserved-but-unused credits are released back to your balance when the batch finishes.

For exact per-image pricing and how billing settles, see [How credits are used](/help-center/how-credits-are-used).

## Common issues

**Ads don't match my brand**

* Check the brand kit for the wrong logo, colors, or outdated product images.
* Add reference creatives that show the style you're aiming for.

**A batch produced fewer ads than expected**

* Some images can fail or be filtered during generation. Reserved-but-unused credits are released back to your balance when the batch finishes.

**I ran out of credits mid-batch**

* Top up under **Settings** > **Billing**, then start a new batch. See [How credits are used](/help-center/how-credits-are-used).

## Next steps

<Columns cols={2}>
  <Card title="Community" icon="users" href="/ad-remixer/community">
    Share your creatives or remix what others have made.
  </Card>

  <Card title="Autopilot" icon="robot" href="/ad-remixer/autopilot">
    Get a fresh batch generated and emailed every week.
  </Card>
</Columns>

***

Questions? Reach out at [help@gooseworks.ai](mailto:help@gooseworks.ai).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.