Models & Files

Value not in list (model not found)

Value not in list: ckpt_name: '…' not in […]

A loader references a checkpoint, LoRA, or VAE filename that ComfyUI cannot find in your models folders, so the value is no longer a valid dropdown option.

What it means

A loader node stored the name of a model file, but that exact filename is not present in the corresponding models folder — so it is "not in list" of available options. ComfyUI can only select models it can see on disk.

This is common when you open a workflow made elsewhere: it references models you do not have, or a file whose name changed. The graph is fine; the referenced asset is the problem.

Common causes

  • The referenced checkpoint/LoRA/VAE is not in the models folder.
  • The file was renamed or moved after the workflow was saved.
  • The model lives in the wrong subfolder (e.g. a LoRA under checkpoints).
  • The model list was not refreshed after adding the file.

How to fix it

  1. 1

    Place the file in the correct models subfolder

    Put checkpoints, LoRAs, and VAEs in their matching folders under ComfyUI/models so the right loader can see them.

  2. 2

    Refresh the model list

    Press R or reload the browser (or restart the server) so ComfyUI re-scans the models folders and repopulates the dropdowns.

  3. 3

    Re-select the model in the loader

    Open the loader’s dropdown and pick the model again — the stored name may differ slightly from the file you have.

  4. 4

    Download the referenced model if you don’t have it

    If the workflow needs a specific model you are missing, obtain that exact model and place it in the correct folder before running.

When the specific model files behind a result are tracked with the workflow, "value not in list" stops being a guessing game — you know exactly which asset the graph expects.

Frequently asked questions

Frequently Asked Questions

Quick answers to the most common questions.

Related nodes

Related errors

Make every ComfyUI run reproducible

Numonic captures the full workflow behind each ComfyUI generation — models, samplers, seeds, prompts, and custom nodes — so a setup that finally works is one you can find and rebuild, not re-debug.