If you want a prompt conditioning input to apply only during part of generation, use ConditioningSetTimestepRange. If you want the ControlNet guidance itself to begin or end at particular points, set start_percent and end_percent on ControlNet Apply. These controls refer to different objects; choose by what you want to limit, not by treating their percentage fields as interchangeable.
Decide what should be limited
ConditioningSetTimestepRange takes a CONDITIONING input and outputs modified CONDITIONING. Its start and end values define the timestep interval for that conditioning, expressed as percentages of the total generation process. It does not replace the conditioning with a different data type.
ControlNet Apply takes positive and negative conditioning, a ControlNet model and an image, among other inputs. Its start_percent and end_percent control when ControlNet guidance starts and stops influencing image generation. Its outputs are processed positive and negative conditioning.
A practical distinction: ask whether the time limit belongs to a particular conditioning input, or to the ControlNet guidance applied through the ControlNet node. If the latter, adjust the ControlNet window. Changing one does not automatically set the other.
Choose the control by its target
| What you want to limit | Mechanism | What the percentages refer to | Output to connect onward |
|---|---|---|---|
| One conditioning input’s active timestep range | ConditioningSetTimestepRange | start and end as percentages of total generation | Modified CONDITIONING |
| ControlNet’s guidance window | ControlNet Apply | start_percent and end_percent as points in the diffusion process | Processed positive and negative CONDITIONING |
| Both a conditioning input and ControlNet guidance | Both mechanisms, each configured for its own target | Separate ranges; do not assume one controls the other | Follow the graph’s conditioning connections |
The shared use of percentages does not establish that the two nodes affect the same object or have identical behavior. Keep each range tied to its corresponding node and input.
Configure the graph in order
- Identify the exact influence you want to bound: a conditioning input, ControlNet guidance, or both.
- For a conditioning input, place
ConditioningSetTimestepRangeon that conditioning path. Setstartandendto the intended percentages, then connect itsCONDITIONINGoutput to the next conditioning consumer. - For ControlNet, set
start_percentandend_percenton ControlNet Apply. Connect its processed positive and negative outputs to the next ControlNet node or the sampler, as appropriate for the graph. - If both are needed, configure each range independently. Inspect the graph connections to confirm that the conditioning you intended to limit actually passes through the timestep-range node, and that ControlNet uses the intended window.
- As an author-recommended comparison, not a procedure established by the cited documentation, keep the prompt, source image, model and other settings consistent while changing only the range under investigation. Record the target node and the conditioning path being changed. For a conditioning-range comparison, verify that the target conditioning passes through
ConditioningSetTimestepRangeand that other conditioning paths remain unchanged; for a ControlNet-window comparison, verify which ControlNet Apply node and outputs are involved. A single-variable comparison may not isolate an effect in every graph structure. Treat any observed appearance as specific to that workflow, not a general guarantee.
For ControlNet, the documentation also notes that the input image needs preprocessing and that a suitable ControlNet model is required. A timing window does not provide those dependencies. See ConditioningSetTimestepRange documentation and ControlNet Apply documentation.
Use a hypothetical acceptance check
The following is a hypothetical configuration and wiring check, not a software test. Suppose a creator wants a fictional text conditioning to use start=0.25 and end=0.60, while a pose ControlNet Apply node uses start_percent=0.10 and end_percent=0.75. These are independent fields on separate nodes: the values illustrate what to enter and which paths to check, not equivalent effects or one-to-one corresponding stages of generation, and they do not predict a particular image.
| Check | Hypothetical setting or observation | What it can establish |
|---|---|---|
| Conditioning node | start=0.25, end=0.60 | The conditioning node is configured with the intended percentage interval |
| ControlNet Apply | start_percent=0.10, end_percent=0.75 | The ControlNet node is configured with its own intended guidance window |
| Graph path | The target conditioning passes through the range node; ControlNet outputs continue to the intended consumer | The graph wiring matches the chosen control targets |
| Comparison | Keep other inputs fixed and compare a run with a changed range | Whether this particular workflow’s output differs under that change |
A matching configuration is not proof that a visual feature will appear only inside a perceived stage of generation. The cited node descriptions specify parameter roles and data flow, not a guaranteed visual outcome across models, samplers or workflows.
If the result is unclear
First verify the node receiving the changed values and trace the relevant conditioning connections. If the graph is wired as intended, change only one range at a time and compare outputs under otherwise consistent settings. If the issue concerns ControlNet but its image or model input is missing or unsuitable, resolve that prerequisite separately; timing values do not substitute for preprocessing or a model.
The documentation does not specify that these two ranges are equivalent, nor does it promise a particular degree of influence or a universal interpretation of visual stages. Use the parameters to define the documented conditioning interval or ControlNet influence window, then judge the actual output in the specific workflow.
Common questions
Can I use `ConditioningSetTimestepRange` to time-limit ControlNet? Use ControlNet Apply’s start_percent and end_percent when the target is ControlNet guidance. The conditioning node’s documented target is its conditioning input.
Does a conditioning range change the output type? The documented input and output are both CONDITIONING; the output is described as conditioning with the timestep range applied.
Can I set both ranges? Yes, when you intend to limit both targets. Configure and verify each on its own graph path; the documentation does not say that matching values make their effects identical.
Sources and next step
- ConditioningSetTimestepRange - ComfyUI Built-in Node Documentation
- ControlNetApply - 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.