Preview Integer
Check the seed, steps, or batch size your workflow is really passing around
Integers are everywhere in ComfyUI and you can't see any of them. The seed that a sampler actually received, the step count after some node did arithmetic on it, the width your workflow thinks it's using - all invisible unless you go hunting. Preview Integer puts one of them on the canvas for you.
It comes from ComfyUI Extended, the small zero-dependency utility pack, alongside Preview Float, Preview Boolean, and Preview Text. They're the same node in four types: a dead-end display that makes one value visible.
How it works
A single required input, int (INT), marked forceInput in the source - it wants a wired integer, not a typed one. On execution the node pushes the value over a websocket to the browser, and the pack's frontend (web/preview.js) writes it into a read-only widget on the node. Full integer, no rounding, no truncation.
It's an output node with no output sockets (OUTPUT_NODE = True, empty RETURN_TYPES), so it terminates whatever wire you hang it on. That's fine - its job is to be the last stop.
Pairing tip: if you want to change an integer between runs instead of just watching it, the same pack's Integer primitive (PrimitiveInteger) gives you increment/decrement/randomize modes. Preview and primitive together are a genuinely tidy loop for iterating on a seed or a step count.
Install
Standard for this pack, which has no dependencies:
cd /path/to/your/ComfyUI/custom_nodes
git clone https://github.com/rookiepsi/comfyui-extended.git
Restart ComfyUI. Or via ComfyUI Manager: search "ComfyUI Extended", install, restart. No models, no pip installs, nothing heavy.
Common issues
- Empty until you run. It populates after the queue executes. Run first, judge second.
- Widget won't refresh. Hard-refresh the browser so the pack's
web/assets reload, then run again. - No output socket. You can't chain through it. If you need the value downstream too, branch your wire before the preview.
The dry truth: it's a debugging convenience, not a workhorse. But when you're chasing a "why is this 512 wide" mystery, seeing the integer print right on the node kills the guesswork in one run.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| int | INT | — |
Outputs (0)
No outputs