Choose LatentUpscale when you need to enter a target width or height; choose LatentUpscaleBy when your requirement is a scale factor. With LatentUpscale, treat crop as a separate framing decision, not part of the size choice. Confirm the input latent’s geometry and units first, then inspect the resulting latent geometry before continuing the workflow.
Decide and set the route
Use this sequence for a specific canvas requirement:
- Read the incoming value’s type label and determine its latent geometry. Do not assume that numbers describing latent cells are pixel dimensions. If the workflow does not make the units clear, resolve that before entering a target.
- Write down the deliverable requirement. If you have a required width and height, or one target side with the other intended to follow the aspect ratio, choose LatentUpscale. Its documented
widthandheightinputs accept a target dimension; setting one to zero calculates that side from the other to maintain aspect ratio. - If your requirement is instead “scale this latent by a factor,” choose LatentUpscaleBy and record the intended
scale_byvalue. Do not translate a desired final canvas into a factor by guessing: first establish the input geometry and the convention your workflow uses. - Record
upscale_methodfor either route. The node documentation exposes this setting but does not establish that one option always produces better detail. - For LatentUpscale, select and record
cropseparately. Decide whether the resulting framing is acceptable; do not infer crop behavior from the width and height entries alone. - Run the workflow and inspect the actual output latent geometry using a suitable downstream display or measurement. Record what the workflow shows, rather than treating an entered value or a calculated value as a verified output.
These are two different latent-space interfaces, not a choice between latent and pixel upscaling. The LatentUpscale documentation lists dimensions and crop, while LatentUpscaleBy lists scale_by.
Use a geometry acceptance worksheet
The following numbers are hypothetical and demonstrate what to record, not a prediction of ComfyUI’s output or rounding behavior. Suppose the input latent is observed as 80 × 60 cells. A creator needs a landscape deliverable but has not yet established whether the requested dimensions refer to latent cells or pixels.
| Check | Explicit-dimensions route | Scale-factor route | Decision or observation |
|---|---|---|---|
| Input | 80 × 60 latent cells; unit confirmed | 80 × 60 latent cells; unit confirmed | Record the observed geometry, not a presumed pixel size |
| Requirement | A chosen target width and height, or one side with aspect ratio maintained | A chosen multiplier | Select the route that matches how the requirement was specified |
| Settings record | width, height, upscale_method, and crop | scale_by and upscale_method | Keep crop review separate from size entry |
| Output check | Record displayed final latent geometry and whether framing is acceptable | Record displayed final latent geometry and compare with the requirement | Do not fill in expected counts before observing the workflow |
For a concrete planning example, the creator might write “target width: 128 cells” only if that is genuinely the intended latent-space target. If the brief instead says “twice the input,” record the intended factor and inspect the output. Neither notation alone establishes pixel dimensions or image quality.
Limits and what to do if it fails
The documentation describes node inputs and outputs; it does not specify the exact geometry-rounding algorithm, a conversion from latent cells to image pixels, or a quality ranking for upscale_method choices. Do not derive those facts from the node name or assume that requested settings guarantee a particular final measurement.
If the observed geometry does not match the requirement, first check the incoming type and units, then verify which node and values the workflow actually uses. For the explicit route, review both dimension inputs and the separately selected crop. For the factor route, verify scale_by. If units or output geometry remain unclear, measure the relevant upstream and downstream values in the workflow before changing settings. If the geometry is acceptable but the final image is not, treat that as a separate visual-quality review; these node descriptions do not promise recovered or improved detail.
Common questions
Can I set only width or only height? Yes. The LatentUpscale documentation says a zero width is calculated from height to maintain aspect ratio, and a zero height is calculated from width. Verify the resulting geometry in your workflow.
Does crop determine the target dimensions? The documentation describes `crop` as affecting cropping, final appearance, and output dimensions. Review it as its own setting; do not assume that changing it is equivalent to changing the requested width or height.
Is a scale factor better for preserving quality? The supplied documentation does not establish a quality advantage for either interface. Choose by how the target is expressed, record the method setting, and assess the actual output for your workflow.
Sources and next step
- LatentUpscale - ComfyUI Built-in Node Documentation
- LatentUpscaleBy - 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.