Cross-platformWorkflow & organisation

How to Track Prompts Across AI Image and Video Tools

By Marco Cavazzana · Updated · 4 min read
ShareEmail
Short answer

Keep one record per output with eight fields: platform, model or version, prompt, settings, references used, date, status and where the file lives. A dated folder per project plus one spreadsheet is enough. Local tools such as ComfyUI and A1111 embed the prompt in the image file; most web tools do not, so you must copy it at the moment you generate.

Anyone who uses more than one AI image or video tool eventually hits the same problem: a client asks for 'that version from last Tuesday, but with the blue background' and nobody can remember which platform made it, let alone the prompt. The fix is not a complicated tool. It is a habit of writing one record per output at the moment you make it, in a format you can search later. This guide gives you the fields, a folder-and-sheet system that works across every platform, and a note on which tools save metadata for you and which do not.

What to record for every output

Each generated image or clip you might ever want again deserves one row. Eight fields cover almost every case.

  1. Platform. Midjourney, Kling, Flux on a hosted service, ComfyUI locally, and so on.
  2. Model or version. The exact model name and version if the interface shows it, such as a Gen-4 variant, a Kling Professional mode, or a checkpoint filename. Models change monthly and the same prompt behaves differently on each.
  3. Prompt. The full text, including negative prompts and any parameters embedded in the prompt line.
  4. Settings. Aspect ratio, duration, resolution, seed, stylisation values, guidance, steps, camera preset, and anything else you changed from default.
  5. References. Filenames or links of any image, style reference, Element, Ingredient or audio you supplied.
  6. Date. When it was generated, so you can match it to the model that existed that day.
  7. Status. Draft, shortlisted, approved, delivered, rejected. This is the field clients care about.
  8. Location. Where the file is saved and its filename.

If that sounds like a lot, note that five of the eight can be copied and pasted in seconds. The discipline is doing it before you click generate again.

Which tools save the prompt for you

Tool typeExamplesPrompt stored in the file?What you must do
Local open-source UIsComfyUI, A1111 (Automatic1111), ForgeYes, usually as PNG metadata (the workflow or the generation parameters)Keep the original PNG; converting to JPEG or uploading to most services strips it
Hosted image toolsMidjourney, Flux hosted, Ideogram, Leonardo, ChatGPT images, GeminiMostly no; the prompt lives in the web interface or chat historyCopy the prompt and settings into your record as you generate
Hosted video toolsKling, Runway, Luma, Pika, Google Flow, HiggsfieldNo; the exported video carries no promptRecord prompt, model, duration and references per clip; name the file to match the row
Hosted model playgroundsReplicate, falSometimes a run log in the web interface, not in the fileCopy the input JSON into your record

Web histories are convenient until they are not: they are per account, they can be pruned, and they are useless when the account belongs to a freelancer who has moved on. Treat them as a backup, not the record.

A folder-and-sheet system

You need two things: a predictable folder structure and one spreadsheet per project. Keep both in the same shared drive the rest of the project uses.

Folders

  • ProjectName/ at the top.
  • 01-exploration/, 02-shortlist/, 03-approved/, 04-delivered/ for status. Move files forward; never copy, so there is one version of truth.
  • refs/ for every reference image, audio file and style sample you fed to any tool.
  • Filenames that carry the key facts: 2026-03-14_kling-pro_bottle-dolly_v3.mp4 reads as date, platform and model, subject, version.

The sheet

One row per output, one column per field above, plus a free-text notes column for what went wrong or right. Add a filter on status and a filter on platform, and you can answer 'show me every approved Midjourney image' in a click. For video, add a column for the source still, because the still is usually what you will reuse. If your team already lives in a project tool with custom fields, the same eight fields work there too.

Habits that make it stick

  • Record before you iterate. The moment you see a result you might keep, paste the prompt. Iterating first means losing the version you liked.
  • Copy the whole prompt, not a summary. Paraphrases cannot be re-run.
  • Save references with the output. A Runway References shot or a Kling Elements clip cannot be reproduced without the reference images.
  • Note the model when a platform updates. If a tool announces a new version, add a row in your notes so you know why older prompts changed behaviour.
  • Keep PNG originals from local tools. The embedded workflow is the most complete record you will ever have, and it is gone once you export to JPEG.

For client work, this record is also your evidence. Our guide on keeping a record of AI work for clients covers what to hand over and why.

Try it

Set up your sheet, then generate this prompt on two different platforms and fill a row for each. The point is the habit, not the picture.

A single green apple on a weathered wooden table, soft side light from a window, shallow depth of field, muted colours, photographic, no text

Change one setting on the second run, such as aspect ratio or a style value, and record it. Then close both tools, open your sheet and try to reproduce the first result from the row alone. Any field you could not fill is the one your system is missing.

Frequently asked questions

How do I keep track of AI prompts across different tools?
Keep one record per output with the platform, model or version, full prompt, settings, references, date, status and file location. A dated folder structure plus one spreadsheet per project is enough for most teams. Record at the moment you generate, because most web tools do not save the prompt inside the file.
Do AI image generators save the prompt in the image file?
Local tools such as ComfyUI and A1111 usually embed the prompt or workflow as PNG metadata, which survives as long as you keep the original PNG. Most hosted web tools, and all mainstream video platforms, do not store the prompt in the exported file. For those you must copy the prompt yourself.
What should an AI prompt log include?
At minimum the full prompt text, the platform and exact model version, every changed setting including seed where available, the references you supplied and the date. Add a status field so you can separate drafts from approved and delivered work. Filenames that carry date, platform and subject make the log searchable.

Nothing you makeis lost.

Free · No card · Read-only · 2-minute setup

DreamdriveFree plan · Chrome
Add to Chrome — it’s free