To sell ComfyUI workflows, export your original graph, document its nodes and model requirements, and package the files with setup instructions and a license. Test the retail edition in the environment you advertise before offering paid delivery. A workflow file is not the same product as included models, GPU compute or a hosted generation service.
This guide is for creators selling reusable creative graphs. Its original dependency worksheet separates what is included, what must be downloaded and what may cost extra. It is a proposed release process, not a claim that we ran these graphs or verified a particular model's redistribution rights.
Make the result and requirements specific
Describe the input, intended output and configurable controls. A product-photography background workflow has different requirements from a 3D generation graph. Show representative results made with the retail workflow and name any extra editing involved.
Say whether the product assumes local ComfyUI, Desktop or a supported hosted environment. State the version and hardware you tested instead of promising that every installation works. Do not sell a picture as proof that the buyer receives an editable graph.
Export the right artifact
ComfyUI's official Rodin example distributes a JSON workflow and separately supplies input images. Use that distinction in your own package: the graph, its inputs and its dependencies must be accounted for individually.
For a workflow intended for the visual editor, supply the documented editor-compatible export, not an unexplained API-only payload. If you offer another export, explain its intended consumer. Keep an explicit JSON copy so buyers are not dependent on metadata surviving image editing or upload services.
Use this original dependency worksheet
This fictional studio-pack manifest is a planning example, not an executable workflow or a confirmed compatibility result.
| Component | Package decision | Buyer-facing evidence |
|---|---|---|
| Editor workflow JSON | Include original graph | Edition and intended environment |
| Custom nodes | List exact source and version | Install steps and any separate license |
| Model weights | Include only with distribution rights | Source, version and required location |
| Input images | Include only permitted samples | Dimensions and usage rights |
| API service | Buyer supplies account and access | Separate costs and prerequisites |
| Setup guide | Include steps and known limitations | Clean-environment test record |
A download link for a model is not permission to redistribute its weights. Review the actual license and distinguish rights to run the model, redistribute it and use generated outputs. When redistribution is not permitted or practical, document the required source and let the buyer obtain it separately.
Diagnose missing nodes before launch
Official ComfyUI guidance notes that missing nodes can reflect version differences or startup import failures. Your support instructions should separate an absent node from a node that exists but fails to load.
For a clean-environment check, start with the documented app version, install only declared dependencies, place required models in the specified locations and load the customer graph. Use permitted sample inputs and run through the advertised controls. Record errors, dependency versions and output expectations.
Test the package after disconnecting your private model folders and custom paths. Include a troubleshooting table for missing node, missing model, wrong input dimensions and failed API access. Do not promise success on hardware or application editions you have not checked.
Package and sell the ZIP
The reviewed PayRequest upload rules permit ZIP; JSON is not a direct-upload allowlist member. Put your original workflow, permitted samples, dependency list, setup guide and license in a genuine archive. Avoid bundling large models when the buyer must obtain them separately, and check file and account limits.
Create a PayRequest digital product, show what is included and excluded, connect an eligible payment provider and configure delivery after confirmed payment. Verify the buyer page and an appropriate payment/download check before publishing. PayRequest delivers the package; it does not install nodes, host inference or provide GPU resources.
For business automation exports, use the separate workflow ZIP guide. For mesh and texture products, see Blender asset bundles. Find the broader product families in the specialist download directory.
Market a maintainable edition
Show the output, input requirements and exact support scope. Use a changelog when dependencies change, and state whether updates are included rather than making an unsupported lifetime promise. An original limited sample can let qualified buyers inspect your documentation before they purchase.
Editorial note: AI assisted with writing and the illustrative cover. Official sources and upload code were reviewed on 14 October 2026. The manifest is a fictional planning example. No ComfyUI execution, model-license approval, live purchase or customer result is claimed.
