Approving a clipart or sticker batch

Clipart and sticker projects stop at Awaiting approval before delivery. This is the one moment in the pipeline where you decide whether the batch is good enough to ship — or whether you want to regenerate before any files leave the studio.

Why the gate exists

Clipart bundles deliver 15-30 images at once; sticker projects deliver one per prompt. Both formats are sold as digital downloads, so once they’re packaged and pushed to Drive there’s no clean way to swap a weak image without rebuilding the listing. The approval step keeps the bad ones out before they cost you a redo.

Wall art, poster, SVG, and custom projects skip this step — they have either a single image (you accept or regenerate it directly) or no generated image at all.

What to check

Open the project, scroll the Overview tab, and look at every thumbnail:

• Composition — is the subject centered, fully visible, not cut off at the edges?
• Transparency — clipart and stickers must have transparent backgrounds. Look for grey haloes around the subject; that’s a sign background removal didn’t fully clear the edge.
• On-brief — does each image match the idea you described? One off-brief image is usually fine; six is a sign the prompt needs work.
• Duplicates — for clipart bundles, look for near-identical pairs. Buyers expect variety.

Approving

The Approve button on the project page advances the pipeline to processing → delivery. From that point the worker chain runs unattended: ESRGAN upscale (4×, alpha-aware), 300 DPI metadata, ZIP packaging, Google Drive upload, listing writing, and (if connected) Etsy draft creation.

You can’t “approve only some” of the images. If a few are weak, you have two choices:

1. Approve anyway and accept the batch as-is.
2. Regenerate individual images from the project page before approving the rest. Each regenerated image costs the same per-image credit as the original.

What if I don’t approve?

Approval is mandatory for clipart and sticker. The project sits at Awaiting approval indefinitely until you act. Credits have already been deducted at launch — they won’t be returned just because you walked away.

If you want to abandon the project entirely, use Delete project on the project page. This removes the R2 files and the database record. Credits already spent on generation are not refunded; this is a no-coming-back action.

Related

• Choosing a generation model — picking the right model is the best way to reduce regenerations.
• Tips for better AI-generated images — prompting patterns that produce higher batch yield.