Ino DateTime Base64

Every automated pipeline needs unique filenames. Save ten runs to the same folder and they clobber each other unless you stamp something unique on each one. Ino DateTime Base64 is that stamp: it returns the current UTC datetime as a base64 string, and the pack explicitly guarantees it's unique per execution. No inputs, no setup, one string out. It's the laziest way to make sure your outputs never collide.

It's from ComfyUI-InoNodes, the 125+ node automation kit built around predictable chaining - and this is one of its quiet workhorse utilities. You won't build a workflow around it; you'll sprinkle it in wherever a unique token is needed and forget about it.

How it works

There's genuinely nothing to configure. The node takes no inputs and outputs a single STRING called base64. Internally it grabs the current UTC datetime and base64-encodes it, producing something like a short alphanumeric token. What makes it special for workflow use is how the pack treats it: the node is fingerprinted on its own output, meaning ComfyUI's caching treats every execution as fresh input. The value changes on every run, so no two runs of a workflow get the same token. That's the "unique per execution" guarantee, and it's the reason to prefer this over a plain timestamp node.

Where you'll use it

• Unique filenames. Feed the token into an Ino string node or an Ino Save Images-style node to append to a prefix, so each run writes its own file instead of overwriting.
• Cache busting. Anywhere a string ID is used as a lookup key, a fresh value per run forces the pipeline to treat this run as new - useful if you're uploading to S3 and don't want the uploader to think "already seen this."
• Correlation IDs. In the pack's more advanced flows, a per-run token is handy for tying together a download, a generation, and an upload so you can trace them later.

If you just need the human-readable datetime, the pack's other time nodes (Ino DateTime Simple, Ino DateTime Custom) give you ISO or formatted strings instead. This one's specifically for when you need a unique-ish opaque token rather than something readable.

Gotchas

Two things worth knowing. First, it's UTC, not your local timezone - fine for a unique ID, confusing if you decode it expecting your local time. Second, and this is the one that bites: the value is base64 of a datetime string, so its precision is whatever the datetime carries. If two executions somehow happen in the same instant you could in theory collide, but in practice ComfyUI runs are never that fast, and the "unique per execution" fingerprinting handles the normal case. Don't overthink it.

Also note this node, like every node in the pack, respects the V3 schema - which means it needs a recent ComfyUI (0.18.1+).

Installation

It ships with the whole pack:

• ComfyUI Manager: search "ComfyUI Ino Nodes", install, restart.
• Manual: cd ComfyUI/custom_nodes && git clone https://github.com/nobandegani/comfyui_ino_nodes && cd comfyui_ino_nodes && pip install -r requirements.txt, restart.

Python 3.10+, no models, no keys, and inopyutils (the pack's only real dependency) comes along via requirements.txt. If you're already running InoNodes for the file or S3 helpers, this one's already installed and waiting.