Sign In

Wildcard Saver

Updated: Feb 4, 2026

tool

Type

Other

Stats

20

0

Reviews

Published

Feb 4, 2026

Base Model

ZImageTurbo

Hash

AutoV2
8FA855BE6F

Wildcard Saver: Quick Start

The Wildcard Saver node is a utility for ComfyUI designed to capture and store text strings—such as prompts, subjects, or styles—directly into .txt files. This is perfect for building your own custom wildcard libraries on the fly without leaving the ComfyUI interface.

1. Key Features

  • Dynamic Saving: Convert any text input (or generated prompt) into a reusable wildcard file.

  • Three Save Modes: Choose between saving to your standard wildcards folder, the output directory, or a temp folder.

  • Smart Overwrite Protection: If "append" is turned off, the node automatically renames files (e.g., colors_1.txt) to prevent accidental data loss.

  • Live Console Debugging: Provides a clear visual log in your terminal showing how many lines were added and the exact file path used.


2. Setup

  • File: Save WildcardSaver.py in your ComfyUI/custom_nodes/ directory.

  • Installation: Restart ComfyUI. The node will appear under the category CustomNodes/IO.


3. Settings Explained

  • text: The string you want to save. Each new line in the text will be treated as a separate entry in the wildcard file.

  • filename: The name of your file (do not include .txt).

  • append: * True: Adds the new text to the end of the existing file.

    • False: Creates a new file. If the name exists, it adds a numbered suffix.

  • save_mode:

    • wildcards: Saves to ComfyUI/wildcards/ (Created automatically if missing).

    • output: Saves to your standard ComfyUI output folder.

    • temp: Saves to the temporary folder.

  • debug: Set to True to see color-coded success and error messages in your terminal.


4. Reading the Debug Logs (Console)

When debug is enabled, you will see a blue (magenta-ish) log entry in your terminal:

  • Before: How many valid lines were in the file before saving.

  • After: The total count of lines now in the file.

  • Path: The exact disk location where the file was saved.


Why use this?

  • Prompt Harvesting: If you generate a great prompt using LLMs or randomizers, you can save it instantly to your permanent library.

  • Automation: Create "dataset" files for training or long-term projects by appending successful prompt combinations to a list while you work.


Note: 'VibeCoded'