Batch Generate Ad Variants Inside Claude

To batch generate ad variants, connect Polaris to Claude via MCP, then ask for several versions of the same ad concept in one request. Claude walks you through settings via tappable option cards, Polaris renders the variants in parallel, and you download the finished set as a ZIP once they're ready.

Why batch instead of one at a time

Testing usually beats guessing. Rather than generating a single ad and hoping it performs, asking for a batch of variants, different angles, hooks, or actors on the same product, gives you a small set to compare and pick winners from before spending on media. Polaris supports this directly: a batch request renders each variant in parallel rather than making you wait through one generation before starting the next.

Step-by-step: batch generating in Claude

1. Connect Polaris. Add the MCP connector at polarisugc.com/api/mcp in Claude and authorize it once.
2. Share the product. Attach a product photo or paste your script directly into the chat.
3. Ask for a batch explicitly. Tell Claude you want several variants of the same ad concept, for example different hooks or settings on the same product.
4. Set shared settings via option cards. Claude presents tappable cards for model and other settings that apply across the batch.
5. Watch the panel render in parallel. The live Polaris panel shows each variant's progress at once, with individual renders typically finishing somewhere in the 20 to 180 second range.
6. Review and download. Once the batch finishes, download the set as a ZIP and compare variants before choosing which to run.
7. Recreate the near-misses. If one variant is almost right, use one-click Recreate instead of starting over from scratch.

New accounts also get a first batch of 12 free with no card required, which is a low-friction way to try batch generation before committing. The web app is available as a secondary surface for reviewing a batch visually, but requesting and generating the batch inside Claude is the primary path.

Pro tips

• Vary one dimension per batch, hook line, setting, or actor delivery, rather than changing everything at once, so you can actually tell what drove the difference.
• Use a batch to test the opening hook specifically before committing credits to full multi-clip sequences built around it.
• Failed renders in a batch are auto-refunded, so a batch request doesn't waste credits on the ones that don't come out.
• Run the top two or three variants through Copy Judge before you spend on media, particularly for claims-sensitive categories.

Honest caveats

Every variant in a batch is still built around your actual product and script, not a stock-avatar library, so the batch is only as strong as the brief and photo behind it. A batch narrows down promising creative, it doesn't replace real ad testing once variants are live. If you operate in a regulated niche, every variant in the batch needs the same compliant language, no disease, cure, or guaranteed-result claims, even the ones you don't end up running.

See the full Claude MCP workflow, browse AI UGC ad examples, or compare pricing plans for batch usage at scale.