Naming and organizing your AI image outputs: a checklist
Folders per project, a file-name pattern, the prompt saved beside the picture, keepers vs drafts, archiving, and what the studio library cannot do.
After a week of generating, the folder looks like this: forty files with names made of random characters, three that are nearly identical, and no memory of which prompt made the good one. Nothing about it is a model problem. It is a filing problem, and a small habit fixes it.
This is a checklist. Work through it once for a project and the rest of the project files itself. First, what the studio does for you, so you know which parts of the job are yours.
What the studio library does and does not do
Every render you make lands in your library in the studio. Open one and you see the prompt, the model, the ratio, the output type, what it cost and the date. You can search by prompt text or model name, filter by photos, videos and other kinds, sort newest or oldest, and copy the prompt or reuse it. The library header also shows how many days renders are kept, so treat it as a window and not as an archive.
- No folders, no tags, no projects, no stars. The library is one flat list. Your project structure lives on your own disk.
- The file name is not yours to set. The downloaded file arrives with the studio's own name. Rename it after you save it.
- Settings are not stored in the file. The prompt, model and ratio stay in the library entry, not inside the picture. If you want them next to the image later, you have to save them yourself.
- A random seed is not shown back to you. If you pinned a number, you know it. If you left it random, it is gone, as the seed explainer covers.
1. One folder per project, three levels at most
Make a folder per project, not per day and not per model. A project is a thing with an end: a campaign, a book cover, a set of product shots. Inside it, keep three subfolders and no more.
- 01-drafts for everything you download while exploring.
- 02-keepers for the files you would actually use.
- 03-final for the finished, upscaled or edited versions that leave the project.
The numbers keep the folders in working order in every file browser. Deeper trees look tidy on day one and get ignored by day five.
2. One file-name pattern, used every time
Pick a pattern, write it at the top of the project folder, and never improvise. A pattern that works for most people has four parts in a fixed order: project, subject, version, and a date or seed.
autumn-sale_red-scarf_v03_s4821.png
autumn-sale_red-scarf_v04_2026-11-11.png- Lowercase, no spaces. It sorts the same everywhere and survives a trip through a web form.
- Zero-padded versions (v03, not v3) so version 10 does not sort before version 2.
- The seed only when you pinned it. A made-up number in the name is worse than none.
- Subject before version, so all versions of one subject sit together in a sorted list.
3. Keep the prompt next to the picture
The picture cannot tell you how it was made, and the library will not keep it for ever. Copy the prompt with the library's copy button and save it beside the file. The cheapest way is a single text file per project, with one block per keeper.
autumn-sale_red-scarf_v04
model: Still
seed: 4821
prompt: a red wool scarf on a birch bench, soft morning light, shallow depth of fieldIf you prefer one file per image, give the text file the same name as the picture with a different ending, so the two sort side by side. Either way the rule is the same: the prompt is saved the day the image is, not later.
4. Decide keeper or draft at download, not later
Most renders never need to leave the studio. A quick draft from Still Lite, which starts at €0.30, is there to be looked at and discarded; the library's delete button removes it in two presses. Download only what passes a quick test.
- Would I use this, or build on it? If yes, it is a keeper and goes straight to 02-keepers with its prompt.
- Is it close, with one thing wrong? Download it as a draft, name it, and fix it with an edit, as in refining instead of re-rolling.
- Neither? Delete it in the studio and do not look back.
5. Close the project, then archive
When a project ends, do five things in this order and you will thank yourself in a year.
- Move the finished versions to 03-final and check each one opens.
- Check that every keeper has its prompt note.
- Delete the weakest drafts from 01-drafts, but keep the two or three that show how you got there.
- Zip the project folder and name the archive after the project and the year.
- Copy the archive to a second place: an external drive or your own cloud storage. A folder in one place is not a backup.
Keeping the cost side tidy works the same way: the library shows what each render cost, and the project cost estimate post shows how to total it before you start.
What this cannot do
- The studio will not bulk-download a whole project or sort it into folders for you. Downloads are one file at a time, from each library entry.
- Nothing here puts the prompt inside the image file. If a picture is renamed or moved without its note, the link between them is lost.
- Deleting from the library cannot be undone, and renders are kept only for the number of days the library header shows. Download first, then clean up.
The habit in one line: a folder per project, a fixed name pattern, a prompt note saved the day the file is, and a decision at download. Start with your next render in the studio, or pick a model on the models page first.
Questions
Does the studio organize my AI images into folders?
No. The library is a flat list you can search by prompt or model, filter by kind and sort by date. Folders, names and tags are something you build on your own disk after downloading.
What should I put in an AI image file name?
Project, subject, version and either the seed or the date, in that order, lowercase with no spaces. Zero-pad the version so files sort correctly.
How do I keep the prompt that made an image?
Copy it from the library entry when you download the picture and save it in a text file next to the image. The prompt is not stored inside the image file itself.
How long does the studio keep my renders?
The library header shows the number of days renders are kept. Treat it as a short window, download what you want to keep and back it up somewhere of your own.
