Resolution Down Step (720→480, 1080→720)

The display name is the whole spec here: feed it 720, get back 480. Feed it 1080, get back 720. This node steps a resolution down by one standard tier - it isn't a general-purpose scale-by-percentage node.

What it's for

Useful anywhere you're doing a two-pass workflow at deliberately different quality tiers - a full-resolution final pass and a faster lower-res draft/preview pass, say - and you want the "one tier down" resolution computed rather than hardcoded twice in your graph. If your pipeline works in the standard 480/720/1080 tiers video generation tends to live in, this saves you a manual lookup.

How it works

The schema exposes a single resolution in, resolution_down out, with no ratio or percentage parameter anywhere. That matches the display name's framing exactly - this reads as a lookup between named, common tiers (1080→720, 720→480) rather than a formula that scales cleanly to arbitrary values.

This kind of node makes sense in a pipeline where "step down one tier" is a decision you make repeatedly and want centralized in one place - say, a graph that generates a hero shot at full resolution and then automatically derives a smaller thumbnail or preview version from the same value, without you having to hardcode the lower number twice and risk the two drifting out of sync if you ever change your base resolution.

Inputs and outputs

• resolution (INT, 1–99999, default 720) - your input resolution.
• Output: resolution_down (INT) - the stepped-down result.

Installing it

No models or extra dependencies mentioned in the README. Search ComfyUI Manager for the repo name first, but a small personal pack like this often isn't indexed - the manual route is the reliable fallback:

cd ComfyUI/custom_nodes
git clone https://github.com/huyl3-cpu/comfyui-sortlist.git

Restart ComfyUI afterward.

Common issues and troubleshooting

Don't assume it extrapolates cleanly outside the two documented tiers. Because there's no exposed ratio parameter, feeding it something like 540 or 4320 - values outside the 720/1080 pairs the display name advertises - puts you in undocumented territory. Test what it actually returns for your specific input before wiring it into anything automated, rather than assuming it generalizes the way a percentage scaler would.

If you need a genuine proportional downscale, this isn't that node. For a half-res, 0.75×, or otherwise ratio-based resize, reach for a standard scale-by-factor node instead - this one is purpose-built around the specific named tiers in its title, not general resolution math.

It only outputs a number, not a resized image. This is a calculator, not an image-resize node - you still need to feed resolution_down into an actual resize/scale node to change anything about your images or video.

There's no companion "step up" node in this pack. If your pipeline needs to go the other direction - deriving a higher tier from a lower one - you won't find a matching node here to do it symmetrically; you'd be hardcoding that value or building the lookup yourself.