Use FluxGuidance when you want to adjust the guidance value carried in FLUX conditioning. Use FluxDisableGuidance when your goal is to remove the guidance embed. These are different documented operations; the available documentation does not establish that setting the value to zero is equivalent to explicitly disabling guidance. Decide whether you want to tune a value or turn off the mechanism before editing the workflow.
Choose the operation and check the conditioning path
The ComfyUI documentation describes FluxGuidance as accepting CONDITIONING and a guidance value, then returning CONDITIONING containing the new value. Its stated range is 0.0 to 100.0. FluxDisableGuidance accepts CONDITIONING and returns modified CONDITIONING with guidance disabled by setting its value to None. See the official FluxGuidance documentation and FluxDisableGuidance documentation.
Use this ordered workflow:
- Identify the FLUX workflow’s text-encoding output and trace the CONDITIONING connection that reaches the sampler. Record the existing route as the baseline.
- Duplicate that route into three clearly named branches: original, value-adjusted, and disabled. Keep the same prompt, input image if present, sampler settings, and other workflow inputs for all branches.
- On the value-adjusted branch, insert FluxGuidance between the existing conditioning source and its downstream conditioning connection. Change only its guidance input for each comparison; stay within the documented range.
- On the disabled branch, insert FluxDisableGuidance on the conditioning route. Confirm its output, rather than the unmodified source, reaches the same downstream destination.
- Check the node input and output type labels and wire direction. Color may help locate a node, but use the displayed type labels and actual connections to verify the route.
- Generate and record each branch under the same remaining settings. Treat the resulting images as observations, not as proof that either operation must produce a particular visual change.
If your purpose is simply “less prompt influence,” do not select a node by name alone. Decide whether you want to compare guidance values or remove the embed, then build the corresponding branch.
Acceptance worksheet: three controlled branches
The following is a hypothetical record format, not a measured result or a promise about generated images. For example, a creator might use one prompt, one source image, and identical sampler settings across all branches, then record whether a requested object is present and whether the composition changed. The observations must come from the creator’s actual outputs.
| Branch | Recorded workflow check | Hypothetical observation | Decision |
|---|---|---|---|
| Original | Source CONDITIONING goes to the sampler path | Requested object present; composition unchanged from the saved baseline | Keep as the comparison reference |
| Value-adjusted | FluxGuidance output reaches the same downstream path; record the entered value | Requested object absent; composition also differs | Record both observations; do not infer a universal effect from one image |
| Disabled | FluxDisableGuidance output reaches that path | Requested object present; another detail differs | Keep this as a distinct result, not as evidence that a zero value would match |
Before accepting the comparison, verify that only the intended guidance operation differs between branches. If a branch bypasses its node, connects to a different destination, or uses a changed prompt or sampler setting, mark the comparison inconclusive and correct the workflow before drawing a conclusion.
Limits and what to do when the comparison fails
The published node pages describe the conditioning changes, but do not prescribe a recommended guidance value, guarantee how a particular prompt will respond, or establish equivalence between zero and None. Do not report a universal “best” value or promise that disabling guidance will preserve a particular image detail.
If the value-adjusted branch looks unchanged, first verify that the FluxGuidance output is actually connected downstream and that the entered value was applied. If the disabled branch appears to follow the original, that single observation does not prove the operations are equivalent; check the connection and repeat the controlled comparison if the distinction matters. If the workflow does not expose the expected CONDITIONING route, inspect the actual node types and wiring before inserting either node. The cited documentation does not establish how every custom node or workflow handles these connections.
Three quick questions
Is zero the same as disabling guidance? The cited documentation does not say so. FluxGuidance sets a numeric value; FluxDisableGuidance sets guidance to None. Treat them as separate conditions unless further documentation for your specific workflow establishes otherwise.
Which branch should I use to reduce prompt influence? Use the value-adjusted branch if you want to tune a guidance value. Use the disabled branch if your intention is to remove the guidance embed. The documentation does not guarantee a particular relative visual effect.
Can I compare the outputs fairly? Yes, as an author-recommended workflow: hold the prompt, input, and other settings constant, verify each CONDITIONING route, and record the actual outputs. This controls the comparison; it does not make the results a software guarantee.
Sources and next step
- FluxGuidance - ComfyUI Built-in Node Documentation
- FluxDisableGuidance - ComfyUI Built-in Node Documentation
This guide interprets public documentation and uses explicitly hypothetical acceptance examples, not application tests. Controls and availability can change; verify the cited manual against your installed version.
For work created in Imagild, carry the input requirements and acceptance checklist into the photo editor. The external software controls discussed above belong to their respective products.