Forge Academy · Practical workshop
Organize collections and export client-ready campaigns
By the InfluencerForge Editorial Team
Open the worked example ↓
TL;DR — Create one collection per campaign, tag assets as you generate, curate a finals set, and export the whole collection as a single ZIP from its detail view — no per-image downloads and no messy handoffs.
A productive month of generation easily produces hundreds of renders, and volume without structure turns delivery day into archaeology. Collections, tags, and one-click ZIP export exist so the organizing happens as you work — not in a panic before a client call.
A handoff people can use
The client should not have to find the finals.
Example delivery: three approved skincare concepts in two placements. Keep exploratory work in one collection and the six approved assets in a separate finals collection. Collections organize your account; they are not shared team workspaces.
Name the two collections “Iris — Skincare — October — Working” and “Iris — Skincare — October — Finals”. Check each asset against the brief before adding it to Finals.
After downloading, use your own computer to organize the client package. The folder structure shown here is a suggested handoff, not a claim that the app creates these folders or a manifest automatically.
Suggested delivery structure
iris-skincare-october/
01-routine/
routine-9x16.jpg
routine-1x1.jpg
02-introduction/
introduction-9x16.jpg
introduction-1x1.jpg
03-detail/
detail-9x16.jpg
detail-1x1.jpg
delivery-notes.txtBefore sending
Open the ZIP yourself.
- Count the expected files: three concepts in two placements means six finals.
- Open each export, check dimensions and inspect product details at full size.
- Match filenames to the brief and remove drafts, duplicates and private working notes.
- State what is licensed, where the client intends to publish and which revisions were included.
- Include the required AI/advertising disclosure notes; do not assume a platform preserves embedded metadata.
Use the UGC production walkthrough before the handoff, or the content calendar for an ongoing monthly delivery. For metadata details, read what is inside an AI image file.
Run the workflow
- 1
Create one collection per campaign
Before generating, create a collection named for the client, campaign, and month — “Acme — Spring Launch — May” beats “New stuff 3” every time you search for it later. Every render you keep goes straight into its campaign collection.
- 2
Tag as you generate
Add tags for hook, placement, and status while the context is fresh — tagging 200 images retroactively never happens. Collections keep each brief, reference set, and final export organized inside your account.
- 3
Curate down to a finals set
Keep a separate finals collection per campaign containing only deliverables. Drafts, near-misses, and B-roll stay in the working collection; the finals collection is what gets exported. This split is the difference between sending a client 12 assets and sending them 200.
- 4
Export the collection as a ZIP
Open the collection's detail view and use the download action — every asset in the collection is packaged into a single ZIP archive in one click. No per-image saving, no missing files. The Help Center covers export details.
- 5
Deliver with the license in order
Renders generated on any paid plan carry a commercial license, so your client can run them in ads and product listings. Free-tier exports are non-commercial — client work needs a paid plan, starting with Starter at 29 EUR/month.
Frequently asked questions
Follow along with 100 free credits
No card required. Explore showcase models with free credits. Product-reference ads and commercial delivery require a paid plan; model training has its own eligibility and credit cost.