ComfyUI: understand, install, troubleshoot

Nodes in ComfyUI: what a node is, what a good workflow is

A node is an operation; connected, nodes form a graph that shows the whole process. How to read a workflow, and why the best one is not the longest.

The building blocks of a workflow

A node is an operation.

It can load a model, receive a prompt, transform an image, sample, apply a LoRA or pass data on to another step of the workflow. Each node has inputs and outputs; an output only connects to an input of the same type. Connected to each other, nodes form a graph.

This representation makes visible a large part of the process that a classic generation interface keeps hidden: which model was loaded, in what order the operations happen, where an image comes in and where it goes out.

Reading a workflow

A workflow reads like a flow, from loading to saving. You almost always find the same families of operations in it:

• load: the model, its components, a LoRA, a start image;
• condition: encode the prompt, the references, a mask;
• generate: sample in latent space;
• decode: come back to a visible image;
• transform: correct an area, upscale, filter;
• save: write the result.

Once you know which family does what, an unknown graph stops being a wall of boxes: you look for where the model comes in, where the image goes out, and what happens in between.

Understand before you add complexity

A hundred-node workflow is not better than a ten-node one.

At Axiris, we understand the role of each block before adding complexity. A workflow becomes genuinely useful when it can be:

• understood;
• modified without breaking the rest;
• diagnosed when it fails;
• reused on another project;
• handed over to someone else;
• adapted to a new model.

This is also what makes the studio's method possible: building the image in steps and freezing what is validated. A graph you understand replays identically; a graph you do not understand gets relaunched at random. For what this allows in a graphic designer's work: Building the image by areas: the box, the mask, the layer.

Core nodes and extensions

ComfyUI ships with a set of nodes built into the project and maintained with it. Everything added on top comes from the community and is called a custom node: what an extension brings, what it costs and how to choose one is the subject of the page Custom nodes: the ComfyUI extensions.

Official reference: Documentation: Nodes.

And for your workflow?

A workflow is built on your projects, not on a downloaded example. Contact request: a first conversation, free and with no commitment. Every practice is different; it is by listening to you that we propose what suits you.