Comfy Credits are Comfy's account balance for paid Partner Nodes and GPU runtime in Comfy Cloud. You purchase or manage them through your Comfy account, and supported usage in local ComfyUI can draw from the same balance. They are a billing unit for hosted work, with consumption determined by the service and settings you run. Comfy credit rules
What are the key facts about Comfy Credits?
| Field | Verified information |
|---|---|
| Developer | Comfy, which operates Comfy Cloud and the Partner Nodes billing system. Provider documentation |
| Released | A standalone launch date for the credit unit is not published in the cited billing documentation. Credit rules |
| Type | Usage credits for Partner Nodes and cloud GPU execution. Credit rules |
| Size or parameters | Not applicable: Comfy Credits are a billing unit. Credit rules |
| License and access | Paid service access through a Comfy account; the ComfyUI application itself uses GPL-3.0. Partner Nodes, software license |
| Where it runs | Comfy Cloud and supported Partner Nodes in local ComfyUI; hosted models execute remotely. Credit rules, Partner Nodes |
| Conversion | Comfy publishes 211 credits per US dollar; model charges vary with generation settings. Pricing documentation |
What can you pay for with Comfy Credits?
Comfy's unified balance makes it possible to use cloud GPU execution and supported model APIs within the same account. The billing documentation distinguishes these two kinds of consumption and provides a credit history for checking what a run actually used. That is useful when a workflow combines locally available components with hosted generation. Credit rules
Partner Nodes provide access to external models through the node interface. Their practical benefit is workflow composition: an externally generated image can feed subsequent processing in the same graph. The model service remains hosted even when the graph is open on your computer. Partner Nodes overview
For planning, write down the paid stages before estimating a project. A draft might require an image generation, a variation, and a final export; another project might require only one paid generation. Count the work your graph performs and the outputs you keep separately. This gives you a useful cost measure: total project spending divided by accepted deliverables.
When do Comfy Credits expire, and what billing limits apply?
Credits have different expiration rules. Comfy's FAQ says monthly credits expire at the end of the billing period, while purchased top-ups expire one year after purchase. Credits cannot be transferred or refunded; Comfy directs technical billing errors to support. Check these rules before prepaying for work you may postpone. Partner Nodes FAQ
Prepayment also has a documented edge case: usage reports can arrive after execution, temporarily pushing a balance below zero. Comfy says further supported usage may then be unavailable until the balance is positive. Keep enough balance for the planned run instead of treating the displayed amount as a precise spending stop. Credit rules
There is no universal credit cost for an image. Comfy's pricing page explicitly makes the selected model and its settings part of the calculation. A quote for one node cannot establish the price of a different image model, a video operation, or an entire graph. Partner Nodes pricing
The account FAQ and overview contain differing detail about remote login. The overview documents Comfy API key login for non-whitelisted sites, while parts of the FAQ still describe localhost-only access. Use the overview's dedicated account instructions for that setup; do not assume a remote address supports ordinary browser login. Overview, FAQ
How do you buy Comfy Credits and check workflow costs?
- Open your ComfyUI settings and sign into your Comfy account under User.
- Open Credits, inspect the available balance, and purchase a top-up if needed.
- Add the intended Partner Node and choose its model settings.
- Check that node's published price before running the workflow.
- Execute a small trial, then review the charge in your credit history. These account and execution steps follow Comfy's documentation. Setup, pricing and management
Make the trial representative. Use the intended output settings and include any paid processing that a finished image will require. Record the balance change alongside the workflow name, model, and settings. Repeat this measurement when you change the graph substantially; a cost estimate belongs to the workflow you measured.
For a manual local installation, Comfy documents this launch option to disable its built-in Partner Nodes:
python main.py --disable-api-nodes
Run it from the ComfyUI directory in the environment used for your installation. This is useful when preparing a session that relies on local model execution; it does not purchase credits or impose a budget on a separate hosted account. Documented launch option
Keep installation choices and credit budgeting connected. The ComfyUI guide explains the workflow environment, while the cloud GPU pricing guide provides a place to compare infrastructure options before deciding where to execute a graph.
How do local ComfyUI, Partner Nodes, and Comfy Cloud compare?
The meaningful comparison is between execution arrangements, because a credit balance does not generate an image by itself.
| Arrangement | What you manage | What to measure |
|---|---|---|
| Local ComfyUI with local models | Your installation and hardware; Comfy describes local use as free. Overview | Resource use and time for your chosen workflow |
| Local ComfyUI with Partner Nodes | Comfy account balance and model-specific service charges. Pricing | Paid calls needed for an accepted result |
| Comfy Cloud | Hosted GPU work and any Partner Nodes used by the graph. Credit rules | Combined execution and model usage |
Choose the arrangement around the workflow you need to finish. Compare the same deliverable, including revisions, in each option. A low generation price offers limited value if the selected service lacks a required operation or produces drafts that need extensive additional work.
What else should you know about Comfy Credits?
Do I need Comfy Credits to run Stable Diffusion locally?
Comfy describes local ComfyUI use as free, with Partner Nodes available as an optional paid feature. A graph using local models does not require Comfy Credits merely because it uses the ComfyUI interface. Local-use policy
How much is one dollar of Comfy Credits?
The cited pricing documentation lists 211 credits per US dollar. Use the current node price to estimate a generation, since the conversion alone does not specify how much work a model performs for that amount. Pricing
Can I use cloud subscription credits in local ComfyUI?
Comfy says subscription credits and top-ups can fund supported usage across Cloud and Local. In local ComfyUI, that includes eligible Partner Nodes connected to your account. Credit rules
Where can I check an unexpected charge?
Open the account's credit history and match the usage to your workflow runs. Comfy directs billing discrepancies to its support process; retain the relevant run details so the charge can be investigated. Credit history instructions
Sources
- Comfy credit rules
- Partner Nodes pricing
- Partner Nodes setup and execution
- Partner Nodes FAQ
- ComfyUI software license
Top comments (0)