ComfyUI can reduce the spatial overlap on a tiled VAE node when tile_size is less than four times the entered overlap. In that case, the documented adjusted overlap is one quarter of tile_size. The displayed input and the value used during processing may therefore differ; that alone does not mean the node ignored your setting.
Check the spatial settings in order
- Identify the node and operation.
VAEEncodeTiledtiles an image into aLATENT;VAEDecodeTileddecodes aLATENTinto anIMAGE. Both have spatialtile_sizeandoverlapcontrols, but they perform different operations. Check the type labels and connected data rather than relying on node color. - Read the configured
tile_sizeandoverlapseparately. Do not infer the effective overlap from the slider position or the node’s general tiled purpose. - Compare the values using the documented condition: does
tile_size < 4 × overlap? If yes, calculatetile_size ÷ 4as the documented adjusted overlap. If not, this particular automatic-adjustment condition is not met. - Record the configured value, the comparison, and the calculated value. Treat the calculation as the documentation’s rule, not as an independently observed runtime measurement.
- Run the workflow and inspect the resulting image for visible discontinuities where tiles meet. This visual review is an editorial acceptance check, not a guarantee that a particular overlap produces a particular quality.
The tiled decode documentation describes the spatial adjustment. The tiled encode documentation identifies the corresponding image-encoding controls. The node docs also note that VAE compression ratios are accounted for when calculating tile and overlap sizes, so do not assume the UI values directly describe pixel dimensions in the processed image.
Hypothetical worksheet: check 256 and 96
The numbers below are a hypothetical calculation using the documented rule, not a report from running ComfyUI. Use a separate observation column for what you actually see in your workflow.
| Check | Hypothetical entry | Decision or observation |
|---|---|---|
Spatial tile_size | 256 | Record the configured input |
Entered spatial overlap | 96 | Record this separately from the effective value |
| Four times overlap | 384 | Compare 256 with 384 |
| Constraint result | 256 < 384 | The documented adjustment condition is met |
| Expected adjusted overlap | 256 ÷ 4 = 64 | Record 64 as the rule-based expected value, not a runtime measurement |
| Output boundary review | Not yet observed | After a run, note any visible join discontinuity; do not infer quality from the arithmetic alone |
For a real workflow, replace the hypothetical entries with your node values. If you have a runtime log or other direct evidence of the value used, record that separately; the cited documentation does not specify how to expose or log that value.
Limits and what to check next
Do not apply the spatial formula to video settings. temporal_size and temporal_overlap concern chunks of frames for video VAEs, not the width or height of spatial tiles. The decode documentation gives a separate temporal rule: when temporal_size is less than twice temporal_overlap, temporal overlap is halved. The encode documentation says those temporal controls are relevant only to video VAEs and have no effect on standard image VAEs. See the encode node reference before diagnosing a video workflow.
If the spatial condition is not met but the behavior still seems unexpected, check that you are inspecting the correct tiled node and its connected IMAGE, LATENT, and VAE inputs. Then compare the output at tile joins and consult the node documentation for the operation in use. The supplied documentation establishes the adjustment rule, but does not promise a particular seam-free result, prescribe a universal best overlap, or describe a UI display of the runtime value. A calculated effective value is not proof that the output will look better or recover missing detail.
Does this mean the node ignored my input?
Not necessarily. When the documented condition is met, the rule accounts for a lower effective spatial overlap.
Should I increase `tile_size` instead?
The rule explains when overlap is adjusted; it does not prescribe a best setting. Choose values for your workflow, then review the output and resource behavior.
Does this rule apply to `temporal_overlap` too?
No. Video temporal settings have a separate documented condition. Evaluate them against temporal_size, not spatial tile_size.
Sources and next step
- VAEDecodeTiled - ComfyUI Built-in Node Documentation
- VAEEncodeTiled - 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.