Quick summary: Most ComfyUI failures come from four places: a broken or outdated custom node, a model file that is missing or from the wrong family, too little GPU memory, or an update that changed the code but not its dependencies. This guide gives you a fixed order to check them in, the exact error messages that point to each cause, and the fixes from ComfyUI's official documentation. If you would rather not maintain a local install at all, the last section compares running it yourself with Comfy Cloud's plans.
What's in this guide
- First, find out what actually failed
- Fix 1: rule out custom nodes (the most common cause)
- Fix 2: "Value not in list" and other model errors
- Fix 3: CUDA out of memory and very slow generations
- Fix 4: things that break right after an update
- Fix 5: startup, GPU and connection problems
- Local ComfyUI vs Comfy Cloud: what each option costs
- Editor's note, FAQ and related guides
First, find out what actually failed
ComfyUI is a node-based app: a workflow is a chain of loaders, encoders, samplers and save nodes, and any one of them can stop the run. When a run fails you normally get a "Prompt execution failed" dialog with a Show report button. Click it before you change anything. The report names the node that failed and the Python error behind it, and that one line usually tells you which of the sections below you need.
Two more places are worth knowing. The terminal or console window that runs ComfyUI prints the full error, including "Failed to import" lines for custom nodes at startup. And if you use Comfy Desktop, the app writes its own app.log, which you can open from Desktop Settings → Logs → Diagnostics → Open logs folder. For the ComfyUI process itself, Desktop shows the output in the instance's Manage panel under the Terminal tab.
A simple habit saves a lot of time: before you debug your own workflow, load one of the built-in template workflows and run it. If the template works, the problem is in your workflow or its models. If the template fails too, the problem is in the installation.
Fix 1: rule out custom nodes first
The ComfyUI team says plainly in its troubleshooting guide that most of the issue reports it receives turn out to be caused by custom nodes, not by ComfyUI itself. So the first test is always the same: start ComfyUI with every custom node switched off and see if the problem disappears.
How to start without custom nodes
- Comfy Desktop: there is an option in the settings menu to start with custom nodes disabled.
- Manual install (Windows, macOS, Linux): from the ComfyUI folder run
python main.py --disable-all-custom-nodes. - Windows Portable: copy
run_nvidia_gpu.bat(orrun_cpu.bat), rename the copy, open it in Notepad, and add--disable-all-custom-nodesto the launch line, so it reads.\python_embeded\python.exe -s ComfyUI\main.py --disable-all-custom-nodes --windows-standalone-build. Double-click the copy to launch.
If the error is gone, a custom node is responsible. If it is still there, skip to the model, memory and update sections below.
Find the guilty node by halving
The official method is a binary search: enable half of your custom nodes, test, and keep halving whichever group contains the problem until one node is left. With 16 nodes that takes about four rounds instead of sixteen.
- Check frontend extensions first. Nodes that add their own interface code cause the most trouble after ComfyUI's frontend changes: blank screens, misaligned UI, missing image previews, or links between nodes that stop working. In ComfyUI's settings, open Extensions and disable all third-party extensions, then restart once. If the problem disappears, re-enable them half at a time. For these you only need to reload the page between tests, not restart the server.
- Then check regular nodes. If the frontend test changed nothing, the cause is more likely a Python dependency: "Failed to import" messages, nodes that still show as missing after installing them, or ComfyUI crashing at launch. A common cause is two node packs that require different versions of the same package, such as one pinning an exact
torchversion while another needs a newer one. - Back up before moving folders. If you halve by hand, copy the whole
custom_nodesfolder somewhere safe first, then move half of the node folders into a temporary folder, restart, and test. - Or let the CLI do it. If you have Comfy CLI installed,
comfy-cli node bisect startruns the same search for you; mark each round withcomfy-cli node bisect goodorbad, and finish withcomfy-cli node bisect reset.
Once you know the node, the options are, in order: update it from ComfyUI Manager, look for a replacement on the ComfyUI Registry, report it on the node's GitHub page with your ComfyUI version and the error, or remove it from custom_nodes.
Fix 2: "Value not in list" and other model errors
Missing model
This is the classic error when you open a workflow someone else shared:
Prompt outputs failed validation: CheckpointLoaderSimple: - Value not in list: ckpt_name: 'model-name.safetensors' not in []
It means the loader node is asking for a file that isn't in the folder it searches. Download the model (ComfyUI Manager can fetch many of them for you) and put it in the right subfolder: checkpoints go in models/checkpoints/, VAEs in models/vae/, LoRAs in models/loras/, ControlNets in models/controlnet/ and embeddings in models/embeddings/. If your models live somewhere else, for example in a folder shared with another app, point ComfyUI to it in extra_model_paths.yaml instead of copying gigabytes around.
Models from different families
Errors like "expected input[1, 16, 128, 128] to have 4 channels, but got 16 channels instead" or "mat1 and mat2 shapes cannot be multiplied" almost always mean you mixed model families. SD1.5 and SDXL work in a 4-channel latent space, while Flux and SD3 use 16 channels, so a Flux checkpoint decoded with an SDXL VAE fails at the VAE decode step. The same rule applies to ControlNets: SD1.5 ControlNets only work with SD1.5 checkpoints and SDXL ControlNets only with SDXL. For Flux, the docs also flag one specific mistake: loading the T5 encoder into both slots of the dual CLIP loader instead of T5 in one slot and clip_l in the other.
"Error while deserializing header"
This usually means the model file is damaged or incomplete. Download it again, make sure the drive has room (single models can take anywhere from about 2 GB to well over 15 GB), and check that ComfyUI has permission to read the folder.
Fix 3: CUDA out of memory and very slow generations
"RuntimeError: CUDA out of memory" means the workflow needs more video memory than your GPU has free. Work through these in order, testing after each one:
- Close other apps that use the GPU, such as games, video editors or a second ComfyUI window.
- Lower the resolution or the batch size.
- Launch with
--lowvram. If that's not enough, try--novram. Use--cpuonly as a last resort, because it is very slow. - Try
--force-fp16or--use-pytorch-cross-attentionto cut memory use further. - If your desktop itself stutters,
--reserve-vram 2keeps about 2 GB free for the operating system.
On Portable you add these flags to the launch line in the .bat file, the same way as the custom node flag above; on a manual install you add them after python main.py. If models take ages to load each time you switch, the docs suggest moving them to an SSD and adjusting caching with options like --cache-lru 10.
Fix 4: things that break right after an update
A frequent pattern: you ran git pull, and now the new templates are missing, the interface looks old, or node help is out of date. The code updated but its dependencies did not. The fix is to run pip install -r requirements.txt inside the same Python environment that runs ComfyUI. A startup log line saying "Falling back to the default frontend" is the giveaway that the frontend package didn't update.
- Portable: use
update\update_comfyui.bat, which updates both code and dependencies. To update only dependencies, run.\python_embeded\python.exe -m pip install -r ComfyUI\requirements.txtfrom the portable folder. - Desktop: update the ComfyUI instance from Manage → Update and pick Stable or Latest on GitHub. The Desktop app itself updates separately. If a new feature you read about is missing, you are probably on Stable, which can lag behind GitHub.
- Before you update Desktop: Comfy Desktop takes a snapshot automatically before and after updates, recording the ComfyUI version, custom nodes and pip packages. If an update goes wrong, restore the previous snapshot from the instance's Snapshots tab. Snapshots don't include model files or outputs.
Desktop users on Windows should know one specific bug: versions 1.0.46 and earlier can get stuck in a loop where the app shows an update screen and then closes on every launch. The fix is to download and run the latest Windows installer from comfy.org/download over the top; your installs, models and settings are kept.
Fix 5: startup, GPU and connection problems
- "Torch not compiled with CUDA enabled" on an NVIDIA card: you have a CPU-only PyTorch. Uninstall torch and reinstall the CUDA build the docs list, then check with
python -c "import torch; print(torch.cuda.is_available())". On an Intel GPU the same message means the XPU backend wasn't found, and the docs warn not to install a CUDA build there. - GPU not detected: update the graphics driver and check that
nvidia-smishows the card. - App won't open on macOS: go to System Settings → Privacy & Security and choose Open Anyway. On Linux, the AppImage needs FUSE 2 (
libfuse2). - "Failed to connect to server": allow ComfyUI through the firewall, temporarily disable a VPN or proxy, or start on another port, since the default 8188 may be taken.
- Wrong Python version: the system requirements page currently recommends Python 3.13, with 3.12 as a fallback when custom node dependencies misbehave.
- Visual glitches in the browser: the docs recommend Chrome 143 or later; older versions have known display and performance issues with ComfyUI.
Local ComfyUI vs Comfy Cloud: what each option costs
If most of your time goes into fixing drivers and dependencies, it's worth knowing the alternative. ComfyUI itself is free and open source. Comfy Cloud is the official hosted version, with models and popular custom nodes pre-installed and billing only for active GPU time.
| Option | Price | Hardware | Limits and key features |
|---|---|---|---|
| Local ComfyUI (Desktop, Portable or manual) | Free | Your own GPU | Any model or custom node, works offline; you handle installs, updates and node conflicts yourself |
| Comfy Cloud, free start | $0 | Cloud GPUs | 5 free runs on real GPUs plus free Comfy Agent credits for new users |
| Comfy Cloud Standard | $20/month, or $16/month billed yearly ($192) | Blackwell RTX 6000 Pro, 96 GB VRAM | 30-minute max per workflow run, 50,400 credits per year, top-ups available |
| Comfy Cloud Creator | $35/month, or $28/month billed yearly ($336) | Same | Everything in Standard plus importing your own models and LoRAs; 88,800 credits per year |
| Comfy Cloud Pro | $100/month, or $80/month billed yearly ($960) | Same | Runs up to 1 hour each, 253,200 credits per year |
Prices are from the Comfy Cloud pricing page as of 2026-10-25 and may change. Credits are spent on GPU runtime and on Partner Nodes such as Nano Banana, and unused top-up credits roll over for up to a year. Idle time spent building a workflow isn't charged.
Editor's note
- Who local ComfyUI is for: people with a recent GPU who want full control over models and custom nodes and don't mind reading a traceback now and then.
- Who it's not for: anyone who needs a result today on a laptop without a dedicated GPU. The free Comfy Cloud runs or a simpler hosted image tool will be less frustrating.
- Biggest gotcha: installing every interesting node pack you find. Each one adds Python dependencies, and conflicts between them are the top source of breakage. Install only what a workflow needs.
- Common error → fix: "Value not in list" → model file missing or in the wrong
models/subfolder. "Expected 4 channels, got 16" → mixed Flux/SD3 and SD1.5/SDXL parts. "CUDA out of memory" → smaller image, then--lowvram. Missing features aftergit pull→pip install -r requirements.txt. - Before you ask for help: note your OS, ComfyUI version (shown on the About page in settings), Python and PyTorch versions, GPU and driver, install type, and the full error text. The official guide asks for exactly this.
FAQ
Why does ComfyUI say a node is missing after I installed it?
Usually its Python dependencies failed to install, so the node pack can't load. Look for a "Failed to import" line in the console at startup, then reinstall the pack's requirements or update it from ComfyUI Manager. If it still won't load, it may conflict with another pack, and the halving method above will find it.
Is there an official ComfyUI Docker image?
No. The ComfyUI team states it doesn't provide one. Community images exist on Docker Hub, but they aren't maintained or supported by Comfy Org. The official routes are Desktop, Portable for Windows, a manual install, or Comfy Cloud.
Do Comfy Cloud credits work in local ComfyUI?
For Partner Nodes, yes. The pricing page says the credits that come with a subscription can be used for Partner Nodes in both Comfy Cloud and local ComfyUI. Running open models on your own GPU doesn't use credits at all.
Related guides on Lightmind24
- Ollama Not Working? Fixes for Common Errors and GPU Issues, for the same driver and VRAM problems with local language models
- How to Use Nano Banana in Gemini, if you want to try that image model without a local setup
- Runway Pricing Explained, another look at how AI credit plans add up
Check custom nodes first, models second, memory third, and most ComfyUI errors stop being mysterious.
Images: Comfy Cloud pricing page screenshot (captured 2026-10-25) and screenshots from ComfyUI's official documentation; see the official screenshots at the end of this post.
Last verified: 2026-10-25
Sources:
ComfyUI Docs: How to troubleshoot and solve ComfyUI issues
ComfyUI Docs: Troubleshooting custom node issues
ComfyUI Docs: Model issues
ComfyUI Docs: How to update ComfyUI
ComfyUI Docs: Comfy Desktop FAQ
ComfyUI Docs: System requirements
ComfyUI Docs: Comfy Cloud
Comfy Cloud pricing
댓글
댓글 쓰기