Comfy UI Manager

Workflow Manager Documentation | ComfyUIManager.com

ComfyUI Manager allows you to manage your workflow collection. Organize, preview, tag, and manage your JSON workflows precisely and easily.

What Are Workflows in ComfyUI?

Workflows in ComfyUI are saved node graph configurations (.json files) that specify how picture generation is handled, such as model loading, prompts, conditioning, samplers, and post-processing.

These files can be saved, shared, or imported into other ComfyUI setups.

How ComfyUI Manager Enhances Workflow Handling

While ComfyUI supports loading and saving workflows, ComfyUI Manager adds several enhancements:

  • Clean display of available workflows
  • Preview thumbnails (where supported)
  • Rename, tag, or duplicate workflows
  • Auto-backup before overwrites
  • Store workflows in folders or categories
  • Visual search and filter (coming soon)

Workflow File Location

By default, ComfyUI stores workflows here:

  • Windows: ComfyUI/workflows
  • Linux/macOS: ~/ComfyUI/workflows

If you store templates elsewhere (for example, on cloud storage or backups), you can create custom folders within ComfyUI Manager as well.

Best Practices for Workflow Management

  • Use clear, descriptive file names (e.g. txt2img-anime-portrait-v1.json)
  • Store in subfolders by style, task, or model
  • Add tags in file metadata (if supported)
  • Backup workflows before major UI or node changes
  • Preview JSON before importing from unknown sources

Sharing Workflows with Others

ComfyUI workflows are fully portable. To share:

  1. Locate your saved JSON in /workflows
  2. Zip the file or folder
  3. Share via GitHub, Drive, or forums (e.g. Civitai, Reddit)
  4. When importing, ensure the necessary nodes and models are installed.

Note: If a workflow contains any missing nodes, ComfyUI will display them as red blocks with an error. Install the appropriate custom nodes using Manager.

Troubleshooting Workflow Issues

  • Missing nodes:
    • Open Manager and install missing node packs listed in the error
    • Refresh and reload the workflow
  • Workflow not executing:
    • Ensure model paths haven’t changed
    • Verify VAE, LoRA, or ControlNet inputs are mapped correctly