How to Fix ComfyUI Cannot Find Model File

If ComfyUI shows an error like "Model not found", "Checkpoint not found", or a node has an empty model dropdown, the model file is not in a location that ComfyUI can see.

This is rarely a corrupted file — it is almost always a path problem. The file exists somewhere on your disk, but ComfyUI is looking in a different folder.

In the 30-day Wonderful Launcher telemetry window ending June 29, 2026, missing models were detected on 27 installs and resolved on 17 installs. That makes missing model placement one of the most useful public docs topics for existing users: once nodes load correctly, the next blocker is often the model asset.

Case-review boundary: model file or something else?

Agent repair cases often reach this page after missing custom nodes are fixed. That is the right handoff only when ComfyUI now recognizes the node but cannot find the model asset the node selected.

Missing model, wrong folder, or wrong ComfyUI install?

Use this split before downloading another multi-GB file:

Do not declare a missing-node repair "fixed" just because red nodes disappear. Queue or validate the workflow once more so the next missing model file becomes visible.

What the errors look like

Error: Checkpoint not found: v1-5-pruned-emaonly.safetensors

FileNotFoundError: Model file not found: models/checkpoints/sdxl_base.safetensors

ValueError: No checkpoint found in models/checkpoints/

Official ComfyUI model troubleshooting also shows validation errors like:

Prompt outputs failed validation:
CheckpointLoaderSimple:
- Value not in list: ckpt_name: 'model-name.safetensors' not in []

Or the model dropdown in a node simply shows no options.

Why it happens

• Wrong folder: The model file is in models/ but needs to be in models/checkpoints/
• Wrong subfolder: The model is a LoRA but was placed in checkpoints/ instead of loras/
• Not downloaded yet: The model file was never downloaded or the download was incomplete
• Custom model path not configured: You have models in a separate drive but extra_model_paths.yaml is not set up
• Filename mismatch: The workflow expects a specific filename that does not match what you downloaded
• Symlinks or shortcuts: Windows shortcuts (.lnk files) are not the same as the actual model file

ComfyUI default model folder structure

ComfyUI/
└── models/
    ├── checkpoints/      ← SD 1.5, SDXL, FLUX checkpoints (.safetensors, .ckpt)
    ├── loras/            ← LoRA files (.safetensors)
    ├── vae/              ← VAE models
    ├── clip/             ← CLIP models
    ├── controlnet/       ← ControlNet models
    ├── upscale_models/   ← Upscaling models (ESRGAN, etc.)
    ├── embeddings/       ← Textual inversion embeddings
    ├── clip_vision/      ← CLIP vision models (for IP-Adapter)
    ├── ipadapter/        ← IP-Adapter models
    ├── unet/             ← Standalone UNet models (FLUX, etc.)
    └── sams/             ← Segment Anything Model checkpoints

Each model type goes in a specific subfolder. ComfyUI will not find a checkpoint if it is in the wrong subfolder.

Step-by-step fix

Step 1: Identify what type of model is missing

The error message or node type tells you which folder to check:

Step 2: Check if the file is there

dir ComfyUI\models\checkpoints\

Replace checkpoints with the relevant subfolder. If the file is not there, download it or move it from wherever it was saved.

Step 3: Check for incomplete downloads

Model files are large. An incomplete download will have a much smaller file size than expected:

If the file is much smaller, delete it and download again.

Step 4: Use extra_model_paths.yaml for external folders

If your models are on a different drive, copy or rename extra_model_paths.yaml.example to extra_model_paths.yaml, then edit the file in the ComfyUI root directory:

my_models:
    base_path: D:/AI/models/
    checkpoints: checkpoints/
    loras: loras/
    vae: vae/
    controlnet: controlnet/

Restart ComfyUI after editing this file. ComfyUI will scan both the default models/ folder and your external folders.

If you launch ComfyUI with a custom config file path, confirm the same process loads that config. Recent ComfyUI builds also expose an --extra-model-paths-config option for loading one or more extra model path files, but most users should start with extra_model_paths.yaml in the ComfyUI folder.

Step 5: Fix filename mismatches

If a workflow expects a model named sd_xl_base_1.0.safetensors but your file is named sdxl_base.safetensors, either:

• Rename your file to match the workflow expectation
• Edit the workflow to select your filename from the dropdown

When not to run pip install blindly

Model-not-found errors are never fixed by installing Python packages. Do not run pip install when the problem is a missing or misplaced file. The fix is always about file placement, not package management.

Verification before you call it fixed

After moving or downloading a model file, verify these four things:

How Wonderful Launcher can help

Wonderful Launcher helps manage model paths. It helps detect where your models are stored, assists with configuring extra_model_paths.yaml, and provides clear feedback when a model file is missing or in the wrong location.

Download Wonderful Launcher — it's free and simplifies model management.

Related errors

• Where ComfyUI Stores Checkpoints
• Model Path Not Detected
• Where to Put Safetensors in ComfyUI
• Install Models in ComfyUI
• Workflow Missing Nodes
• ComfyUI Common Issues

Source References

• ComfyUI GitHub
• Official ComfyUI model troubleshooting
• ComfyUI extra_model_paths.yaml.example