Template Image

Every pack ships its own little conveniences, and this is StudioDeep's: a node that loads a bundled reference image straight into your graph as an IMAGE tensor. It currently exposes exactly one template - character-consistency-moodboard.png, a 3200×1800 layout guide the pack ships in its templates/ folder - and its whole job is to make that file available to your workflow without you hunting for a path on disk.

It sounds trivial, and it kind of is. But there's a real workflow reason it exists: this pack's loop is reference → panels → moodboard → regenerate, and a layout template is the thing you want sitting behind your composition so every project starts from the same structure. The node turns that constant into a one-wire convenience instead of a "where did I save that PNG" ritual.

How it works

The node scans the templates/ directory for image files (.png, .jpg, .jpeg, .webp) and exposes them in the template dropdown. Pick one, and it loads the file with PIL, converts it to a [1, H, W, C] float32 tensor, and hands it out as image. It's a pure file loader - no resizing, no compositing, no AI. What you do with the loaded image is up to your graph.

Inputs: template (dropdown). Output: image (IMAGE).

Installing

Standard StudioDeep install:

cd ComfyUI/custom_nodes
git clone https://github.com/studiodeep-ai/comfyui-studiodeep StudioDeep
pip install -r StudioDeep/requirements.txt

or ComfyUI Manager → "StudioDeep", then restart. The template ships with the repo, so it's there the moment the pack is.

Troubleshooting

• Dropdown shows (none) - templates/ isn't being found, almost always because the pack landed somewhere odd after a manual clone. The folder must sit beside nodes/.
• Adding your own template - drop any PNG/JPG/WebP into templates/ and restart. The dropdown is generated from the folder contents, so your file shows up automatically. That's the intended way to use this for your own brand or layout.

The honest take: this is a thin node for a thin need. If you never generate from a shared template, you can skip it without losing anything. But if you're building repeatable, on-brand pipelines - which is very much this pack's personality - having your layout reference as a node instead of a file path is the sort of small nicety you stop noticing, which is the highest compliment a utility node can get.