配置文件丨导出

You know that feeling when a ComfyUI update quietly breaks three custom nodes and you have no idea what you had installed last week? ConfigExport is the insurance policy for that moment. It gathers your node list, your frontend settings, your Python dependency snapshot, and optionally your workflows and input/output files, then packs them into one timestamped ZIP you can keep or move to another machine. Think of it as "export my entire ComfyUI environment to a file" - a first-aid kit against dependency hell, which the KB's ecosystem essay calls the most common operational complaint in ComfyUI.

It's part of ComfyUI-QING's configuration-management category (display name 配置文件丨导出), and it pairs with ConfigImport in the same pack to round-trip a setup: export here, import over there. This node is an OUTPUT_NODE - it doesn't feed the graph so much as perform an action and report back.

How it works. It locates your ComfyUI root, then toggles what gets collected based on six boolean inputs. The defaults are the sensible ones: export_node_info (the custom_nodes list and their configs) and export_frontend_settings (UI config and preferences) and export_dependencies (a requirements snapshot plus the installed-package list) are on. export_workflows, export_inputs, and export_outputs are off by default - because your input/ and output/ folders can be gigabytes, and you rarely want them in a config backup. Everything lands in a comfyui_config_<timestamp>.zip inside output/config_backups/ by default, or wherever you point output_path (which must be an absolute path).

The result is a single result_analysis STRING output - a summary of what was exported, how many files, total size, and any errors - which shows in the UI as the node's text.

The inputs that matter.

• export_node_info / export_frontend_settings / export_dependencies - leave these on for a true environment snapshot.
• export_workflows - turn on if you want the migration to carry your graph library.
• export_inputs / export_outputs - on only when you actually want the big folders (e.g. moving a whole installation).
• output_path - optional; leave empty for the default backups folder.

How to install. ComfyUI-QING installs as one pack - search "ComfyUI-QING" in ComfyUI Manager, or:

cd ComfyUI/custom_nodes
git clone https://github.com/GAO-SHIQING/ComfyUI-QING
cd ComfyUI-QING
python install_dependencies.py

Restart afterward. The README's clone URL is typo'd (GAOSHI-QING, missing the H) - use the URL above or Manager.

Troubleshooting. The number one surprise is that workflows/inputs/outputs aren't exported by default - you flip them on explicitly. Second: output_path must be absolute or the node errors out on purpose. Third: this snapshots the environment, not the model weights - checkpoint/VAE/LoRA files in models/ are not part of the export, so a full restore still needs your model library. And if you're backing up before an upgrade, actually do it before - the whole point is having the snapshot on disk when the update lands. This is a config tool, not a migration for the model files that make up most of a ComfyUI install's disk footprint.