Int2String

Int2String does exactly one thing: takes an INT and hands back a STRING. That's the entire node - no formatting options, no padding, no radix. It exists to bridge a gap ComfyUI doesn't close automatically: an INT socket and a STRING socket are different types, and most of the graph won't let you wire one directly into the other even when what you conceptually want is obvious, like stamping a seed number onto an image filename.

This is the kind of node you don't think you need until you do. A seed value, a batch index, a width or height coming out of another node as an INT - none of it can go straight into a text field without a cast, and Int2String is that cast.

How it works

There's no logic worth describing beyond the type conversion itself - it calls Python's str() equivalent on whatever integer arrives and passes the result along. No tooltip, no hidden formatting behavior; what you put in is what comes out, just as text.

The inputs and outputs that matter

• Int - the only input, required. Wire it from anywhere that outputs an INT: a seed, Chibi's own ImageSizeInfo width/height, a batch counter, whatever.

One output: STRING, ready to plug into any text field - Chibi's ImageAddText text field (to stamp a seed or index onto an image), SaveImages' fixed_filename_override (to number your outputs), a Textbox, or string concatenation elsewhere in your graph.

How to install it

• ComfyUI Manager: search "ComfyUI-Chibi-Nodes", install, restart.
• Manual: cd ComfyUI/custom_nodes && git clone https://github.com/chibiace/ComfyUI-Chibi-Nodes/, restart.

Nothing to download, no dependencies - this is about as minimal as custom node logic gets. It appears under Chibi-Nodes/Text once installed. For the pack overall, the author's README calls these "experimental nodes" and jokes that version 2 shipped "with more bugs" - a node this small has essentially no surface area for that to matter, but it's the general calibration worth carrying into every node in this collection: small, personal, useful, not heavily maintained.

Common issues

There's genuinely very little to troubleshoot here. If a downstream node still rejects the connection after wiring Int2String's STRING output in, double-check you're actually feeding the STRING output and not accidentally still wired to the original INT source - it's an easy slip when you're rewiring a graph and forget to move the connection to the new node's output rather than just adding it alongside the old one. Beyond that, this node either works or the type mismatch it's meant to fix wasn't the actual problem.