Image Size Bus

The Image Size Bus is the plainest node in the comfyui-bus-plugin pack, and it knows it. It takes a width and a height, and hands them back to you. That's the job description. Where it earns its keep is when the same dimensions need to reach more than one place - EmptyLatentImage, a Resize before a ControlNet preprocessor, an upscale target - and you don't want to edit the same 1024×1024 in four separate widgets.

It's a pass-through junction for two integers, exactly in the spirit of the rest of the pack: ComfyUI has no generic connection type, so you get one small typed node per combination of values, and width+height is one of them. Set the size once here, wire width and height to everywhere that needs them, and one edit fixes the whole workflow.

The inputs and outputs

• width (INT) - default 1024, range 256–16384, snaps to steps of 8.
• height (INT) - default 1024, same range and step.

Outputs are the same two values: width and height, both plain INT ports. Both inputs are widgets by default, so this doubles as a compact input panel at the top of a workflow - and each can be converted to a connection if you'd rather feed the size from a calculator node or an external input.

That's genuinely the entire node. It doesn't compute aspect ratios, it doesn't validate that a model supports the resolution, it doesn't touch pixels. If you need width and height in exactly one place, this node is redundant and you can skip it. If they appear in two or more, it's the difference between updating one number and hunting down three.

Installing it

Same pack as every bus node. ComfyUI Manager: search "comfyui-bus-plugin", Install, restart. Or:

cd ComfyUI/custom_nodes
git clone https://github.com/rhdunn/comfyui-bus-plugin

then restart. Zero dependencies, no models to download - the entire pack is a handful of small Python files.

Common issues

There's very little to trip over here because there's very little happening. The realistic gripes: the step of 8 means you can't type an odd dimension without it rounding, and the node won't warn you that 1024×1024 is a bad idea on a model that expects 512×512. It just routes numbers. If you need a size that's tied to a specific checkpoint's native resolution, that's on you to know - this bus will happily hand out whatever you type. Keep it for organization, not for advice.