ComfyUI
Build and reuse node-based generative-media workflows, preserving models, custom-node dependencies, and reviewable outputs.
- Image, Video & Audio
- Generative Media
- Images
- Video
Comfy Org: Node-Based Creative Tools
Develops ComfyUI and its open ecosystem for node-based generative-media workflows.
About Comfy Org
Comfy Org maintains the ComfyUI ecosystem, including the open core, frontend, and desktop distribution. These components support different parts of node-based media creation: graph editing, workflow execution, and access to a usable local application.
For work organized in Floatboat, study how a prepared brief becomes a bounded media-generation step and how its outputs return for review. Local execution, paid cloud services, and partner-model API nodes have different requirements. The core license does not grant rights to every model, extension, or generated asset.
Comfy Org Projects
ComfyUI represents media production as a reusable graph of explicit operations. Explore the workflow model alongside node and model dependencies, with representative inputs and output checks retained when moving a production recipe between machines or collaborators.
Explore Other Publishers
Meet other people and teams publishing open tools, projects, and Agent Skills.
Comfy Org FAQ
What does Comfy Org maintain?
ComfyUI is the representative project here. Its core, frontend, and desktop repositories form a related software ecosystem.
Why are core, frontend, and desktop kept together here?
They serve one product workflow but have different engineering responsibilities. A repository split alone does not require separate introductory pages.
Is ComfyUI a collection of Skills?
No. It is a node-based application and execution engine; instructions for an agent to operate it are a separate form of content.
Does a core license cover third-party model weights?
No. The core uses GPL-3.0; weights, custom nodes, API providers, and input media must be checked separately.
How do local and cloud offerings differ?
Local execution depends on your hardware and installed components. Hosted compute and partner API services have their own access and charges.
What should be checked before sharing a workflow?
Preserve the workflow, required models and node versions, representative inputs, and usage conditions for the assets being transferred.
Validate a ComfyUI Graph with One Sample
Open the ComfyUI guide to check runtime, models, and custom nodes. Run one representative input and inspect the saved output before planning a batch.