Named buckets for your generations — one per shoot, per drop, per client. File images into a project, filter the gallery by it, and export the whole thing as one ZIP with a manifest.
Three actions, none of which cost a credit.
Name it after the thing it is: "Diwali 2026", "Kurti drop 3", a client, a buyer. Up to 200 per account.
Select images in your gallery and add them to a project. New work can be filed as it is generated, including whole bulk batches.
Filter the gallery down to one project, archive a project when the season ends, or export the whole project as a single ZIP.
Every AI photo tool gives you one undifferentiated gallery. That works until the tenth SKU.
A project is the unit a catalogue seller actually thinks in — a drop, a season, a buyer, a client. The gallery filters down to it in one click.
"The Diwali range, zipped" is one action. You can export an explicit selection of images, or hand over a project id and get the whole collection.
Each archive ships a CSV mapping every file back to its source name, the tool that produced it, its generation id and its date — so the handoff to a listing pipeline or a VA is machine-readable.
Projects are free on every plan, including free. This is filing, not capability — charging for the ability to organise work you already paid to create would be the wrong kind of gate.
Finished seasons get archived rather than removed, so last Diwali's range is out of the way but still there when you need to re-list it.
One project per client keeps several catalogues apart in a single account, and each client's work exports on its own.
No on both counts. Projects are free on every plan, including the free plan, and creating, filing, filtering, archiving and exporting all cost 0 credits. This is filing rather than capability — charging for the ability to organise work you already paid to create would be the wrong kind of gate.
Up to 200 per account. That is an abuse guard rather than a plan feature.
Yes. You can export an explicit selection of images or hand over a whole project and get the entire collection as one ZIP, up to 50 images per archive.
A manifest.csv that maps every file in the archive back to its source name, the tool that produced it, its generation id and its creation date. A folder of images is not machine-readable; a folder plus a manifest is.
It is hidden from the default project list but nothing is deleted. The images stay in your gallery and the project can be listed again when you need it — useful for a season you will re-list next year.
Yes. A whole bulk run can be filed into one project, which is the natural pairing: generate twenty SKUs in a batch, keep them together as a collection, export them as one ZIP.
Name the shoot, file the images, export the collection. Free on every plan.