Organise a ComfyUI film project

Start with one project root

For a small film, separate reusable references from shot-specific attempts. Here is a suggested manual structure; it is not Velvet Avocado’s on-disk format:

archive-film/
  references/
    evelyn/
    archive-location/
  shots/
    010-entry/
      take-01/
        output.mp4
        workflow.json
        notes.md
    020-close-up/
  edit/
    selects.md

Keep shared model files in your existing ComfyUI model directories rather than copying large checkpoints into every film. Record which files and versions a workflow needs so you can reconstruct the environment later.

Save the workflow with the take

When you keep an output, save the workflow you ran at the same time. Give the attempt its own folder so later graph changes do not overwrite the record of an earlier result.

A short notes.md might contain:

Shot: 010-entry
Take: 01
Action: Evelyn enters the archive and stops at the doorway.
References: evelyn/front-approved.png; archive-location/doorway.png
Workflow: workflow.json
Environment: record ComfyUI and custom-node versions here
Models: record exact model filenames and versions here
Decision: selected for the rough cut; check the coat at the next cut

Include the seed and important generation settings when available. Keep copies of the exact references used, or stable versioned paths to them. If you overwrite front-approved.png next week, a note pointing to that filename alone will no longer identify the original input.

The graph is only part of the record. It also depends on model files, custom nodes, inputs, and their versions. Recording those dependencies improves repeatability; it does not guarantee identical output across different environments.

Make the editorial choice explicit

Suppose you generate six attempts at Evelyn entering the archive. Take four has the right movement; take six has a better face but a different coat.

Record which one you selected and why. Your editor needs an unambiguous path to the chosen file, not a directory full of increasingly hopeful filenames. Keep rejected attempts separately from your selects, especially if their prompts or settings may be useful later.

Review the selected entry shot beside the close-up. The character continuity guide includes a short checklist for that comparison.

Add Velvet Avocado when you want a shared project home

Velvet Avocado provides a local project for organising characters, locations, references, and generated media, with an Editor for assembling a sequence. Compatible ComfyUI workflows can be a generation route alongside connected cloud providers.

A practical way to introduce it is:

1. Start a small Velvet Avocado project and organise the character and location references you will reuse.
2. Choose a compatible ComfyUI workflow and check its required models, nodes, and inputs in your ComfyUI installation.
3. Run a test generation and inspect the output and the generation information available for that workflow.
4. Keep the workflow and environment record described above, then bring your chosen media into the edit.

Compatibility matters: an arbitrary graph with custom nodes is not automatically supported. Keep using ComfyUI directly for graph development and experiments that need its full control surface.

A useful end-of-session check

Before closing the project, pick one selected take and ask:

• Can I find the exact input references?
• Do I have the workflow and a record of its dependencies?
• Is the editorial decision clear?
• Can I find this take from the shot name without searching the whole output directory?

If those answers are yes, you have a usable production record whether you manage it with folders, Velvet Avocado, or a combination of both.