Repository brief

Comfy-Org/ComfyUI

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-29T22:24:06.690Z
3mo ago

Comfy-Org/ComfyUI

ComfyUI is a large, actively maintained Python-based visual AI engine and application for building diffusion pipelines with a graph/nodes interface. It is very widely adopted, with 107,253 stars and 12,377 forks, and it is still receiving frequent commits as of 2026-03-29.

GitHub
Loading tags...
Stars107,253
Forks12,377
Default branchmaster
Last pushed2026-03-29T21:11:31Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

6 of 6 fork briefs
Selected

Choose this fork if your priority is AMD GPU support and you want a ComfyUI distribution already shaped around ZLUDA and advanced workflows. Stay with upstream if you want the broadest, least specialized, most portable ComfyUI baseline.

Choose this fork if Chinese localization and fork-specific onboarding matter more than staying current with upstream ComfyUI. Avoid it if you need the latest model support, bug fixes, or the broadest compatibility with current ComfyUI extensions.

Choose this fork if installability and operational tooling matter more than staying close to upstream ComfyUI. Choose upstream if you want the broadest community support and the least divergence.

Prefer this fork if you specifically want a serverless, browser-first ComfyUI product and can tolerate divergence from upstream. Prefer upstream if you want the latest ComfyUI features, broad model support, and lower upgrade risk.

Choose upstream unless you specifically need this fork’s repository state; it does not appear to add capabilities, and it is already behind upstream by 20 commits.

Prefer this fork only if its custom API-node and runtime changes match your exact workflow and you do not need the full upstream feature set. For general ComfyUI use, upstream is the safer choice because this fork is materially behind and appears to remove several major capabilities.