🐯 YFG CivitAI MetaSave V2

Here's the situation this node exists for: you render something in ComfyUI, drag the PNG onto CivitAI, and the page lists the checkpoint and LoRAs under "used resources" as empty, with a prompt it can't decode. It's not you doing something wrong. The stock SaveImage node writes ComfyUI's own workflow JSON into the PNG - great for dragging the image back into ComfyUI, useless to CivitAI, which is built to read the A1111-style parameters text chunk instead. That mismatch has annoyed ComfyUI users for years (there's a whole family of "how do I make CivitAI see my resources?" threads on r/civitai).

YFG CivitAI MetaSave V2 is the fix: a drop-in replacement for SaveImage that embeds the exact A1111-compatible metadata chunk CivitAI parses - model, LoRA and embedding hashes, sampler settings, seed, and both prompts - so your uploads get their resource list and generation info filled in automatically, exactly like A1111 outputs do. It's part of the YFG Comical pack (the "😸 YFG Comical Nodes" collection), and it's the second generation of the pack's MetaSave node: V1 is frozen so old workflows never break, and V2 is where new work happens. Both can sit in the same workflow.

How it works

Under the hood it does a metadata capture pass over the upstream graph: it walks back from the node, picks up the seed, sampler, steps, CFG, dimensions and prompts, and detects LoRAs both from LoraLoader nodes and from inline <lora:name:weight> syntax in the prompt text. Each model file is SHA-256 hashed (first 10 hex chars, which is what CivitAI matches against) and the hashes are cached on disk in civitai_metasave/.cache/model_hash_cache.json, so the first save of a workflow is slow and every run after is not.

The A1111 parameters chunk goes into a PNG text chunk for PNG output; for JPG and WebP it goes into the EXIF UserComment instead, so CivitAI can still read it. The full ComfyUI workflow JSON rides along too (that's the default metadata_scope of full), so you don't lose the "drag the image back into ComfyUI" superpower that made workflow-in-image a community norm in the first place.

The inputs that matter

Most of the defaults are right. The ones you'll actually touch:

• images - the IMAGE output from your VAE decode. That's the only required wiring.
• filename_prefix - defaults to ComfyUI, but this is where V2 earns its keep. It supports tokens like %date:yyyy-MM-dd%, %seed%, %model%, %width%, %height%, prompt truncation via %pprompt:32% / %nprompt:32%, and - the new bit - any extra metadata field you define: %extra:Prompt Index%, or %KEY% for captured fields like %Steps% or %Sampler%.
• metadata_scope - full embeds A1111 parameters + workflow; default behaves like the stock SaveImage; parameters_only / workflow_only / none trim it down.
• extra_key1 / extra_value1 - your first custom metadata pair, e.g. key Prompt Index, value wired from a random-prompt node. Fill one in and another pair appears below it, up to 32. V1 was stuck at four fixed pairs; V2 grows as you use it.
• output_format and quality - png, jpg, or webp (jpg/webp quality is an integer 1–100, ignored for PNG). save_workflow_json optionally writes the workflow as a sidecar .json next to the image.

It also returns two outputs, filename and filepath, which V1 didn't have - handy for piping the saved location into a logger or display node.

Installing it

Same install as any node from this pack:

cd ComfyUI/custom_nodes
git clone https://github.com/gonzalu/ComfyUI_YFG_Comical

…then restart ComfyUI. Or just search "YFG Comical Nodes" in ComfyUI Manager and hit install - easiest path. The node needs piexif for the EXIF embedding; it's declared in the pack's pyproject.toml so Manager pulls it in automatically. If you cloned manually and see an import error mentioning piexif, pip install piexif fixes it.

Where people get burned

• "Steps not found in metadata!" warning, parameters string skipped. This is deliberate, not a bug - CivitAI requires a Steps value, so the node won't write a parameters chunk it can't complete. Some upstream sampler setups don't expose steps; that's the one real gotcha.
• A filename token that doesn't resolve is replaced with nothing and logged to the console, so a typo like %seed% vs %Seed% (both fine, matching is case-insensitive) silently drops out of the name but stays visible in the log.
• An extra pair with a value but no key raises an error rather than quietly losing data. Empty-key pairs are skipped.

It's a save node, not a fun one, but if you post to CivitAI with any regularity it quietly fixes a real annoyance - and the filename tokens alone are worth the install if you've ever hand-renamed batches by seed.