Nodes/Praveen's ComfyUI Tools/Tile Info Display
ComfyUI Node

Tile Info Display

See the tile geometry when your tiling workflow misbehaves

By Praveenhalder·Created about a year ago·Updated 7 months ago· 2
Tile Info Display
  • tile_info
  • info_text

Tile Info Display is a debug node for the pack's tiling pair. You feed it the tile_info blob that Image Tile Split produces, and it prints a human-readable summary of the tiling geometry: grid size, original image dimensions, tile size, base tile size, overlap in pixels and percent, batch size, and total tile count. If your split/merge workflow is producing seams, wrong dimensions, or scrambled output, this is the node that tells you whether the metadata is what you think it is.

The whole thing exists because tile_info is an opaque dict. You can't see into a TILE_INFO wire, and when the merge comes out wrong you have no idea whether the problem is your processing, your merge settings, or the split geometry itself. This node makes the invisible visible.

How it works

One required input, tile_info (TILE_INFO), one output, info_text (STRING). It formats the dict's fields into a tidy multi-line string:

Grid: 4x4
Original Size: 1920x1080
Tile Size: 564x324
Base Tile: 480x270
Overlap: 42x27 px
Overlap %: 10.0%
Batch Size: 1
Total Tiles: 16

The node is also flagged as an output node, so it shows its text in the UI even when nothing downstream consumes info_text - which is what you want from a diagnostic. Wire it in parallel to the merge (same tile_info source) and it costs nothing to keep around while you tune.

When you actually need it

  • The merged image has a visible grid/seam pattern → check the overlap numbers here before you start fighting blend settings.
  • The output came out the wrong size → compare Original Size against what the merge produced; if your tiles were upscaled, the numbers here are the pre-upscale geometry and the merge scales them.
  • Tiles look scrambled → verify the grid and batch size; the merge assumes row-major tile order.

It won't fix anything for you - it's a window into state, not a control. That's exactly what a debug node should be.

Installation

Part of Praveen's ComfyUI Tools. Install via ComfyUI Manager (search "Praveen" / "praveen-tools"), or:

cd ComfyUI/custom_nodes
git clone https://github.com/Praveenhalder/praveen-tools

Restart ComfyUI. No extra dependencies or model downloads - it's pure Python formatting over the metadata dict. If you use the tiling pair at all, keep this one wired in; it's the difference between debugging blind and debugging with numbers.

Categoryimage/tile

Inputs (1)

NameTypeDefaultDescription
tile_infoTILE_INFO

Outputs (1)

NameTypeDescription
info_textSTRING