Remove Image Info Main Fields

Not every saved image should carry its full recipe. You might want to share a file without the negative prompt, without the seed, without the model name - or you might be generating captions and genuinely don't want sampler settings in the output. The fixed fields of image_info - model, refiner, detailer, lora_stack, clip, vae, positive, negative, sampler settings, seed, size - all get serialized into metadata by default. IPT-RemoveImageInfoMainFields is the switchboard that decides which of those fields are stripped before the bundle goes further.

Think of it as the privacy/cleanliness control for the metadata path. The pack's whole value prop is "save the recipe," so it's oddly fitting that it also gives you the fine-grained "except this part." Use it between the image-info plumbing and the saver.

How it works

Every field is a boolean toggle, all defaulting to false (meaning "keep"). Flip model on and image_info.model is removed; flip positive and the prompt goes. Some toggles cover groups: sampler_settings removes sampler, scheduler, steps, and CFG in one switch, and size removes width and height together. seed is its own toggle. The node returns the filtered image_info, so it slots inline: image_info → RemoveImageInfoMainFields → Image Saver.

Inputs and outputs that matter

The toggles: model, refiner, detailer, lora_stack, clip, vae, positive, negative, sampler_settings (sampler/scheduler/steps/cfg), seed, size (width/height).

• image_info (optional input) - the bundle to filter.
• image_info (output) - the scrubbed bundle.

Installing it

cd ComfyUI/custom_nodes
git clone https://github.com/kinorax/comfyui-info-prompt-toolkit.git
cd comfyui-info-prompt-toolkit
pip install -r requirements.txt

Restart, or ComfyUI Manager → "ComfyUI-Info-Prompt-Toolkit". ComfyUI 0.17.0+. No models.

Common issues

The silent-failure trap is toggling something off and then not checking the saved file - the removal is applied to the image_info object, so if a later node rebuilds or merges the bundle, the field can come back. Put the removal as close to the saver as possible. Also, removing fields is irreversible for that run: there's no undo inside the bundle, so keep a parallel un-scrubbed branch if you think you'll want the full recipe later. And remember this only strips the fixed fields - extras is handled by its sibling Remove Image Info Extra Keys, so scrub both if you're sanitizing for real. It's a boring, exact tool, and for anyone sharing output images it's the difference between "recipe attached" and "recipe you decided to attach."