Free lesson

Verify software, checkpoint and installation sources

Verify software, checkpoint and installation sources — Local image workflows with ComfyUI. Separate three rights decisions; Acquire one exact checkpoint, not an entire collection; Use the package matching the actual hardware. Practical assignment: Lab evidence.

Demo edition. The materials are undergoing editorial review.

Topics covered

  • Separate three rights decisions
  • Acquire one exact checkpoint, not an entire collection
  • Use the package matching the actual hardware

Separate three rights decisions

Create separate evidence rows for ComfyUI code, checkpoint weights and any optional node package. The engine repository carries GPLv3 licensing; the tutorial-linked SD1.5 archive labels the selected checkpoint CreativeML OpenRAIL-M. These are not interchangeable licenses. Read the checkpoint’s associated terms, including use and redistribution conditions, rather than assuming a download button means unrestricted use. The model license also does not license all training data or clear every possible trademark, likeness or output claim. This course avoids those extra issues with an original, unbranded still life and no real person. Do not add a random LoRA or custom node to improve the image before reviewing its own source and license. Keep source URLs, inspected date and artifact names in the ledger. The expected decision is narrowly “documented for this synthetic local exercise,” not blanket commercial clearance.

Save the license evidence as a dated copy or stable reference together with the chosen artifact name. A later repository badge can change, and your handoff should show what was checked for this revision rather than an unrelated current summary.

Acquire one exact checkpoint, not an entire collection

Follow the file link in the official first-generation tutorial to v1-5-pruned-emaonly-fp16.safetensors in the Comfy-Org archive. Record that it is an SD1.5-family checkpoint before choosing loaders or other components. Download only that file, not the full repository with unrelated alternatives. The inspected file page publishes SHA-256 e9476a13728cd75d8279f6ec8bad753a66a1957ca375a1464dc63b37db6e3916; compare your local hash after download. This verifies agreement with that published artifact, not universal trust in every checkpoint or a security guarantee. A small HTML error response with the expected filename is not a model. Safetensors avoids some pickle-loading risks, but provenance and dependencies still matter. Put the verified file in the portable installation’s ComfyUI/models/checkpoints folder and preserve the model card/license evidence outside the binary. Do not execute scripts bundled by an unknown mirror.

PowerShell may display hexadecimal letters in uppercase while the published digest uses lowercase. Compare the same64 hexadecimal digits case-insensitively; do not accept a different digest merely because the filename, size or download progress looked plausible.

# PowerShell read-only check after an optional learner download
Get-FileHash -Algorithm SHA256 ./v1-5-pruned-emaonly-fp16.safetensors
# Compare to the artifact page, then move the verified file to:
# ComfyUI_windows_portable/ComfyUI/models/checkpoints/v1-5-pruned-emaonly-fp16.safetensors

Use the package matching the actual hardware

Download the official Windows Portable package selected in lesson one, extract it into a dedicated practice directory and read README_VERY_IMPORTANT.txt. Use the documented launcher for that package: the NVIDIA package uses run_nvidia_gpu.bat, while its CPU-only launcher is documented under advanced/run_cpu.bat. Other GPU vendors have their own packages; an NVIDIA launcher is not a universal accelerator switch. Keep the terminal visible and open the local URL it reports manually if necessary. No Python command is executed on the Mac during this course authoring, and no browser is automated here. Do not install custom nodes or enable paid partner nodes. If startup fails before the interface opens, inspect runtime/driver compatibility and the actual error rather than changing prompts or downloading more checkpoints. Success at this step is a local interface and saved version/log information, without running generation.

If operating-system security blocks a downloaded package, verify the official source and documented installation method. Do not disable every security control or exclude an entire personal drive merely to bypass a warning from an unverified download.

Practical assignment

Lab evidence

Continue to learning

Course outline

  1. Define a modest local image experiment
  2. Verify software, checkpoint and installation sources
  3. Build the complete seven-node graph
  4. Set a bounded run and compare one variable
  5. Diagnose failures and audit without generating
  6. Package evidence, inspect output and preserve recovery