Get Timestamp JNK

Get Timestamp exists for one reason: unique filenames. It outputs the current Unix epoch time in seconds as a string, and - the important part - it re-evaluates every single run. Drop it into a filename builder ahead of your save node and every image you save gets a genuinely unique suffix, so batch runs stop overwriting each other. That's the whole job, and it does it perfectly.

The "fresh every run" behavior isn't an accident; it's the point of the implementation. The node overrides IS_CHANGED to always return NaN, which is the ComfyUI convention for "recompute me on every queue, every time." So unlike most nodes that only re-run when their inputs change, this one always fires - which is exactly what you want from a clock. A timestamp that didn't refresh would be a bug; this one's built so it can't be.

Inputs and outputs

No inputs. One output: timestamp - the current Unix epoch (seconds since 1970-01-01) as a STRING, e.g. 1755369600.

Installing it

Pack install: search JNK in ComfyUI Manager, or

cd ComfyUI/custom_nodes/
git clone https://github.com/Aljnk/ComfyUI-JNK-Tiny-Nodes.git

Zero dependencies; it's time.time() wrapped in a node.

Where people get burned

It's easy to forget what "Unix epoch seconds" looks like. It's a long integer, not a human date - 1755369600 won't tell you the time at a glance, and if you wanted a formatted date you're using the wrong tool (a text/format node or Python datetime is what you want). It's also seconds, not milliseconds, so two runs in the same second can produce the same value - for a save node that's almost always fine, but if you're looping faster than once a second, you can still collide. And one more subtlety: because it always re-evaluates, don't expect it to be stable inside a single batch - that's a feature for filenames and a bug for anything that needs a fixed value across a run. Use it where uniqueness is the goal, and it's the right tool every time.