Save Images Mikey (Mikey)

This is the base save node the rest of Mikey Nodes' save family builds on - the same rich, position-based filename templating as Save Images No Display, but with the on-screen preview left on, so you actually see what you just saved in the UI as it happens.

What it does

It's a terminal output node (no downstream outputs, is_output_node is true) that saves your batch to disk using a positional filename builder instead of ComfyUI's default prefix_00001_.png numbering. You get three free text slots - filename_text_1, filename_text_2, filename_text_3 - a timestamp, and a counter, and every one of those pieces has its own _pos field telling the node where in the final filename it lands (position 0, 1, 2, 3, 4...). filename_separator (default _) is what glues the pieces together into one string.

The controls that actually matter day to day:

• images - wire in your VAE Decode output.
• sub_directory - an optional subfolder under your ComfyUI output root, if you want this batch kept separate.
• filename_text_1/2/3 - drop in whatever identifies this batch: a checkpoint name, a short prompt fragment, a project tag.
• counter_type - none, folder, or filename (default folder), controlling whether the running number increments per output folder or per unique filename base.
• timestamp_type - job or save_time (default save_time), useful if a single run produces multiple saved images and you want to tell the order apart.
• extra_metadata - free text stamped into the PNG's own info alongside whatever else ComfyUI writes there by default.

The gap in the docs

Neither this node nor Save Images No Display gets a dedicated writeup in the pack's README - both only surface in the node registry itself, with byte-identical schemas. The most reasonable read, given the naming, is that this is the version that echoes the saved result back to ComfyUI's preview panel, while the "No Display" variant skips that step to keep the UI responsive on large batches. I can't verify the exact mechanism without reading the source, so treat that as an educated guess rather than a confirmed fact.

Installing

Comes bundled with the whole pack - ComfyUI Manager, search "Mikey Nodes," install, restart, or cd ComfyUI/custom_nodes && git clone https://github.com/bash-j/mikey_nodes and restart manually. No models or heavy dependencies; it's a pure file-writing utility.

Common problems

• Slow UI on very large batches. If you're running dozens or hundreds of images through this node and the ComfyUI tab starts lagging, that's almost certainly the preview rendering, not the save itself - switch to Save Images No Display for big batch runs where you don't need to eyeball every result as it lands.
• Position collisions producing an odd filename order. Give each _pos field its own number with room to spare (the defaults - 0, 1, 2, 3, 4 - already do this) so you can add another field later without renumbering everything.
• Missing node after install. Standard custom-node symptom - restart the ComfyUI process itself (a browser refresh won't pick up newly installed Python nodes), and check ComfyUI Manager's install log if the node still doesn't appear.