ComfyUI Node

Timestamp

A filename-safe clock that never collides

By TinyBeeman·Created about a year ago·Updated about a month ago· 1
Timestamp
    • long
    • date
    • time
    • short

    ComfyUI has a habit of generating a dozen images in a row and letting them pile up as ComfyUI_00001_.png through ComfyUI_00012_.png. Fine for a while, terrible when you're running the same workflow repeatedly and want outputs that are actually distinguishable at a glance. Timestamp is the fix: it reads the clock and hands you four text versions of "right now," all formatted to be safe to shove into filenames.

    It's about as simple as a node gets - no inputs at all - but it earns its place in the pack because three of its four outputs are specifically shaped for naming files, and one of them is compact enough for folder suffixes without making everything unreadable.

    The four outputs

    The node fires whenever the workflow runs and produces:

    • long - 2026-08-14-14-32-07, the full timestamp with dashes instead of colons. This is the one you'll wire into a filename prefix; the dashes make it legal on Windows, macOS, and Linux, and the second-level precision means two runs a second apart won't collide.
    • date - just 2026-08-14.
    • time - just 14-32-07.
    • short - a compact base62-encoded version of the same instant, something like 9hXp2d.... It's the least readable and the most space-efficient; use it when you want a unique suffix without the full date in the name.

    Because IS_CHANGED always reports a change, Timestamp re-evaluates on every queue - so consecutive runs genuinely get different values. If a node did cache its output, the whole point would be dead; the author deliberately made sure it doesn't.

    What to wire it into

    The natural partner is the pack's Save Image w/Meta node, whose prefix input accepts any string. Combine them and every output becomes 2026-08-14-14-32-07_whatever.png instead of ComfyUI_00042_.png. That's the highest-value use, but the outputs are plain strings, so you can also feed them to a filename builder, log them, or embed them in a JSON metadata block - whatever your workflow needs a "when was this made" marker for.

    Installing it

    Timestamp is part of ComfyUI-TinyBee, a small MIT-licensed utility pack with no models and no heavyweight dependencies. Via ComfyUI Manager:

    1. Manager → Custom Nodes Manager.
    2. Search "ComfyUI-TinyBee" and install.
    3. Restart ComfyUI.

    Or the manual route:

    cd ComfyUI/custom_nodes
    git clone https://github.com/TinyBeeman/ComfyUI-TinyBee
    

    Restart and you'll find it under 🐝TinyBee/Util. The pack's only real extra dependency, jsonata, is for its JSON Parser node - Timestamp uses nothing beyond the Python standard library.

    Gotchas

    Not much to trip on here, honestly. The output uses the local system time of the machine running ComfyUI, so if you're saving to a network drive or checking timestamps from another timezone, remember the values are whatever your OS clock says. And while the second-level precision makes collisions unlikely in normal use, running several batches within the same second can still produce identical strings - throw a counter or a prefix_2 value into the mix if that genuinely matters to you.

    Category🐝TinyBee/Util

    Inputs (0)

    No inputs

    Outputs (4)

    NameTypeDescription
    longSTRING
    dateSTRING
    timeSTRING
    shortSTRING