Nodes/comfyui_brick_tools/Save Brick Sequence
ComfyUI Node

Save Brick Sequence

Every frame of the shot, versioned, in a folder your whole team can find

By brick-momen-sirri·Created 4 months ago·Updated 3 months ago· 0
Save Brick Sequence
  • images
  • project_root
  • sequence_version_folder
  • version
project_name0000_base
model_prefix
shot_number0

When you're working in archviz, a "sequence" is a shot - a run of frames that will become a camera move. Save them with ComfyUI's default save node and they're scattered across output/ with counter suffixes. Save Brick Sequence (class SaveArchVizSequence) from comfyui_brick_tools - the free toolkit Brick Visual released from their studio pipeline - files every frame of a shot into a versioned folder with a name that actually tells you what it is.

What it produces

Give it a batch of images and a shot number, and it writes PNG frames to:

ComfyUI/output/projects/8140_The Edge_Riverside_Tower/
  sequences/SHOT_0007/
    20260312_8140_SHOT_0007_v001/
      0001.png
      0002.png
      ...

The shot_number integer becomes SHOT_0007 (padded to four digits), and each save bumps the version - save the same shot again and you get v002 in a fresh folder. Like the image saver, model_prefix is optional and inserts after the date, so 20260312_flux-2-dev_8140_SHOT_0007_v001/ is a valid folder.

The project_name dropdown and Create Project button behave exactly as in Save Brick Image: pick an existing project, or type a new one in the required ####_Office_Name_Project_Name format and it's created, selected, and refreshed for you.

Why a frame sequence beats a video file here

Raw frames are the right intermediate for a lot of pipelines. You can hand them to a frame-interpolator, an upscaler that works per-frame, or a video model that takes image sequences; you can also hold the sequence while you regenerate just the frames that were off. And because every frame gets the workflow embedded in its PNG metadata, you can drag any frame back onto the canvas and rebuild the exact graph that made it. That's the ComfyUI "the image is the project file" property, now organized per-shot.

The Download ZIP button

This is the frontend trick worth knowing: after the node has saved a sequence once, a Download ZIP button appears on it. Click it and the node zips the latest sequence that node instance saved and hands it to your browser. Handy for emailing a shot to a client or a teammate without making them dig through the folder tree. There's a catch - it tracks sequences per node instance, so if you save multiple shots from one node, it's always the most recent one. One node per shot keeps things predictable.

Outputs

project_root (the project folder), sequence_version_folder (the full path to the versioned shot folder), and version (the integer version). Wire the path into a display node or use it downstream.

Install

The whole pack installs in seconds - no models, no keys, no requirements.txt:

cd ComfyUI/custom_nodes
git clone https://github.com/brick-momen-sirri/comfyui_brick_tools

Restart ComfyUI and hard-refresh the browser (the ZIP button and Create Project dialog are frontend code). Manager users can search comfyui_brick_tools.

One gotcha carries over from the sibling nodes: 0000_base is a placeholder project and will error if you save to it, and your project name must match a real folder under ComfyUI/output/projects/. Set that up once and the sequence side of your workflow finally looks like a production archive instead of a junk drawer.

CategoryBrick/Save

Inputs (4)

NameTypeDefaultDescription
imagesIMAGE
project_nameCOMBO0000_base1 options: 0000_base
model_prefixSTRING
shot_numberINT00–9999

Outputs (3)

NameTypeDescription
project_rootSTRING
sequence_version_folderSTRING
versionINT