Reference only

IPAdapter model not found: unified presets and manual loaders use different rules

A downloaded IPAdapter file can exist on disk without satisfying a unified loader's preset matching. Identify the loader before renaming or relocating files.

Symptoms and scope

A downloaded IPAdapter file can exist on disk without satisfying a unified loader's preset matching. Identify the loader before renaming or relocating files.

Error fragments for search; IDs, values and filenames may vary:

IPAdapter model not found
IPAdapterUnifiedLoader

Source-supported context

The IPAdapter Plus README distinguishes precise naming for unified loaders from manual selection, and separates IPAdapter weights, CLIP Vision and FaceID LoRAs into different resource categories. Source 1 Source 2

Cases to distinguish

1. A preset expects a specific artifact/name but the download retains a generic model.safetensors filename.

2. Adapter, vision encoder and FaceID LoRA files are mixed, or custom paths lack the relevant category.

3. The chosen variant targets another base model or vision encoder and does not fit the selected preset.

Diagnostic sequence

The sequence below is an editorial procedure based on the cited context, not a diagnosis already confirmed for your environment.

Step 1. Record node class, preset, base family and the exact missing-resource message. Distinguish IPAdapter from CLIP Vision.

Step 2. Check artifact identity and naming against the preset's README instructions. Rename only a verified matching file; do not disguise another model.

Step 3. Inspect models/ipadapter or its extra_model_paths equivalent, then check the independent clip_vision and loras locations.

Step 4. Refresh scanning and test one reference image. A manual loader requires you to preserve all component relationships, not merely choose nonempty dropdown values.

Completion check

The preset selects the intended artifact and completes image encoding and sampling, not just the first discovery check.

Limitations and cautions

The author marks the repository as maintenance-only. Preserve version conditions for new-core compatibility issues rather than promising active ongoing support.

Original sources

Localization prepared: 2026-09-22. The source-check dates above were inherited from the existing article; this translation does not claim they were all rechecked today. No GPU run, minimum-memory measurement or runtime guarantee is supplied.

Didn't solve it?

Check the next possible cause

The same symptom can come from a different cause. Work through these related entries in order.

  1. CLIP Vision missing or incompatible: it is not the prompt's text encoderCLIP Vision model not foundReference-image workflows need a vision encoder with the expected architecture. Distinguish it from the object feeding CLIPTextEncode.
  2. InsightFace installation or initialization fails: separate packages from FaceID assetsNo module named 'insightface'Missing insightface, failed wheel builds and initialization errors require different checks: interpreter, native build, execution backend and model files.
Paste your full log into the error finder

Was this page helpful?

Anonymous. Only a yes/no counter is stored; no account, IP address or device details.

Sources & references

Localized from the existing Chinese research draft. Original source-check dates are retained; this translation is not new technical verification or a runtime test.

01ComfyUI IPAdapter Plus READMESource checked: 2026-09-2102Install custom nodesSource checked: 2026-09-21

Report an issue · aea57e1a-9e1b-5692-a8d8-0e68b6dd8119