πͺ π Preview Image Size & Aspect Ratio
See β1216 x 832β before you spend five minutes rendering it
This is a display node, and I mean that literally: it has no outputs. You wire numbers or a ratio into it, and it renders a summary card on the node - the dimensions and the ratio they work out to. That sounds trivial until you're running width and height through a text parser and a couple of math nodes and you genuinely cannot see what values are arriving without queuing a full render to find out.
Where it earns its slot: after a ratio finder, so you can eyeball that it produced 1216 x 832 rather than 832 x 1216 before you commit. Or on the width/height outputs of an image loader, so you can see the true resolution of a source image you're about to re-render.
How it decides what to display
There's a precedence order, and it explains most confusing readouts:
widthandheightboth wired and both above zero β it divides them for the ratio and displaysW x H.- Otherwise,
aspect_ratiowired β it parses the string, accepting:,x,Xor/as the separator (16:9,2.35:1,3x2), and displays that ratio's dimensions. - Otherwise,
ratio_floatβ shown as a single-digit ratio:1.85 x 1for landscape, or1 x 1.5for portrait. - Nothing wired β
1 x 1, silently.
The result is pushed to the frontend, which draws it on the node. Nothing goes to the console, so if you're looking for the value in your terminal log you won't find it.
Worth clearing up one thing the pack's README implies: despite the "image size" name, there is no IMAGE input on this node. It doesn't measure a tensor. You feed it the integers. If you want dimensions from an actual image, take them from the loader's own width/height outputs.
Inputs and outputs
All four inputs are optional and all four are input-only (they don't get widgets you type into):
width-INTheight-INTaspect_ratio-STRINGratio_float-FLOAT
And there are no outputs at all - it's a terminal node. To place it in a workflow, connect it off the same wire that feeds your latent node.
Install
ComfyUI Manager β search SaturnNodes, or:
cd ComfyUI/custom_nodes
git clone https://github.com/KOFiblto/ComfyUI-SaturnNodes
Restart. No dependencies beyond the pack's Pillow/numpy/piexif trio, no models, no install script. Category is πͺ SaturnNodes/Utils.
Why bothering with a size readout at all
Because resolution is where images go wrong. Every model has a native resolution - 1024Γ1024 for SDXL, with a small set of trained aspect ratios around it - and generating outside that gives you duplicated anatomy and tiling rather than a nice big picture. The old failure people post about constantly is asking a 1024-trained model for 1920Γ1080 because they wanted widescreen. Newer architectures are more forgiving, mostly taking any size in roughly a 1β2 megapixel band and degrading softly, but "roughly" is doing a lot of work in that sentence.
So having the exact numbers visible mid-graph is a cheap sanity check, especially when the number came out of a string in your prompt rather than a widget you typed.
Where people get burned
It says 1 x 1 and you assume the workflow is broken. All four inputs are optional, so an unwired node happily reports nothing. Check the wire before you check the node.
Typed floats into INT sockets. width and height are strictly integers; ComfyUI will refuse a FLOAT link. Round or cast upstream.
Expecting it to simplify the ratio. It doesn't snap to a nearest known ratio or reduce a fraction - it shows you what you gave it. Give it 1216 and 832 and you get 1216 x 832, which is the useful thing anyway.
The ratio looks inverted. Width and height got swapped somewhere upstream. That's exactly the bug the node exists to catch, so, job done.
Inputs (4)
| Name | Type | Default | Description |
|---|---|---|---|
| widthopt | INT | 00β16384 | β |
| heightopt | INT | 00β16384 | β |
| aspect_ratioopt | STRING | β | |
| ratio_floatopt | FLOAT | 0.000β100 | β |
Outputs (0)
No outputs