1024

One thousand twenty-four. The native square of SDXL and most of what came after it - Flux, Illustrious, the whole 2024-and-later generation basically trains and expects at 1024, and 1024×1024 is the resolution most modern models are happiest at. This constant node from 2daadv's ComfyUI-GadgetNodes pack outputs a fixed INT of 1024 and nothing else, which makes it the most genuinely useful of the pack's constants: it's the number you're typing into width and height on almost every modern workflow.

Same family, same mechanics: no inputs, one INT output, no state, no frontend tricks. It lives under Gadget/core/const with 0, 1, -1, 64, 256, and 512. The pack is MIT-licensed, one developer, and new enough that there's no community reputation to lean on - but the const nodes are four lines of Python each, so there's not much to go wrong. Install once:

cd ComfyUI/custom_nodes
git clone https://github.com/2daadv/ComfyUI-GadgetNodes.git
pip install -r ComfyUI-GadgetNodes/requirements.txt

then restart, or search "GadgetNodes" in ComfyUI Manager.

Why lock 1024 in instead of typing it:

• Width and height, twice. An SDXL workflow has width and height on the Empty Latent, and quite possibly on a resize node or two as well. Type 1024 into four widgets and they will drift apart eventually - one gets edited, the others don't. A single constant feeding all of them makes the graph self-consistent by construction. This is the node-plumbing "one source, many consumers" pattern in its most everyday form.
• Tiles too. Tiled samplers that process 1024×1024 chunks are a common compromise between quality and VRAM; the constant keeps the tile size fixed while you tune everything else.
• A sanity baseline. When a workflow starts producing weird crops, knowing 1024 is locked as the intended size lets you blame the resize node instead of the dimension.

The caveat, stated plainly: 1024 is the default, not the rule. Portrait and landscape crops, 768 for fast passes, 1536 on big cards - all legitimate, and if you vary them per-run you want a widget, not a constant. The constant is for when "square at 1024" is your workflow's contract with itself.

Wire the 1024 output into any integer input that should always say 1024. It'll be the most-used member of the family for anyone running modern models.