Save Brick Video
Your Wan and LTX clips, filed like a real archviz pipeline
- video
- project_root
- saved_video_path
- version
So you've rendered a passable camera move out of Wan or LTX. Now what? If you're like most people, you're feeding it into ComfyUI's plain save-video node and getting ComfyUI_00013_.mp4 dropped into a folder that holds every video you've ever made. Save Brick Video (class SaveArchVizVideo) from comfyui_brick_tools - the free toolkit from archviz studio Brick Visual - gives video clips the same production treatment as the pack's image and sequence savers: project folders, shot numbers, versioning, and sensible filenames.
How it fits your video pipeline
The node takes ComfyUI's native VIDEO input - the same type the built-in Save Video node accepts - so it drops straight into any modern video workflow. It saves to:
ComfyUI/output/projects/8140_The Edge_Riverside_Tower/
videos/SHOT_0007/
20260312_8140_SHOT_0007_v001.mp4
shot_number becomes SHOT_0007 and the version auto-increments per shot. The format (auto/mp4) and codec (auto/h264) dropdowns match the core Save Video node's choices - leave them on auto and you'll get a sensible default. If your pipeline starts from frames rather than a video node, the README is explicit: build the VIDEO first with ComfyUI's video nodes (video combine/encode), then connect it here. This node files finished video, it doesn't encode frames for you.
The outputs mirror the other savers: project_root, saved_video_path, and version - all of which are handy for logging, naming, or downstream display.
The one real requirement
This is the gotcha that will bite you: the VIDEO type is from ComfyUI's newer video API, so you need a reasonably recent ComfyUI. If you're on a version from before the native video type landed, this node simply won't appear (or will error on load) - update ComfyUI first, then install the pack. It's the only dependency the pack has; there are no model downloads, no API keys, no requirements.txt.
Metadata, done properly
Like the pack's image saver, this node embeds the workflow and its own archviz_saver payload into the video's metadata (unless you run ComfyUI with --disable-metadata). For PNGs that's what lets you drag an image back and rebuild the graph; for videos it means your shots carry their provenance into the studio's Brick Browser, which reads it back for previewing and re-loading workflows. Keep the originals.
Install
Same as the rest of the pack:
cd ComfyUI/custom_nodes
git clone https://github.com/brick-momen-sirri/comfyui_brick_tools
Restart ComfyUI and hard-refresh the browser - the pack ships frontend JS (the Create Project button and Brick Browser sidebar). ComfyUI Manager users can search comfyui_brick_tools. Then use the Create Project button on the node (or make the folder yourself) because, as with the image and sequence savers, the default 0000_base is a placeholder that errors if you try to save to it.
For anyone producing archviz clips that have to survive contact with a client review, having every take land in videos/SHOT_0007/ with a date, project code, and version in the filename is worth the two minutes of install by itself.
Inputs (6)
| Name | Type | Default | Description |
|---|---|---|---|
| video | VIDEO | — | |
| project_name | COMBO | 0000_base | 1 options: 0000_base |
| model_prefix | STRING | — | |
| shot_number | INT | 00–9999 | — |
| format | COMBO | auto | 2 options: auto, mp4 |
| codec | COMBO | auto | 2 options: auto, h264 |
Outputs (3)
| Name | Type | Description |
|---|---|---|
| project_root | STRING | — |
| saved_video_path | STRING | — |
| version | INT | — |