# ComfyUI

> Source: https://aiwiki.ai/wiki/comfyui
> Updated: 2026-06-21
> Categories: Developer Tools, Generative AI, Image Generation, Open Source AI
> From AI Wiki (https://aiwiki.ai), a free encyclopedia of artificial intelligence. Quote with attribution.

**ComfyUI** is a free, [open-source](/wiki/open_source_ai) node-based graphical user interface and backend for [generative AI](/wiki/generative_ai) workflows, primarily focused on [image generation](/wiki/ai_image_generation) using [diffusion models](/wiki/diffusion_models) such as [Stable Diffusion](/wiki/stable_diffusion) and [FLUX](/wiki/flux). Created by a developer known as comfyanonymous and first released on GitHub on January 16, 2023, ComfyUI lets users build complex image and video generation pipelines by connecting visual nodes in a graph-based editor.[1][2] Each node represents a discrete operation (loading a model, writing a prompt, applying a sampler, and so on), and the connections between nodes define the data flow of the entire generation process.

ComfyUI has grown into one of the most widely used tools in the AI image generation ecosystem. As of early 2026 it had accumulated over 106,000 stars and 12,300 forks on GitHub, and by April 2026 its developer organization, Comfy Org, reported more than 4 million users worldwide.[1][20][21] It supports a broad range of generative models and serves as the preferred interface for new model releases from organizations like [Black Forest Labs](/wiki/black_forest_labs) and [Stability AI](/wiki/stability_ai), which frequently ship same-day ComfyUI support.[1][20] The software is licensed under the GNU General Public License v3.0 ([GPLv3](/wiki/gpl)).[1]

## What is ComfyUI used for?

ComfyUI is used to design, run, and share generative AI pipelines that go beyond a single text-to-image prompt. Because each step of the diffusion process (model loading, text encoding, sampling, decoding, conditioning, and post-processing) is exposed as a separate node, users assemble custom workflows for tasks such as image generation, [ControlNet](/wiki/controlnet)-guided composition, upscaling, inpainting, face restoration, video generation, and audio generation. The same visual workflow can be executed programmatically through an API, which makes ComfyUI equally suited to interactive experimentation and production automation. As of December 2024 the core application shipped with 1,674 built-in node types, and the community has added thousands more.[8]

## History and Origins

### Early Motivation

ComfyUI originated from the personal curiosity of its creator, comfyanonymous. In October 2022, comfyanonymous discovered Stable Diffusion and began experimenting with it using the existing [AUTOMATIC1111](/wiki/automatic1111) Stable Diffusion Web UI, which was the dominant interface at the time.[2] Despite having no prior experience with [PyTorch](/wiki/pytorch) or diffusion model internals, comfyanonymous found the AUTOMATIC1111 codebase limiting when attempting advanced modifications, such as testing different samplers or chaining upscaling processes.[2] The frustration with rigid, form-based interfaces for complex diffusion pipelines motivated the development of a more flexible tool.

As comfyanonymous later described, the design philosophy was straightforward: "Everyone is trying to make easy to use interfaces. Let me try to make a powerful interface that's not easy to use."[2] The goal was to build a tool that exposed the full internals of the diffusion pipeline, giving users fine-grained control over every step of image generation.

### When was ComfyUI released?

Comfyanonymous began writing the code on January 1, 2023, and published the first version on GitHub on January 16, 2023.[2] The initial release provided a basic node-based interface where users could wire together model loading, text encoding, sampling, and image decoding nodes to produce images through Stable Diffusion. The project quickly attracted attention from the AI art community because of its transparency: rather than hiding the generation pipeline behind a simplified form, ComfyUI made every component visible and configurable.

### Growth and Stability AI Connection

ComfyUI grew rapidly during 2023 as the Stable Diffusion community adopted it for complex workflows that were difficult or impossible to replicate in other interfaces. Comfyanonymous had an involvement with Stability AI during this period. By June 3, 2024, that involvement had ended, and the creator shifted focus entirely to the open-source project.[7]

### Formation of Comfy Org

As the project grew, comfyanonymous decided to formalize the effort. On June 21, 2024, Comfy Org was officially formed as a dedicated organization to steward the project.[7] The founding team was announced by Yoland Yan (co-founder and CEO) and included several well-known figures from the Stable Diffusion community:[7][9]

| Team Member | Role | Background |
|---|---|---|
| comfyanonymous | Creator of ComfyUI, Co-founder | Originally experimented with Stable Diffusion in October 2022; software engineer with a web development background |
| Yoland Yan | Co-founder, CEO | Former Search ML engineer at Google; Chromium committer; creator of ComfyCLI |
| mcmonkey4eva (Alex Goodwin) | Core developer | Creator of SwarmUI; former ML engineer at Stability AI |
| Dr. Lt. Data | Core developer | Creator of ComfyUI-Manager and the Impact/Inspire Pack |
| pythongosssss | Core developer | Major contributor to ComfyUI; creator of ComfyUI-Custom-Scripts |
| Robin | Co-founder | Creator and maintainer of the Comfy Registry; former Google Cloud engineer |

In August 2024, Comfy Org joined the Open Model Initiative, a project organized by the Linux Foundation to promote open AI model standards.[9]

### How is ComfyUI funded?

On September 16, 2025, Comfy Org announced that it had raised $17 million in funding from investors including Pace Capital, Chemistry, Abstract Ventures, and Essence VC. Notable backers include Guillermo Rauch (creator of [Vercel](/wiki/vercel)).[5] The funding is directed toward stabilizing the custom node ecosystem, shipping a refined user interface, building Comfy Cloud (a cloud-hosted version for users without powerful local hardware), and maintaining support for emerging AI models.[5]

On April 24, 2026, Comfy Org announced a second round of $30 million at a $500 million post-money valuation, led by Craft Ventures with participation from Pace Capital, Chemistry, and TruArrow.[21][22] The round brought total funding to roughly $47 million across two rounds in about eighteen months, and the company reported that ComfyUI had surpassed 4 million users.[21][22] In its announcement, the company framed the raise around production-grade open creative AI, with TechCrunch reporting that the round reflected demand from creators who "seek more control over AI-generated media" than closed, prompt-only tools provide.[22]

The team has described their vision as building "the OS of creative AI," emphasizing the principle that "open source lasts forever" and prioritizing community empowerment over proprietary lock-in.[9]

## Architecture and Technical Design

### Node-Based Graph System

At its core, ComfyUI represents generation pipelines as directed acyclic graphs (DAGs). Each node in the graph performs a single function: loading a checkpoint, encoding a text prompt with a [CLIP](/wiki/clip) model, configuring a sampler, decoding a latent image through a [VAE](/wiki/variational_autoencoder), and similar operations.[8] Nodes have typed input and output slots, and users connect them with wires to define data flow. This architecture means that every aspect of the diffusion process is both visible and modifiable.

The node-based paradigm draws inspiration from tools like Blender's compositor and Unreal Engine's Blueprint visual scripting system. Typical node types include:

- **Checkpoint Loader**: loads a diffusion model from a `.safetensors` or `.ckpt` file
- **CLIP Text Encode**: converts a text prompt into conditioning tensors
- **KSampler**: runs the denoising loop with configurable sampler and scheduler
- **VAE Decode**: converts latent representations back into pixel images
- **ControlNet Apply**: applies [ControlNet](/wiki/controlnet) guidance to the diffusion process
- **LoRA Loader**: merges [LoRA](/wiki/lora) weights into the active model
- **Upscale**: enlarges images using models like RealESRGAN or SwinIR

Users connect the output ports of one node to the input ports of another, forming a directed acyclic graph. Workflows commonly consist of tens of nodes, and complex production setups can contain hundreds. As of December 2024, the core application supported 1,674 built-in node types.[8]

The graph-based approach offers several advantages over traditional form-based interfaces:

- Users can see exactly how data moves through the pipeline
- Complex workflows involving multiple models, ControlNet conditioning, upscaling passes, and post-processing can be built by wiring nodes together
- Workflows are reproducible and shareable as JSON files
- New capabilities can be added by creating custom nodes without modifying the core codebase

### Python Backend and Execution Engine

The backend is written in Python and built on top of PyTorch. It handles all computational tasks: model loading, tensor operations, GPU/CPU scheduling, and the execution of the diffusion process. The backend is designed to be hardware-agnostic:[8]

| Hardware | Framework | Notes |
|---|---|---|
| [NVIDIA](/wiki/nvidia) GPUs | [CUDA](/wiki/cuda) | Primary target; best performance |
| AMD GPUs | ROCm (Linux), DirectML (Windows) | Linux support mature; Windows experimental |
| Intel Arc GPUs | Intel Extension for PyTorch | Community-tested |
| Apple Silicon | [MPS](/wiki/metal_performance_shaders) (Metal) | macOS native acceleration |
| Ascend NPUs | CANN | Huawei hardware support |
| CPU only | PyTorch CPU | Functional but slow |

ComfyUI's execution engine processes the graph intelligently. It analyzes the node graph, determines the execution order through topological sorting, and uses a key optimization called **selective re-execution**: when a user modifies one node, only that node and its downstream dependents are re-processed, while cached results from unchanged branches are reused.[8] This dramatically reduces iteration time during prompt experimentation.

### Memory Management

ComfyUI employs dynamic memory management and intelligent VRAM offloading. When GPU memory is limited, it can automatically move model weights between GPU and system RAM as needed. According to the official documentation, ComfyUI can automatically run large models on GPUs with as little as 1 GB of VRAM through smart offloading.[8] This allows users with lower-end hardware to run models like [SDXL](/wiki/stable_diffusion) that would otherwise require 8 GB or more of dedicated video memory.

### Web Frontend

The frontend is a web-based application that provides the visual canvas for building and running workflows. Originally written in vanilla JavaScript, the frontend was rewritten and migrated to a separate repository in August 2024, rebuilt using TypeScript and Vue.js.[17] The compiled JavaScript is served from the `web/` directory within the main repository.

The frontend communicates with the backend through both REST API endpoints and WebSocket connections. This client-server architecture means the frontend is essentially just one possible client for the ComfyUI backend; any application that can speak HTTP and WebSocket can control ComfyUI programmatically.

### File Format and Portability

Workflows are stored as JSON files. ComfyUI can also embed the full workflow JSON inside generated PNG and WebP images as metadata. This means any image produced by ComfyUI carries its own recipe: dragging the image back into the ComfyUI canvas reconstructs the entire node graph that created it. There are two main export formats:

- **workflow.json**: The full workflow export that includes all nodes, their positions, links, UI elements, and group information
- **workflow_api.json**: A streamlined export designed for API execution that strips out UI details and retains only the essential node configurations and connections

## Supported Models

One of ComfyUI's defining strengths is its broad and rapidly updated model support. Because the node-based architecture separates model loading from the rest of the pipeline, adding support for new model architectures typically requires only new or updated nodes rather than a full interface redesign.

### Image Generation Models

| Model Family | Developer | Key Details |
|---|---|---|
| [Stable Diffusion](/wiki/stable_diffusion) 1.5 | Stability AI / CompVis / Runway | 860M parameter UNet; the original widely adopted open-source diffusion model; 512x512 default resolution |
| [Stable Diffusion XL](/wiki/stable_diffusion) (SDXL) | [Stability AI](/wiki/stability_ai) | 3.5B parameter base + refiner; higher quality outputs at 1024x1024 default resolution |
| Stable Diffusion 3 / 3.5 | Stability AI | Uses the MMDiT (Multi-Modal Diffusion Transformer) architecture; improved text rendering and composition; natively supported in ComfyUI |
| Stable Cascade | Stability AI | Wurstchen-based three-stage generation pipeline |
| [FLUX](/wiki/flux) (Schnell, Dev, Kontext, Fill, Redux) | [Black Forest Labs](/wiki/black_forest_labs) | Transformer-based high-quality model family; Schnell optimized for speed; ComfyUI was the first interface to support FLUX on launch day |
| PixArt-alpha / PixArt-Sigma | PixArt | Efficient DiT-based text-to-image models |
| AuraFlow | Fal.ai | Open-source flow-matching model |
| HunyuanDiT | Tencent | Chinese and English bilingual diffusion transformer |
| OmniGen | Various | Supported from ComfyUI v0.2.6 onward |

### Video Generation Models

ComfyUI has expanded well beyond static images. The following video generation models are natively or community-supported:

| Model | Developer | Details |
|---|---|---|
| [AnimateDiff](/wiki/animatediff) | Guoyww et al. | Motion modules that extend SD 1.5 / SDXL to produce 2 to 16 second animated clips |
| Stable Video Diffusion (SVD) | Stability AI | Image-to-video; base model generates 14 frames at 1024x576; XT variant generates 25 frames |
| [Wan 2.1](/wiki/wan) / Wan 2.2 | [Alibaba](/wiki/alibaba_cloud) | Natively supported; 1.3B and 14B parameter variants; text-to-video and image-to-video; Wan 2.2 added Mixture-of-Experts architecture |
| CogVideoX | Tsinghua / Zhipu AI | Available in 2B and 5B variants; generates 6-second clips at 720x480 |
| Mochi | Genmo | Open-source video diffusion model |
| LTX-Video | Lightricks | Fast video generation; LTX 2.3 supports audio-synced 4K video at 50 FPS |
| HunyuanVideo | Tencent | High-quality open video generation model |

### Audio and 3D Models

ComfyUI's scope has continued to broaden beyond images and video. Audio generation is supported through models based on the Stable Audio architecture, using specialized 1D convolutional VAEs and DiT (Diffusion [Transformer](/wiki/transformer)) models. ACE-Step provides music generation with fine-tuning support through LoRA and ControlNet for audio editing, vocal synthesis, accompaniment production, and style transfer. LTX 2.3 introduced native audio-video synchronization capabilities.[19]

For 3D content creation, Hunyuan3D 2.0 (Tencent's open-source 3D voxel generation model) and Rodin3D Gen-2 allow image-to-3D mesh generation directly within ComfyUI workflows.

### ControlNet and Conditioning

ControlNet models give users precise spatial control over the generation process. ComfyUI supports ControlNet variants for multiple base models:

- **SD 1.5 ControlNets**: Canny edge, depth map, OpenPose skeleton, scribble, segmentation map, normal map, MLSD line detection, and more
- **SDXL ControlNets**: ControlNet Union (combining Canny, OpenPose, Depth, LineArt, Scribble, HED, and others into a single model), plus dedicated single-task ControlNets
- **SD 3.5 ControlNets**: Blur, Canny, and Depth variants released by Stability AI in November 2024[15]
- **FLUX ControlNets**: Models by XLabs-AI, InstantX, and Jasperai covering edge detection, depth maps, and surface normals

Additional conditioning tools include [IP-Adapter](/wiki/ip_adapter) for image prompt-based style transfer, T2I-Adapter for lightweight structural guidance, and regional prompting nodes for applying different prompts to different areas of an image.

## Custom Node Ecosystem

The custom node system is one of ComfyUI's defining strengths. Any Python developer can create new node types by writing a class with defined input/output types and a processing function. The ComfyUI community has produced thousands of custom node packages covering use cases from face swapping and video interpolation to prompt scheduling and batch automation.

### ComfyUI-Manager

ComfyUI-Manager, created and maintained by Dr. Lt. Data, is the primary tool for discovering, installing, updating, and managing custom nodes.[10] It provides a searchable interface within ComfyUI itself, allowing users to browse available node packages, install them with one click, and manage dependencies. ComfyUI-Manager ships by default with the ComfyUI Desktop application. Version 3.3.2 introduced an overhaul with official support for the Comfy Registry, where code-reviewed nodes can be installed without triggering security checks.[10]

### Comfy Node Registry

Launched by Robin (one of the Comfy Org co-founders), the Comfy Node Registry (registry.comfy.org) provides a centralized, curated repository for custom nodes.[6] As of late 2024, over 800 custom node authors had published on the Registry, with more than 2,000 node versions available.[11] Nodes published through the Registry undergo code review, reducing the security risks associated with installing arbitrary code from GitHub repositories.[6] ComfyUI-Manager supports installing directly from the Registry with semantic versioning.[11]

### Notable Custom Node Packages

| Package | Author | Description |
|---|---|---|
| ComfyUI-Impact-Pack | Dr. Lt. Data | Detection, segmentation, and face restoration tools |
| ComfyUI-Inspire-Pack | Dr. Lt. Data | Advanced prompt scheduling, regional prompting, and creative tools |
| ComfyUI-AnimateDiff-Evolved | Kosinkadink | Advanced AnimateDiff integration with scheduling and batching |
| ComfyUI-Custom-Scripts | pythongosssss | UI enhancements, image feed, auto-arrange, and workflow tools |
| WAS Node Suite | WASasquatch | Over 210 utility nodes for math, text, image manipulation, and more |
| ComfyUI-IPAdapter-Plus | cubiq | IP-Adapter support for style and composition transfer |
| ComfyUI-KJNodes | kijai | Utility nodes for masks, batch processing, and conditioning |
| ComfyUI-VideoHelperSuite | Kosinkadink | Video loading, saving, and frame manipulation utilities |

### Ecosystem Security

The openness of the custom node system is one of ComfyUI's greatest strengths, but it also introduces security considerations. Because custom nodes are Python code executed on the user's machine, malicious nodes can potentially cause harm. The ComfyUI community and Comfy Org have responded with the Registry's code review process, community verification flags in ComfyUI-Manager, and security advisories for known threats.

## How does ComfyUI differ from AUTOMATIC1111?

[AUTOMATIC1111](/wiki/automatic1111) Stable Diffusion Web UI was the dominant open-source interface for Stable Diffusion from mid-2022 through much of 2023. ComfyUI emerged as a serious alternative in 2023 and gradually overtook AUTOMATIC1111 in adoption, particularly among advanced users and professional workflows.[13] In short, ComfyUI is a node-based graph editor built for flexible, reproducible, multi-step pipelines and headless automation, whereas AUTOMATIC1111 is a form-based interface optimized for quick, straightforward generation. The following table summarizes the key differences.

| Feature | ComfyUI | AUTOMATIC1111 Web UI |
|---|---|---|
| Interface style | Node-based graph editor | Form-based web UI (built with [Gradio](/wiki/gradio)) |
| Learning curve | Steeper; requires understanding of diffusion pipeline components | Lower; straightforward tabs and fields for common operations |
| Workflow flexibility | Highly flexible; users can build arbitrary pipelines | Limited to predefined workflows with extension support |
| Performance (SDXL 1024x1024, 20 steps) | ~8.2 seconds | ~10.9 seconds |
| VRAM efficiency | ~14% lower peak usage on average | Higher peak VRAM consumption |
| Minimum VRAM for SDXL | ~6 GB (with smart offloading) | ~8 GB |
| Selective re-execution | Yes; only changed nodes re-run | No; full pipeline re-runs each time |
| New model support | Typically same-day or next-day | Often requires community extensions; slower adoption |
| Extension/node count | 2,000+ custom node packages | ~305 extensions |
| Workflow sharing | Native JSON export; embeds in images | Settings can be saved as presets |
| API/headless mode | Built-in REST and WebSocket API | API available via `--api` flag |
| Desktop application | Yes (Electron-based, cross-platform) | No native desktop app |
| Video generation | Supported via built-in and custom nodes | Limited; primarily via extensions |
| Primary language | Python (backend), TypeScript/Vue.js (frontend) | Python (backend and frontend via Gradio) |
| License | GPL-3.0 | AGPL-3.0 |
| Development activity | Very active; weekly releases; backed by Comfy Org with $47M raised | Development slowed significantly since mid-2024 |
| Best suited for | Advanced users, complex pipelines, production automation | Beginners, quick generation, straightforward workflows |

### Why ComfyUI Became Dominant

Several factors contributed to ComfyUI overtaking AUTOMATIC1111 as the preferred tool for many AI image generation users:[13]

1. **New model adoption speed.** When Black Forest Labs released FLUX in August 2024, ComfyUI had support on day one. AUTOMATIC1111 was significantly slower to integrate new architectures, and some models (like FLUX and SD3) were never fully supported in the main branch.[12]

2. **Workflow reproducibility.** ComfyUI's JSON workflow format made it trivial to share and reproduce exact generation pipelines. This became increasingly important as workflows grew more complex, involving multiple models, ControlNet conditioning, upscaling, and post-processing.

3. **Professional and production use.** The API-first architecture and headless operation mode made ComfyUI attractive for studios, production pipelines, and automated systems. AUTOMATIC1111 was designed primarily as an interactive tool.[14]

4. **Active development.** AUTOMATIC1111's development pace slowed noticeably after mid-2024. ComfyUI, backed by a funded organization, maintained a weekly release cadence.[13]

5. **Community momentum.** As more users and tutorial creators moved to ComfyUI, the ecosystem of shared workflows, custom nodes, and educational content grew rapidly, creating a self-reinforcing cycle.

6. **NVIDIA partnership.** NVIDIA's announcement at Computex 2024 that it would support ComfyUI within its RTX Remix modding toolkit, along with [TensorRT](/wiki/tensorrt) acceleration providing up to 60% speed improvements on RTX GPUs, further cemented ComfyUI's position.

Many users continue to run both tools. AUTOMATIC1111 remains popular for its approachability and for tasks like simple text-to-image generation and inpainting. ComfyUI tends to be preferred for multi-model pipelines, batch production, and workflows that combine image generation with ControlNet guidance, upscaling, and face restoration in a single graph.

## Workflow Sharing

ComfyUI's JSON-based workflow format has become a standard for sharing generative AI pipelines across the community.

### Embedded Image Metadata

Every image generated by ComfyUI can contain the full workflow JSON embedded as PNG or WebP metadata. When someone drags a ComfyUI-generated image onto the canvas, the application reconstructs the exact node graph, connections, and parameter values that produced that image. This feature makes workflows inherently portable: sharing an image is equivalent to sharing its entire production recipe.

### JSON Export and Import

Users can export workflows as standalone `.json` files through the ComfyUI menu. These files can be version-controlled with [Git](/wiki/git), posted to forums, or bundled with tutorials. Importing a JSON file reconstructs the full graph, though users still need to download any referenced models and custom nodes separately. In the Desktop application, workflows can embed model URLs or registry IDs so that missing models are downloaded automatically.

### Community Platforms

Several platforms serve as hubs for ComfyUI workflow sharing:

| Platform | Description |
|---|---|
| [OpenArt](/wiki/openart) | Hosts the largest dedicated ComfyUI workflow collection with a searchable database containing thousands of workflows |
| [Civitai](/wiki/civitai) | Model-sharing platform that increasingly hosts ComfyUI workflows alongside related LoRAs and checkpoints |
| Reddit (r/comfyui) | Active subreddit with workflow sharing, troubleshooting, and showcase posts; over 148,000 members |
| Discord (Comfy Org) | Official Discord server with 53,000+ members and dedicated channels for workflow sharing and support |
| GitHub repositories | Many creators publish workflow collections as open-source repositories |
| YouTube | Hundreds of tutorial creators demonstrate and share workflows through video walkthroughs |

## API Mode

ComfyUI was designed with an API-first architecture. The backend exposes a Python HTTP server with both REST and [WebSocket](/wiki/websocket) endpoints, meaning the graphical interface is simply one client among many that can communicate with the backend.[14]

### REST API

The primary endpoint for workflow execution is `POST /prompt`, which accepts a workflow graph as a JSON payload. Each node in the JSON is identified by a unique ID and specifies its `class_type`, input values, and connections to other nodes. The server queues the request, executes the graph, and returns the generated outputs. Additional endpoints allow clients to query the node type registry, check queue status, retrieve generated images, and manage the execution history.

| Endpoint | Method | Purpose |
|---|---|---|
| `/prompt` | POST | Submits a workflow graph for execution; returns a `prompt_id` |
| `/object_info` | GET | Returns the complete node class library with inputs, outputs, default values, and documentation |
| `/history` | GET | Retrieves execution history and results |
| `/view` | GET | Serves generated images and other outputs |
| `ws://.../ws` | WebSocket | Provides real-time execution progress updates |

### WebSocket Interface

Clients can open a WebSocket connection to `ws://<host>:<port>/ws` to receive real-time progress updates during generation. The server sends messages indicating which node is currently executing, sampling progress percentages, and completion notifications. This makes it straightforward to build custom frontends or monitoring dashboards.

### Headless and Serverless Deployment

Because the backend does not require a browser or GUI to function, ComfyUI can run in headless mode on remote servers. This has led to widespread adoption for production workloads:

- **RunPod Serverless**: pre-built Docker images allow ComfyUI to run as a serverless endpoint, scaling to zero when idle and spinning up on demand[14]
- **Custom servers**: developers deploy ComfyUI on cloud VMs (AWS, GCP, Azure) behind load balancers to serve generation requests at scale
- **CI/CD pipelines**: some teams integrate ComfyUI into automated content generation workflows, triggering image or video generation from scripts or webhooks
- **ComfyDeploy**: a dedicated platform (Y Combinator-backed) that packages ComfyUI workflows as team-accessible APIs

The API-first design means any workflow that works in the visual editor can be executed programmatically with no modifications, bridging the gap between prototyping and production deployment.

## ComfyUI Desktop

On October 21, 2024, Comfy Org released ComfyUI V1, which introduced a standalone desktop application alongside the existing browser-based interface.[4] Built with [Electron](/wiki/electron), the desktop app wraps the ComfyUI web application while adding native operating system integration.[16]

### Installation and Setup

The desktop application provides a one-click installation experience. On first launch, the app uses the `uv` package manager to install the required Python environment, downloads the stable ComfyUI backend and frontend, and adds ComfyUI-Manager for custom node management.[4] The installer bundle is approximately 200 MB. The application is code-signed, so it installs without triggering security warnings on Windows or macOS.[4]

### Supported Platforms

| Platform | GPU Support | Status |
|---|---|---|
| Windows | NVIDIA (CUDA) | Stable |
| macOS | Apple Silicon (MPS) | Stable |
| Linux | NVIDIA (CUDA) | Supported |
| Windows (AMD) | Vulkan backend | Planned |

### Desktop-Specific Features

The desktop application includes several features not available in the browser-based version:

| Feature | Description |
|---|---|
| One-click installation | No manual Python or dependency setup required |
| Tabbed interface | Open and switch between multiple workflows simultaneously |
| Custom key bindings | Keyboard shortcuts without conflicts from browser-level hotkeys |
| Model library panel | Visual browser for all locally installed models with drag-and-drop checkpoint loading |
| Workflow browser | Save, organize, and quickly load favorite workflows |
| Automatic model downloading | Workflows embed model URLs or registry IDs; missing models are prompted for download |
| Integrated log viewer | Server logs accessible directly within the application for debugging |
| Automatic updates | Background updates keep the app on the stable release track |
| Top menu bar | Consolidated actions menu; extension developers can attach custom menu items |

### Relationship to Browser Version

The desktop application and the traditional browser-based ComfyUI share the same backend and frontend codebase. Users who prefer running ComfyUI through a web browser can continue to do so. The desktop version provides a more integrated experience with native file system access, better performance isolation, and operating system features like system tray icons and native window management.

## Comfy Cloud

Comfy Cloud is Comfy Org's official hosted, browser-based version of ComfyUI, designed for users who lack powerful local hardware. It runs the full ComfyUI experience in the browser with no local installation, and according to the company roughly 90% of local-workflow custom nodes are available in the cloud without manual configuration. Comfy Cloud entered public beta in November 2025 and graduated from beta in March 2026.[23]

In early 2026, Comfy Cloud moved its compute to [NVIDIA](/wiki/nvidia) Blackwell-generation RTX PRO 6000 GPUs, which the company describes as roughly twice as fast as A100s and which provide 96 GB of VRAM and 180 GB of system RAM per instance, enabling heavier workloads such as high-resolution video upscaling.[23][24] Pricing shifted toward a credit-based model with multiple tiers, and the company reported a 30% GPU price reduction in January 2026.[24] Comfy Cloud complements third-party managed hosts such as RunComfy, ThinkDiffusion, and serverless providers like RunPod and Salad, but is maintained directly by the project team so that new core features and model support arrive in the cloud alongside the local release.[14]

## Hardware Requirements

ComfyUI runs on a variety of hardware configurations. The following table outlines the recommended specifications.

| Component | Minimum | Recommended |
|---|---|---|
| GPU (NVIDIA) | GTX 1060 6 GB or equivalent | RTX 3060 12 GB or higher; RTX 4070/4090 for heavy workflows |
| GPU (AMD) | RDNA 2 or newer with ROCm support (Linux) | RDNA 3 or newer |
| GPU (Apple Silicon) | M1 with 16 GB unified memory | M2 Pro/Max or newer with 32 GB+ unified memory |
| VRAM | 4-6 GB (limited model support) | 8 GB minimum; 12-24 GB for comfortable SDXL and FLUX use |
| System RAM | 8 GB | 16 GB or more |
| Storage | 50 GB for base installation and a few models | 500 GB to 2 TB for model libraries |
| Python | 3.12 | 3.13 (recommended by official documentation) |
| PyTorch | 2.4+ | Latest stable release |
| Operating System | Windows 10, Linux (Ubuntu 20.04+), macOS 12.3+ | Windows 11, latest Ubuntu LTS, macOS 14+ |

For video generation workflows, hardware requirements increase substantially. Models like Wan 2.1 (14B parameters) benefit from GPUs with 24 GB or more VRAM, and generating longer video clips can require 48 GB or more.[18] Users without such hardware can run these workflows through Comfy Cloud's RTX PRO 6000 instances, which expose 96 GB of VRAM per session.[23]

## Version History and Milestones

| Date | Event |
|---|---|
| October 2022 | comfyanonymous discovers Stable Diffusion and begins experimenting with AUTOMATIC1111 |
| January 1, 2023 | Development of ComfyUI begins |
| January 16, 2023 | First public release on GitHub |
| Throughout 2023 | Rapid growth; support for SD 1.5, SD 2.x, and SDXL added; custom node ecosystem begins forming |
| June 3, 2024 | comfyanonymous leaves Stability AI |
| June 21, 2024 | Comfy Org officially formed with comfyanonymous, Yoland Yan, mcmonkey4eva, Dr. Lt. Data, pythongosssss, and Robin |
| July 2024 | NVIDIA announces ComfyUI integration within RTX Remix at Computex 2024; TensorRT acceleration support |
| August 2024 | FLUX model support added on day one of release; frontend rewritten in TypeScript/Vue.js and moved to separate repository; Comfy Org joins the Open Model Initiative |
| October 21, 2024 | ComfyUI V1 desktop application released for Windows, macOS, and Linux |
| November 2024 | SD 3.5 ControlNet models (Blur, Canny, Depth) released by Stability AI with ComfyUI support |
| February 2025 | Native support added for Wan 2.1 video generation models |
| September 16, 2025 | Comfy Org raises $17 million in funding |
| November 2025 | Comfy Cloud enters public beta |
| March 2026 | Comfy Cloud graduates from beta; runs on NVIDIA Blackwell RTX PRO 6000 GPUs |
| April 24, 2026 | Comfy Org raises $30 million at a $500 million valuation; surpasses 4 million users |
| Early 2026 | ComfyUI surpasses 106,000 GitHub stars; supports Wan 2.2, LTX 2.3 with audio, and continues weekly release cycle |

## Community and Ecosystem

ComfyUI has built one of the largest communities in the open-source AI tools space.

### How many people use ComfyUI?

By April 2026, Comfy Org reported that ComfyUI had passed 4 million users, alongside one of the largest open-source AI tooling communities by GitHub, Reddit, and Discord presence.[21][22] The table below summarizes the project's reach.

| Platform | Approximate Size (as of early 2026) |
|---|---|
| Total users (Comfy Org reported) | 4,000,000+ |
| GitHub stars | 106,000+ |
| GitHub forks | 12,300+ |
| Reddit (r/comfyui) | 148,000+ members |
| Discord (Comfy Org) | 53,000+ members |

### Industry Adoption

In July 2024, [NVIDIA](/wiki/nvidia) announced support for ComfyUI within its RTX Remix modding software, integrating AI-powered texture generation into the game modding workflow. Studios and content creators have adopted ComfyUI for tasks including concept art generation, texture creation, video post-production, and rapid prototyping of visual assets.

Cloud hosting services like ThinkDiffusion and RunComfy offer managed ComfyUI instances for users who lack powerful local hardware, and Comfy Org's own Comfy Cloud provides a first-party hosted option. Deployment platforms like RunPod and Salad provide serverless ComfyUI execution for production workloads.[14] ComfyDeploy offers tools for packaging ComfyUI workflows as APIs for team use.

### Educational Resources

The ComfyUI ecosystem includes extensive educational content. The official documentation at docs.comfy.org covers installation, core concepts, and node references.[8] Community-created resources include hundreds of video tutorials on YouTube, written guides on platforms like Stable Diffusion Art and Aituts, and interactive workflow examples hosted on OpenArt. The ComfyUI Examples repository maintained by comfyanonymous provides reference workflows demonstrating common use cases.[1]

## Use Cases

ComfyUI serves a wide range of users and applications:

- **Digital artists and illustrators** use it for [AI art](/wiki/ai_art) generation, style transfer, and creative exploration with fine-grained control over every generation parameter
- **Game developers** leverage NVIDIA RTX Remix integration and texture generation workflows for asset creation and game remastering
- **Animation and VFX studios** build complex pipelines combining image generation, video models, and post-processing for production work
- **Photographers** use ControlNet and inpainting workflows for photo editing, background replacement, and image enhancement
- **Researchers** value the transparent pipeline for experimenting with new sampling methods, model architectures, and conditioning techniques
- **Developers** integrate ComfyUI as a backend service through its API for building AI-powered applications and automated content generation systems

## Is ComfyUI open source?

Yes. ComfyUI is released under the GNU General Public License v3.0 ([GPLv3](/wiki/gpl)), and its source code is publicly available on GitHub.[1] The GPLv3 license permits free use, modification, and redistribution, provided derivative works are also released under GPLv3. Comfy Org has repeatedly emphasized its commitment to keeping the core open, describing its goal as building "the OS of creative AI" and stating that "open source lasts forever."[9] Commercial offerings such as the hosted Comfy Cloud are layered on top of the open-source core rather than replacing it, and the local application remains free to download and run.

## Limitations and Considerations

While ComfyUI offers exceptional flexibility, there are some practical considerations for potential users:

- **Learning curve**: the node-based interface requires understanding how diffusion model pipelines work internally, which can be overwhelming for beginners who simply want to type a prompt and generate an image
- **Debugging complexity**: when a workflow with dozens of nodes produces unexpected results, identifying which node is responsible can require systematic troubleshooting
- **Custom node compatibility**: because custom nodes are developed independently by community members, updates to the core application can sometimes break third-party nodes until their authors release compatibility patches
- **Documentation gaps**: while official documentation has improved, some advanced features and custom nodes rely on community-written guides of varying quality
- **Security risks**: installing custom nodes from unverified sources executes arbitrary Python code on the user's machine; the Registry and Manager verification systems mitigate but do not eliminate this risk

## See Also

- [Stable Diffusion](/wiki/stable_diffusion)
- [AUTOMATIC1111](/wiki/automatic1111)
- [FLUX](/wiki/flux)
- [ControlNet](/wiki/controlnet)
- [Diffusion Models](/wiki/diffusion_models)
- [LoRA](/wiki/lora)
- [AI Art](/wiki/ai_art)
- [Generative AI](/wiki/generative_ai)
- [Gradio](/wiki/gradio)

## References

1. ComfyUI GitHub Repository. Comfy-Org/ComfyUI. https://github.com/comfyanonymous/ComfyUI
2. "AI Engineering for Art - with comfyanonymous, of ComfyUI." Latent Space Podcast. https://www.latent.space/p/comfyui
3. "ComfyUI." Wikipedia. https://en.wikipedia.org/wiki/comfyui
4. Robin. "ComfyUI V1 Release." ComfyUI Blog. October 21, 2024. https://blog.comfy.org/p/comfyui-v1-release
5. Robin. "Comfy Raises $17M Funding." ComfyUI Blog. September 16, 2025. https://blog.comfy.org/p/comfy-raises-17m-funding
6. Robin. "Launching ComfyUI Registry." ComfyUI Blog. https://blog.comfy.org/p/launching-comfyui-registry
7. Yoland Yan. "Forming Comfy Org." X (formerly Twitter). June 3, 2024. https://x.com/yoland_yan/status/1803104946679849253
8. ComfyUI Official Documentation. Comfy Org. https://docs.comfy.org/
9. About Comfy Org. https://www.comfy.org/about
10. Dr. Lt. Data. "ComfyUI-Manager." GitHub. https://github.com/Comfy-Org/ComfyUI-Manager
11. Comfy Node Registry. Comfy Org. https://registry.comfy.org/
12. "Automatic1111 vs ComfyUI: What's the Differences." GPU-Mart. https://www.gpu-mart.com/blog/automatic1111-vs-comfyui
13. "ComfyUI vs Automatic1111 (2025) - The Honest Comparison." Apatero Blog. https://apatero.com/blog/comfyui-vs-automatic1111-which-should-you-use-2025
14. "Deploy ComfyUI as a Serverless API Endpoint." RunPod Blog. https://www.runpod.io/blog/deploy-comfyui-as-a-serverless-api-endpoint
15. "Stability AI Releases Stable Diffusion 3.5 Large ControlNet Models." ComfyUI Wiki. November 2024. https://comfyui-wiki.com/en/news/2024-11-26-sd3-5-large-controlnets
16. ComfyUI Desktop Repository. Comfy-Org/desktop. GitHub. https://github.com/Comfy-Org/desktop
17. ComfyUI Changelog. Official Documentation. https://docs.comfy.org/changelog
18. "Wan2.1 ComfyUI Workflow - Complete Guide." ComfyUI Wiki. https://comfyui-wiki.com/en/tutorial/advanced/video/wan2.1/wan2-1-video-model
19. "LTX-2.3 Day-0 support in ComfyUI." ComfyUI Blog. https://blog.comfy.org/p/ltx-23-day-0-supporte-in-comfyui
20. "Comfyui Statistics: Data Reports 2026." WifiTalents. https://wifitalents.com/comfyui-statistics/
21. "ComfyUI raises $30M to scale open-source AI for creative production." ComfyUI Blog. April 24, 2026. https://blog.comfy.org/p/comfyui-raises-30m-to-scale-open
22. "ComfyUI hits $500M valuation as creators seek more control over AI-generated media." TechCrunch. April 24, 2026. https://techcrunch.com/2026/04/24/comfyui-hits-500m-valuation-as-creators-seek-more-control-over-ai-generated-media/
23. "Comfy Cloud Is Out of Beta and It's Just Getting Started." ComfyUI Blog. March 2026. https://blog.comfy.org/p/comfy-cloud-is-out-of-beta-and-its
24. "Comfy Cloud: new features and pricing changes." ComfyUI Blog. https://blog.comfy.org/p/comfy-cloud-new-features-and-pricing