Contents

72 / 153

The ComfyUI Field Manual

Reading the graph

Chapter 71

2 min read

Reviewed v78 · August 2026

Everything in ComfyUI is a graph of nodes joined by typed wires. A node is one operation with inputs on its left and outputs on its right; a wire carries one kind of data from an output to a matching input, and the colors are the type system. Six types come up constantly: MODEL (the diffusion network itself), CLIP (the text encoder), VAE (the translator between pixels and latent space), CONDITIONING (an encoded prompt), LATENT (an image while it is still in the model's compressed working space), and IMAGE (actual pixels). A wire only connects an output to an input of the same type, which makes the graph self-documenting: if a connection is legal, it is because the data genuinely fits there.

Fig.diagram
MODELthe diffusion network that denoisesCLIPthe text encoder for your wordsVAEtranslator between pixels and latentsCONDITIONINGyour prompt, once encodedLATENTan image in compressed working spaceIMAGEactual pixels you can seeOUTINTHE COLOR IS THE TYPE. A WIRE ONLY JOINS AN OUTPUT TO AN INPUT OF THE SAME COLOR, SO IF IT CONNECTS, IT FITS.
Six kinds of data move through a ComfyUI graph, and a wire only joins an output to an input of the same kind.

You run a graph by queuing it. ComfyUI does not recompute the whole thing each time; it caches and re-executes only the nodes downstream of whatever you changed, which is why iterating on the last step of a long pipeline stays fast. And because a finished image carries its own recipe, dragging a PNG that ComfyUI generated back onto the canvas rebuilds the entire workflow that made it, seeds and all. Workflows are just JSON, so they travel as files or ride along inside the images themselves. That single fact, that an output is also its own reproducible source, is one of the quiet reasons the tool won.

Check your understanding

pass: 5 of 7

Answer at least 5 of 7 correctly to unlock the next chapter.

  1. 1. How is everything in ComfyUI structured?

  2. 2. In ComfyUI's type system, what does a LATENT wire carry?

  3. 3. What is the role of the VAE type in ComfyUI?

  4. 4. Why is the ComfyUI graph described as self-documenting?

  5. 5. Why does iterating on the last step of a long ComfyUI pipeline stay fast?

  6. 6. What happens when you drag a PNG that ComfyUI generated back onto the canvas?

  7. 7. In what format are ComfyUI workflows stored, allowing them to travel as files or inside images?

The weekly briefing

Get the week's moves in your inbox.

A short, sourced digest of what actually moved across generative AI, every week. Free.

Free. One email a week, no spam, unsubscribe anytime. Prefer a reader? RSS.