A curated list of things people have built with Comfy: apps, products, films, campaigns and workflows, plus the APIs and SDKs to build your own.
Find a file
Deep Mehta 67b706a803 docs: give every section a voice that is not the warning voice
Five of the ten sections opened straight into bullets, so the only
sections that said anything were the ones carrying a caution, and the
list read as a document that distrusts its own contents.

Each of those five now says what it holds. The three group intros that
opened with a warning now open with what is in the group and keep the
pointer as a trailing clause, and the third-party note leads with what
is checked before what is not. Every disclaimer survives word for word:
no certification, no vetting, not an endorsement, not a quality or
safety rating, and Comfy Org not operating the hosting providers.
2026-10-26 18:12:19 -07:00
.github docs: commit to a reply in a week and a 48 hour takedown 2026-10-26 16:31:01 -07:00
.gitignore feat: a curated list of things people have built with Comfy 2026-10-07 17:44:29 -07:00
.lycheeignore ci: stop the link checker failing on deliberate example URLs 2026-10-23 11:26:03 -07:00
CONTRIBUTING.md feat: stop ranking node packs, point at the registry instead 2026-10-26 17:56:23 -07:00
LAUNCH_CHECKLIST.md docs: stop advertising a node pack index the list no longer has 2026-10-26 18:00:22 -07:00
LICENSE feat: a curated list of things people have built with Comfy 2026-10-07 17:44:29 -07:00
README.md docs: give every section a voice that is not the warning voice 2026-10-26 18:12:19 -07:00
SECURITY.md docs: promise nobody anything 2026-10-26 16:37:21 -07:00
SUBMISSION_GUIDELINES.md feat: stop ranking node packs, point at the registry instead 2026-10-26 17:56:23 -07:00

Awesome Comfy Awesome

Things people have built with Comfy: apps and plugins people shipped, films and campaigns that aired, and workflows you can run, plus the APIs and SDKs for building your own.

For artists who want to see what is possible, and for engineers who want to know where to start.

Inside each section, entries sit under From Comfy for what Comfy Org's own team built and From the community for everything else. How to read this list, just below, says what those headings do and do not tell you, and it is worth a minute before you install anything.

Built something with Comfy? Add it. Removals are as welcome as additions.

Contents

How to read this list

Sections group entries by what you are trying to do. Inside most sections, entries sit under one of two headings.

From Comfy means Comfy Org's own team built it. Some of those are maintained products on a release cadence and plenty are a demo, an example app or a weekend build that works, so the heading tells you who wrote a thing rather than who is looking after it, and a question about one belongs on its own issue tracker. From the community means someone else built it, and it is here because it is useful.

Neither heading is a quality rating, a safety rating or a support commitment. Both say who wrote the thing at the other end of the link, and nothing more than that. A partner integration is not a Comfy product either: where a hosted service or a partner model sits behind a Comfy API, the API is Comfy's and the service is the partner's.

Installing third-party projects

Every entry is checked against the bar: it fits a section, its link resolves, and its description matches what the thing actually does. That is the whole check. It is not a safety audit, and Comfy Org does not certify that a listed project is safe, does not control, test or vet its code, models or data, and may review a listing but does not promise to keep reviewing it. Being on this list is not an endorsement.

Custom nodes and apps are executable code, not metadata. They run with the same access as the Comfy process that loads them, which on a local install is your own user account, your files and your network. Trust a pack as much as you would trust any other software you choose to install: read the source, check who publishes it, and accept that you are the one running it.

If an entry is malicious, misleading or harmful, report it. That form is how an entry comes off the list, and no timeframe is promised for it. Removing an entry does nothing to the project itself, which stays wherever its author put it.

Built with Comfy

Products, tools and apps that run Comfy underneath.

From the community

Other people's work: plugins that put Comfy inside the tools you already use, and apps built on top of your own Comfy. All of it is third-party code, so installing third-party projects is worth a minute first.

Tools that put Comfy inside something else:

  • krita-ai-diffusion - Inpainting, outpainting and live painting inside Krita, against a local or remote Comfy server.
  • OpenLayer - A Photoshop panel that generates, inpaints and upscales through your own Comfy server and hands back editable layers. Alpha.
  • StableGen - A Blender addon that textures 3D meshes through a Comfy backend using multi-view projection.
  • ComfyUI-for-Nuke - Builds and runs Comfy graphs inside Foundry Nuke, against your own Comfy server.
  • ComfyUI-TD - Streams images, video, point clouds and audio from Comfy into TouchDesigner in real time.
  • SwarmUI - A forms-first front end over the same engine, with a Comfy workflow tab when you want the graph back.

Apps on top of your own Comfy:

  • ComfyTV - Turns Comfy into a canvas app where each stage is its own node, across image, video, audio and 3D.
  • Velorn - An open-source desktop video workstation that runs any Comfy workflow on a timeline, locally or in the cloud. (source)
  • ComfyLink - An iOS and Android remote for your own Comfy machine, paired through a node you install in Comfy. (the node)
  • ComfyUI Metadata Viewer - Drop a Comfy output file in the browser and read back the models, parameters and prompt embedded in it.

From Comfy

Apps you can open right now:

  • Emojinius - Upload a character and get back a pack of animated Slack emojis. Needs your own Comfy API key; generation is billed to your account.
  • Cinematic Studio - Direct a shot with a real camera, light and grade it, then run it on any image model.
  • Openjutsu - Swap the main person in a 5 to 15 second clip for the character in one image, keeping the scene, motion and sound. Runs MiniMax H3; needs a Comfy sign-in, and runs are billed in credits.

Clonable app guides, a working app plus a walkthrough of how it is wired:

  • comfy-cinematic-studio - Source and development guide for Cinematic Studio above.

  • comfy-reshoot - A workflow-deployment app, built to be cloned and changed.

  • comfy-openjutsu - Source and development guide for Openjutsu above, run on your own Comfy deployment.

  • comfy-examples - Thirteen smaller apps, each a handful of files behind a deploy button: a Discord image bot, object removal, virtual try-on, sketch to image, profile shots and more.

Work made with Comfy

Films, campaigns, games and public art, all of it the makers' own work and credited to the people and studios named in each line. Most links go to a write-up on Comfy's own site, which is why this section needs no affiliation heading.

Galleries and roundups:

Film and television:

Advertising and campaigns:

Games:

  • ComfyCrawler - A dungeon crawler in a Windows 95 interface, with its art and music generated in Comfy. The hosted build is a read-only edition.

Studios and 3D:

Public art and installations:

  • Moment Factory - Rebuilt a 3D projection mapping pipeline for architectural-scale work. (case study)
  • Ina Conradi's NTU students - Ninety-second films for building-sized LED walls, shown at Hangzhou's West Lake media facade.
  • Echoes of Time - A projection piece on Niš Fortress, produced through a Comfy community challenge.

Studios on their own pipelines, recorded talks:

Teaching:

Events:

Workflows

Graphs you can open and run, and the format they are saved in.

From Comfy

Build your own

The API surfaces, SDKs and hosted endpoints for driving Comfy from your own code.

From Comfy

Comfy Router, one API in front of many hosted image, video and audio models:

Developer Platform, for running your own workflows as a service:

SDKs, which cover the same ground in the same shape:

  • Python SDK - Client for self-hosted Comfy and Comfy Cloud.
  • TypeScript SDK - Node client for the Comfy API v2, against Comfy Cloud, serverless or a self-hosted proxy.
  • Swift SDK - Thin client: submit, stream, collect outputs.

Comfy MCP:

  • Comfy MCP - The hosted endpoint and what it can do.
  • comfy-mcp - Exposes a local Comfy over the Model Context Protocol.
  • MCP documentation - Setup and the tools the server exposes.

Talking to a Comfy server directly:

From the community

Other people's libraries for driving Comfy from code. The third-party note above applies to these too.

Writing workflows as code:

Node packs

Custom nodes are how Comfy grows, and there are thousands of them. The registry ranks them live by install count, with search, versions and scanning, which is a better place to browse than a frozen top twenty here. Packs are third-party code that runs inside your Comfy process, so the note above applies.

Find and install them with:

Writing your own nodes

Everything you need to write a node of your own, from an empty folder to a published pack.

From Comfy

Hosting

Running Comfy on someone else's GPU, by renting one or deploying an image.

From Comfy

From the community

Independent providers and container images, each run by the people who built it. Comfy Org does not operate them, hold your data or set their prices, and the third-party note above applies.

  • ComfyUI-Docker - Container images across several CUDA and Python combinations.
  • SaladCloud - Deploy image and video generation with ComfyUI on their container engine.
  • comfyui-api - A stateless API server in front of Comfy that returns images or sends them to webhooks and S3, built for horizontal scaling.

Getting started

Pick an install path, run your first workflow, and know where to look when something breaks.

From Comfy

  • ComfyUI - The node-graph engine itself: a workflow runner for diffusion models with a Python backend.
  • Download page - Picks the right install path for your machine. Check the system requirements first.
  • Desktop app - Packaged installer for Windows, macOS and Linux. The shortest path to a working setup.
  • Comfy Desktop source - The official desktop app: installs and manages multiple Comfy setups side by side.
  • Manual install - Clone and pip, for when you want to control the Python environment. Windows also has a portable build: one folder, no installer, no system Python.
  • Your first generation - Walks a default workflow end to end and explains what each node did. The interface tour covers the canvas, the queue and the model library.
  • Comfy Cloud - Hosted Comfy, for when you do not have the GPU.
  • comfy-cli - Command-line installer and manager for Comfy, models and node packs. Its docs cover launching, snapshots and switching versions.
  • Troubleshooting - Start here when something breaks, before opening an issue.

Learning

Where to read, watch and ask once you are past the first run.

From Comfy

  • Official documentation - The canonical reference for installation, nodes, models and the APIs.
  • llms.txt - The whole documentation index as one plain-text file, which is the fastest way to find a page.
  • Nodes and models - The two concepts everything else is built on.
  • Basic tutorials - Text to image, image to image, inpaint, outpaint, upscale and LoRA, as annotated workflows.
  • Blog - Official release notes, case studies and announcements.
  • Forum - Longer-form questions and answers that outlive a chat message.
  • Discord - Where most day-to-day help happens.
  • YouTube - Official walkthroughs and release videos.
  • Community links - The official list of community spaces.
  • Contributing to ComfyUI - How to get a change into core.

From the community

  • Nerdy Rodent - Regular walkthroughs of new models and workflows.