ComfyUI workflows have turned into a real product. People will pay for a clean, documented graph that gets a result they can’t get on their own — a consistent character pipeline, a FLUX upscaling chain, a face-swap setup that actually holds. The catch is that most places you can sell one treat it like a generic file. Here’s how to package and sell ComfyUI workflows so buyers trust them and you get paid cleanly.
What buyers actually pay for
- A result, not a graph. Lead with the output. Show the before/after, the sample renders, the use case. The JSON is the delivery, not the pitch.
- Documentation. Required custom nodes, model and LoRA dependencies, recommended settings. Half of all workflow refunds are “it won’t load” — missing nodes or models.
- Compatibility. State the base model (SDXL, FLUX, Pony), ComfyUI version, and VRAM target up front so buyers self-qualify before they pay.
- A license. Personal vs commercial use, redistribution rules. Vague licensing is where disputes start.
How to package a workflow for sale
Ship the JSON (or the embedded PNG you can drag into ComfyUI), a README with dependencies and settings, and sample outputs. Version it — “v1.2, updated for the latest FLUX node” — because workflows break when nodes update, and buyers will come back for fixes. If you trained a LoRA the workflow depends on, decide whether to bundle it or sell it separately with a clear link.
Where most platforms fail workflow sellers
The common stores treat a workflow as a ZIP with a description box. There’s no field for base model, required nodes, or license; buyers can’t filter; and the card payout runs on a processor that may flag AI content. So you get refunds on avoidable compatibility mismatches and a payout layer that treats your category as risky. A workflow deserves a real SKU, not a generic download listing.
Where Clanry lands
Clanry gives ComfyUI workflows a structured schema — base model, required nodes, version, license, preview — so buyers know exactly what they’re getting and refunds drop. The payment path excludes Stripe and settles non-custodial USDC directly to your wallet, with no chargebacks and no held balance. AI work is covered by a written safe harbor, so a workflow shop isn’t living on borrowed time.
See also selling AI prompts, LoRAs and workflows and Clanry vs Gumroad.
FAQ
Where can I sell ComfyUI workflows?
Workflows sell on general digital-product stores and freelance marketplaces, but those treat them as generic files. A platform with a structured workflow SKU — dependencies, version, license, preview — gives buyers more confidence and reduces refunds.
How do I stop refunds on workflow sales?
Most refunds are compatibility issues. State base model, required custom nodes, ComfyUI version, and VRAM up front, ship a README, and version the workflow so buyers know it’s maintained.
How do I get paid for ComfyUI workflows without chargebacks?
On-chain settlement has no chargebacks. On Clanry, buyers can pay by card or fiat-to-crypto and you’re settled non-custodial USDC to your wallet — final at confirmation.
Built by the banned. Claim your handle.