How do you follow the steps behind an image?
A node is one box in the workflow. The lines show what each box passes to the next. In the first-image guide, one box loads the model, the workflow uses the description to generate the image and a final box saves it. Start by tracing those steps so you know what to inspect if an image never appears.
When does the workflow leave your computer?
A local workflow with local models can run on your hardware. Partner Nodes call supported outside models and can use Comfy Credits even from a local install. Comfy Cloud runs the workflow on hosted hardware. Before adding an unreleased reference image, check where every step runs and which service will receive it.
The core is open source under GPL-3.0. Local work still needs compatible hardware and the relevant model files. Cloud credits cover active graphics processor time and Partner Nodes. Cloud supplies a fixed set of supported custom nodes, so a local workflow using an unavailable add-on may need to change before it can run there.
What should you save so a teammate can reopen the workflow?
Save the image and the workflow JSON, a text file describing the steps. Keep a separate list of required model files and any add-ons, with their versions and terms. Saving the workflow does not bundle those dependencies.
By default the Save Image step writes workflow information into PNG files. Inspect the exported copy and remove unintended embedded details before public sharing.
What should you look for when an image never appears?
On paper, draw boxes for a local model, a description of a fictional flower pot, and an image file. Use no downloaded workflow, model, real upload or external account.
- Trace the expected resultFollow each line from the model and description to the file.
- Cross out the modelMark where the run should stop if the named model file is missing. The expected result is a dependency warning and no new image. Actual generation remains untested.