64

Sixty-four. Not a resolution you'd type into an Empty Latent, not a step count - but arguably the most common integer inside a ComfyUI graph that you never see. It's the size of the latent tiles most upscalers and tiled samplers carve your image into, and it's a batch size that shows up in node internals everywhere. This constant node from the ComfyUI-GadgetNodes pack (2daadv, MIT, one-developer, brand new with no reputation yet) exists so that when a node does expose a 64, you can feed it from one authoritative source instead of retyping it.

The mechanism is the same as every const node in the family: no inputs, one fixed INT output of 64, no state, no dependencies. It lives under Gadget/core/const, alongside its siblings 0, 1, -1, 256, 512, and 1024. Install once for the whole family: ComfyUI Manager → search "GadgetNodes", or

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

then restart ComfyUI.

Where 64 actually earns its keep:

• Tiled upscaling and inpainting tile size. A whole genre of upscaling nodes (the tiled-diffusion family in post-processing land) slices images into tiles, and 64 is the classic small-tile edge - the fastest path to tile-free seams at the cost of more passes. If your upscaler exposes a tile_size widget, 64 as a constant gives you a single knob to experiment with (try 64 vs 128 and watch your VRAM graph move).
• Batch slicing. Some image-batch utilities take a batch_size or chunk_size; 64 images at a time is a sane middle ground for tagging and preprocessing passes on a consumer GPU.
• The latent unit. Latent space is literally eight times smaller than pixel space, so a 512-pixel image is a 64-latent square. Any node that reasons in latent coordinates is working in 64s.

Honest take: this is the least-typed constant of the pack's resolution set. You'll wire 512 or 1024 into more things on a normal day. But when a tiling or batching node is being fiddly, having 64 available as a locked value - one that can't be accidentally nudged to 63 mid-experiment - is quietly useful. It's also a nice reminder that the cheap way to shrink VRAM pressure is often to shrink the tile, not the model.

Wire the 64 output into any integer input that wants it, and if you find yourself adjusting it every run, that's a signal you wanted a widget, not a constant.