Tile Images

A small utility, but one you'll reach for constantly once you've made a tile set. The tiles inside this pack travel in a few different layouts - raw boundary output, uncropped tiles with seam margins, or a single packed atlas - and downstream nodes need them in one canonical form: a batch of individual tiles at the resolution recorded in the TILESET. Tile Images does exactly that normalization and nothing else.

What it does

It takes your tile batch plus its TILESET and runs them through tilize_tiles, the same normalizer every node in the pack uses internally. Depending on what you feed it, that means: unpacking a packed atlas back into individual tiles, cropping the seam margin off uncropped resolution * 2 tiles, or just passing canonical tiles through untouched. The output is a plain IMAGE batch of n tiles at exactly resolution square - the format RandomTiling, TilePacking, and RejectCandidateTiles all expect, and the format you want if you're hooking the tiles into anything else in ComfyUI, like an upscaler or a tile viewer.

Inputs and outputs

• tiles (IMAGE) - any tile layout you have (packed, uncropped, or canonical)
• tileset (TILESET, forceInput) - kind, colors, resolution, candidates

Output is a single IMAGE: the normalized tile batch. From there, RandomSubsetOfBatch can pick a few for a quick preview, or wire straight into TilePacking/RandomTiling.

Installing and notes

Standard pack install: git clone https://github.com/samsartor/content_aware_tiles into ComfyUI/custom_nodes (or ComfyUI Manager → "content_aware_tiles") and restart. No models involved.

The one thing to know: because the TILESET port is forceInput, you can't fake it - the tile layout can't be interpreted without the metadata, so keep the tileset wire from wherever the tiles came. And if you feed it tiles whose batch size doesn't match the tileset's expectation (say, a half-generated dual set), you may hit the assert that fires in the shared normalizer - regenerate the full set and you're fine. This is a bare-bones research-pack utility, so don't expect documentation beyond this; the node body is a dozen readable lines.