Before wiring a ComfyUI latent crop pass, measure the latent grid with GetLatentSize and plan every region in latent cells, not image pixels. Record each crop as width, height, x, and y, then compare its rectangle with the recorded grid bounds. For adjacent passes, note the intended shared area explicitly; this is a planning convention, not a promise that cropping will blend or combine regions.
Plan from the measured grid
Use this sequence when splitting a latent for separate passes:
- Connect the latent you intend to process to GetLatentSize. Record its width and height in latent cells. If the node reports multiple streams, the documentation says it measures the first; confirm that this is the latent you mean to plan against.
- Make a grid record, such as
W = 96 cells,H = 64 cells. Keep frames and batch size as separate notes if relevant; they are also reported, but are not the width and height used in the rectangle check below. - Define each planned rectangle using the LatentCrop fields
x,y,width, andheight. For a consistent planning audit, treat the rectangle as starting at(x, y)and extending by its stated width and height. Check0 ≤ x,0 ≤ y,x + width ≤ W, andy + height ≤ H. This is an author-recommended bounds check, not a documented claim about how the node handles out-of-range inputs. - For each neighboring pair, compare the rectangles on both axes and record each non-empty shared interval; mark an axis with no shared interval as “none.” This records intended coverage only. It does not specify how separately processed latents will later be combined.
- Wire the reviewed values to LatentCrop, whose documented input is
LATENTand whose output is alsoLATENT. Check the actual type labels in the workflow; node color alone is only a visual clue.
This workflow separates geometry planning from pixel-image cropping and from latent compositing. GetLatentSize reads latent geometry without decoding it, while LatentCrop takes a latent plus crop dimensions and start coordinates.
Example acceptance worksheet
The following is a hypothetical planning example, not measured software output or a recommended universal layout. Assume GetLatentSize reports a 96 × 64 cell grid. The proposed rectangles below intentionally overlap by 8 cells horizontally. The overlap values are calculated for this worksheet by comparing rectangle ranges; the documentation does not define an overlap calculator or blending behavior.
| Block | x, y | width × height | Planned shared intervals (x; y) | Bounds decision |
|---|---|---|---|---|
| A | 0, 0 | 52 × 64 | Reference for B | Fits: right edge 52, bottom edge 64 |
| B | 44, 0 | 52 × 64 | With A: x 44–52; y 0–64 | Fits: right edge 96, bottom edge 64 |
| C | 48, 0 | 48 × 64 | With B: x 48–96; y 0–64 | Fits: right edge 96, bottom edge 64 |
For this hypothetical sheet, every rectangle stays within the recorded canvas. The A–B shared width is 8 cells; B–C shared width is 48 cells. Those figures describe the chosen rectangles, not guaranteed seam quality or useful processing context. If the overlap is unintended, revise coordinates or dimensions in the plan and repeat the arithmetic before connecting values.
Limits and what to do when a check fails
The cited node pages describe latent-cell measurements and crop inputs, but do not specify padding, clamping, rejection, seam handling, or a rule for choosing an ideal overlap. Do not assume an out-of-bounds crop will be corrected automatically. If any rectangle fails the bounds check, stop and revise the recorded start or size, or remeasure the latent actually connected to the workflow. If the grid measurement is unexpected, first verify the connected latent and whether the first-stream measurement applies. If regions need to be assembled after separate processing, treat that as a separate workflow decision; these two node descriptions do not establish a compositing method. The worksheet is a human review aid, not evidence of an executed ComfyUI test.
Three quick questions
Are these coordinates pixels? No. GetLatentSize reports width and height in latent cells. Do not copy pixel coordinates into this plan without a separately established conversion.
Does overlap make the crops blend? The cited documentation does not say so. Record overlap as planned shared coverage, and determine separately how your workflow handles results.
What if my latent contains multiple streams? GetLatentSize documents that it measures the first stream. Confirm that this measurement represents the latent you intend to crop before relying on the worksheet.
Sources: GetLatentSize documentation; LatentCrop documentation.
Sources and next step
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.