Comfy-Pack: Making ComfyUI Workflows Shareable

comfy-pack is a comprehensive toolkit for reliably packing and unpacking environments for ComfyUI workflows.

Motivations

ComfyUI Manager is great for find missing custom nodes. But when sharing ComfyUI workflows to others(your audience or team members), you’ve still likely heard these responses:

These are fundamental challenges in workflow sharing – every component should match exactly: custom nodes, model files, and Python dependencies. Modern pacakge managers like npm and poetry introduced “lock” feature, which means record the exact version for every requirement. ComfyUI Manager isn’t designed for that.

We learned it from our community and developed comfy-pack to address these problems. With a single click, it captures and locks your entire workflow environment into a .cpack.zip file, including Python packages, custom nodes, model hashes, and required assets.

Users can recreate the exact environment with one command:

comfy-pack unpack workflow.cpack.zip

This means you can focus on your creative work while comfy-pack handles the rest.

Usages

Installation

We recommend you use ComfyUI Manager to install comfy-pack. Simply search for comfy-pack and click Install. Restart the server and refresh your ComfyUI interface to apply changes.

Alternatively, clone the project repository through git.

cd ComfyUI/custom_nodes
git clone https://github.com/bentoml/comfy-pack.git

To install the comfy-pack CLI, run:

pip install comfy-pack

Pack a ComfyUI workflow and its environment

You can package a workflow and the environment required to run the workflow into an artifact that can be unpacked elsewhere.

Unpack the ComfyUI environments

Unpacking a .cpack.zip artifact will restore the ComfyUI environment for the workflow. During unpacking, comfy-pack will perform the following steps.

To unpack:

comfy-pack unpack workflow.cpack.zip

Huggingface gated models can be accessed by setting your HF_TOKEN as an environment variable before unpacking:

export HF_TOKEN=hf_XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXx
comfy-pack unpack workflow.cpack.zip

For example cpack files, check our examples folder.

Deploy a workflow as an API

You can turn a ComfyUI workflow into an API endpoint callable using any clients through HTTP.

curl -X 'POST' \
  'http://127.0.0.1:3000/generate' \
  -H 'accept: application/octet-stream' \
  -H 'Content-Type: application/json' \
  -d '{
  "prompt": "rocks in a bottle",
  "width": 512, 
  "height": 512,
  "seed": 1
}'

import bentoml

with bentoml.SyncHTTPClient("http://127.0.0.1:3000") as client:
        result = client.generate(
            prompt="rocks in a bottle",
            width=512,
            height=512,
            seed=1
        )

# Get the workflow input spec
comfy-pack run workflow.cpack.zip --help

# Run
comfy-pack run workflow.cpack.zip --src-image image.png --video video.mp4

Security Guidelines

A cpack file only contains the metadata of the workflow environment, such as Python package versions, ComfyUI and custom node revisions, and model hashes. It does not contain any sensitive information like API keys, passwords, or user data. However, unpacking a cpack file will install custom nodes and Python dependencies. It is recommended to unpack cpack files from trusted sources.

comfy-pack has a strict mode for unpacking. You can enable it by setting the CPACK_STRICT_MODE environment variable to true. It will sacrifice some flexibility and compatibility for security. For now, comfy-pack will:

More security features are under way.

Roadmap

This project is under active development. Currently we are working on:

Community

comfy-pack is actively maintained by the BentoML team. Feel free to reach out 👉 Join our Slack community!

Contributing

As an open-source project, we welcome contributions of all kinds, such as new features, bug fixes, and documentation. Here are some of the ways to contribute: