Comfy-Org/ComfyUI · error · ValueError
Bria can upscale up to a maximum output dimension of {BRIA_M
Error message
Bria can upscale up to a maximum output dimension of {BRIA_MAX_OUTPUT_SIDE} pixels: input is {width}x{height}, x{multiplier} would be {predicted} pixels on the long side. Enable auto_downscale, or use a smaller input image or a lower multiplier. What it means
Bria's upscaler caps output at BRIA_MAX_OUTPUT_SIDE pixels on the long side. The node predicts the long side after the x-multiplier and, if it exceeds the cap and auto_downscale is off, raises instead of letting the API fail. The message names the input size, multiplier, and predicted side.
Source
Thrown at comfy_api_nodes/nodes_bria.py:725
expr="""{"type":"usd","usd":0.0286}""",
),
)
@classmethod
async def execute(
cls,
image: Input.Image,
desired_increase: str,
auto_downscale: bool,
moderation: dict,
) -> IO.NodeOutput:
multiplier = int(desired_increase)
height, width = get_image_dimensions(image)
if _upscaled_output_side(height, width, multiplier) > BRIA_MAX_OUTPUT_SIDE:
candidates = [c for c in (4, 2) if c <= multiplier]
if not auto_downscale:
predicted = _upscaled_output_side(height, width, multiplier)
raise ValueError(
f"Bria can upscale up to a maximum output dimension of {BRIA_MAX_OUTPUT_SIDE} pixels: "
f"input is {width}x{height}, x{multiplier} would be {predicted} pixels on the long side. "
f"Enable auto_downscale, or use a smaller input image or a lower multiplier."
)
fitted = next(
(c for c in candidates if _upscaled_output_side(height, width, c) <= BRIA_MAX_OUTPUT_SIDE), None
)
if fitted is not None:
multiplier = fitted
else:
shrinkable = next((c for c in sorted(candidates) if _smallest_output_side(height, width, c)
<= BRIA_MAX_OUTPUT_SIDE), None)
if shrinkable is None:
raise ValueError(
f"This image cannot be upscaled by Bria at any multiplier: it is {width}x{height}, and "
f"Bria first enlarges the short side to {BRIA_MIN_SHORT_SIDE} pixels, which pushes the "
f"long side past the {BRIA_MAX_OUTPUT_SIDE} pixel limit. Crop it to a squarer shape first."
)View on GitHub (pinned to 1c6d8d45b3)
Solutions
- Enable the auto_downscale input: the node then picks the largest fitting multiplier (4 or 2) or downscales the input first.
- Lower the desired_increase multiplier so the predicted long side fits.
- Feed a smaller input image (downscale before the node).
Example fix
// before auto_downscale: false, desired_increase: '4' // after auto_downscale: true, desired_increase: '4'
Defensive patterns
Strategy: validation
Validate before calling
long_side = max(get_image_dimensions(image))
if long_side * multiplier > BRIA_MAX_OUTPUT_SIDE:
multiplier = next(m for m in (multiplier, 4, 2) if long_side * m <= BRIA_MAX_OUTPUT_SIDE) Prevention
- Leave auto_downscale enabled unless you need an exact multiplier.
- Compute max(long_side) * multiplier against the cap before queueing large inputs.
When it happens
Trigger: desired_increase parsed as multiplier N; _upscaled_output_side(height, width, N) > BRIA_MAX_OUTPUT_SIDE; auto_downscale widget is false. E.g. a 6000px-long image at x4.
Common situations: User upscales an already-high-resolution render; multiplier widget left at 4 from a small-image workflow; unaware of the output-side cap.
Related errors
- Bria accepts a width-to-height ratio between {BRIA_MIN_RATIO
- This image cannot be upscaled by Bria at any multiplier: it
- One of prompt or structured_prompt is required to be non-emp
- The mask is empty, so there is nothing to {action}. Masks ar
- Mask must have the same aspect ratio as the image: image is
AI-assisted analysis of Comfy-Org/ComfyUI@1c6d8d45b3 (2026-08-14).
Data as JSON: /api/errors/dbff7511bd7bcb7e.
Report an issue: GitHub.