comfyui-subgraph-blueprints
Pre-built subgraph blueprints for ComfyUI.
Subgraph Blueprints are reusable workflow components that appear as single nodes in ComfyUI. They abstract complex node configurations into user-friendly creative primitives like "Text to Image" or "Image Edit".
Installation
pip install comfyui-subgraph-blueprints
Blueprint Format
Blueprints use the native ComfyUI subgraph format with definitions.subgraphs:
{
"id": "workflow-uuid",
"nodes": [{"id": -1, "type": "subgraph-uuid", ...}],
"definitions": {
"subgraphs": [{
"id": "subgraph-uuid",
"name": "Text to Image (Flux.1 Dev)",
"inputs": [{"name": "text", "type": "STRING"}, ...],
"outputs": [{"name": "IMAGE", "type": "IMAGE"}],
"nodes": [...],
"links": [...]
}]
}
}
Usage
from comfyui_workflow_templates_core.loader import (
iter_blueprints,
get_blueprint_entry,
get_blueprint_asset_path,
)
import json
# List all available blueprints
for blueprint in iter_blueprints():
print(f"{blueprint.blueprint_id}")
# Load a specific blueprint
entry = get_blueprint_entry("text_to_image_flux_1_dev")
path = get_blueprint_asset_path("text_to_image_flux_1_dev", "text_to_image_flux_1_dev.json")
with open(path) as f:
data = json.load(f)
subgraph = data["definitions"]["subgraphs"][0]
print(f"Name: {subgraph['name']}")
print(f"Inputs: {[i['name'] for i in subgraph['inputs']]}")
print(f"Outputs: {[o['name'] for o in subgraph['outputs']]}")
Available Blueprints
Categories include:
- Text to Image: Flux, Qwen-Image, Chroma, Omnigen2, etc.
- Image Editing: Flux.2 Klein, Qwen, Chrono
- Text to Video: LTX 2.0, Wan 2.2
- Image to Video: Kandinsky5, Wan 2.2
- ControlNet: Qwen-Image, Z-Image-Turbo
- Inpainting/Outpainting: Flux.1 Fill, OneReward, Qwen-Image
Contributing
See the main repository for contribution guidelines: https://github.com/Comfy-Org/workflow_templates
Metadata
Release files for comfyui-subgraph-blueprints 0.0.13
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| comfyui_subgraph_blueprints-0.0.13.tar.gz | 482.7 kB | Without provenance | Details for comfyui_subgraph_blueprints-0.0.13.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| comfyui_subgraph_blueprints-0.0.13-py3-none-any.whl | Python 3 | none | any | Details for comfyui_subgraph_blueprints-0.0.13-py3-none-any.whl |
Total release size: 1.1 MB
Release files / comfyui_subgraph_blueprints-0.0.13.tar.gz
| Download URL | comfyui_subgraph_blueprints-0.0.13.tar.gz |
|---|---|
| Size | 482.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b1cfa42e9793c0c705b11ae38dc40edc6253b160a2879241bd0bf6ec0fd57a8f
|
|
BLAKE2b-256 checksum How to use checksums |
3d3945b1bae3fd2e80093a6e4e3a202f7317eb35506079601c5d4f7b622f4a24
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Release files / comfyui_subgraph_blueprints-0.0.13-py3-none-any.whl
| Download URL | comfyui_subgraph_blueprints-0.0.13-py3-none-any.whl |
|---|---|
| Size | 613.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e376e8985015f65cdea41a48635f7dcbe4e6efab1ad9138af9b43f01e2b21a99
|
|
BLAKE2b-256 checksum How to use checksums |
ad3a00dc86fc77bf060fa567524adbf345dff7395af1641e4e8ca0152b529e4a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.8
|
Security for comfyui-subgraph-blueprints 0.0.13
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.