List the model references actually stored in a ComfyUI workflow

Use explicit loader adapters rather than name guesses

The viewer's adapters map known fields from the official base node definitions at ce1e922d8623. Examples include CheckpointLoaderSimple ckpt_name, LoraLoader lora_name and VAELoader vae_name. The mapping uses those defined nodes and fields; it does not infer a model from every custom field containing model, path or checkpoint.

Download model-references.json. It is a self-authored five-node API prompt with fictional resources and a deliberately unknown ProjectDynamicLoader. The file is a static inspection exercise, not a graph to run. URLs and paths in the fixture are displayed only as saved text and are never dereferenced.

• Download the known/dynamic/custom reference exercise — Five nodes, three connections, three resolved literal references and two unresolved entries. All names and paths are fictional.
• Official base-node definitions and fixed reference catalog — Pinned ce1e922d8623: 65 names in nodes.py's base NODE_CLASS_MAPPINGS and explicit known-loader adapters. Core extras, frontend-only nodes, installed custom nodes and later versions are outside this catalog.

Inspect the three stored literal references

1. Step 1

   Load the reference exercise

   Open the direct JSON viewer and choose model-references.json. Expect api-prompt with five nodes and three connections. Scroll to Model and resource references: there are three literal entries.

   Open the model-reference viewer

2. Step 2

   Record category, node ID, field and exact string

   Node 1 CheckpointLoaderSimple resolves ckpt_name to fictional/checkpoint.safetensors. Node 2 LoraLoader resolves lora_name to fictional/portrait-lora.safetensors. Node 3 VAELoader resolves vae_name to fictional/vae.safetensors. Preserve the reference's node and field alongside its value instead of flattening the list into untraceable filenames.

3. Step 3

   Review the unresolved entries

   Expand Unresolved entries. Node 4 VAELoader has a connected vae_name value ["5",0], so no filename is inferred. Node 5 ProjectDynamicLoader has no known adapter, even though it stores a ckpt_name-looking string and a path. Its resource references remain unresolved rather than being guessed from those field names.

Expected resolved and unresolved rows

The supported list can also contain resource-directory or built-in-option values from other explicit adapters. Even a resolved string is not proof of the corresponding file's contents, installed presence, version or availability. The same resource string can appear at multiple nodes; keep those references instead of assuming a single usage.

Export the list with its scope and questions

1. Step 1

   Check the node-type context

   The Node types and compatibility questions section lists CheckpointLoaderSimple once, LoraLoader once, VAELoader twice and ProjectDynamicLoader once. The fixed catalog recognizes the three base type names, while the fictional type is outside its scope. That unknown label does not mean malicious or missing plugin.

2. Step 2

   Copy or download the reference report

   Click Copy reference list or Download reference list. comfyui-references.json includes the recognized shape/status, pinned catalog source, three literal references, two unresolved entries, actual node-type counts and a question for the unknown type. Review its filenames and paths before sharing.

3. Step 3

   Keep runtime questions separate

   Ask the provider which implementation/version supplies an unknown node and how a connected resource value is determined. The site does not scan folders, look up installed models, download weights, install plugins or generate guessed repository URLs. Save the original JSON privately if you need the complete unresolved custom fields.

Repeat on the official SDXL fields

The official SDXL UI workflow and API prompt both resolve two checkpoint literals, at nodes 4 and 12: sd_xl_base_1.0.safetensors and sd_xl_refiner_1.0.safetensors. The UI document additionally has nine Note and four PrimitiveNode entries outside this limited base catalog. Those 13 unresolved entries do not establish 13 missing models or plugins.

A file with no literal references may use connected/custom storage or contain no loaders in the supported set. The viewer says no literal references were resolved; it does not claim that the graph requires no models. A malformed, unrelated or over-limit JSON document is not a complete empty-dependency inventory. Keep warnings and original source context with whatever list you export.

• Official ComfyUI SDXL example PNG, fixed revision — Original example from the upstream repository at f9431bb000ce. Use its raw/original download. The checked 1024 × 1024 PNG has SHA-256 038bf565ca4db12e070db3507bed9a6242f0d5200a392962172a207af32ad941; this site does not mirror it.
• Extract the official fields for the comparison — The stored JSON references models; it does not package their weight files.

Sources and reproducible inputs

• Reproducible literal/dynamic/custom model-reference input — Self-authored saved JSON with no node execution, model download or local installation access.
• Official base-node definitions and fixed reference catalog — Pinned ce1e922d8623: 65 names in nodes.py's base NODE_CLASS_MAPPINGS and explicit known-loader adapters. Core extras, frontend-only nodes, installed custom nodes and later versions are outside this catalog.
• Official ComfyUI SDXL example PNG, fixed revision — Original example from the upstream repository at f9431bb000ce. Use its raw/original download. The checked 1024 × 1024 PNG has SHA-256 038bf565ca4db12e070db3507bed9a6242f0d5200a392962172a207af32ad941; this site does not mirror it.
• Official API prompt example, fixed revision — Reference ce1e922d8623; only its stored prompt_text was read. The seven-node JSON example yields nine connections and one checkpoint reference. Its Python/network code is not run.