💾 TOO Smart Image Saver (Advanced)(DOM)

This is the same node as the pack's "TOO Smart Image Saver (Advanced)" - literally the same Python class, registered twice - but with a more polished configuration panel. The (DOM) suffix is about how the frontend reads and writes its config: it accesses the node's data through the browser's Document Object Model directly, which is what lets it draw the prettier interface. The author's own docs put it plainly: "Same as the LiteGraph version, just fancier design."

So if you already read the LiteGraph article, everything that matters is the same, and I won't repeat it all here. The inputs are identical: images (required), optional metadata, workflow, and the three universal any1/any2/any3 sockets. The config panels are the same set - DATA fields, DATE FORMAT, MODEL extraction with SHA-256 hash, LORAS extraction with Civitai AutoV3 hashes, TEXT REPLACE, the NAMING template, and OUTPUT format/quality/metadata toggles. Same two outputs: images passthrough and filepath. Same payload in the file: an A1111/Civitai parameters block plus the embedded workflow (PNG), or parameters via EXIF on WebP/JPEG.

Why would you pick this one over the LiteGraph variant? Honestly, the UI. If you're spending a lot of time in the naming config and the extra polish makes it easier to read, this is the one to drop into your template workflow. The frontend style is the differentiator; the backend behavior is not.

The one real difference to know about. Because of how the DOM-based panel hooks into the node, the standard "right-click → Fix node (Recreate)" repair won't work cleanly on this variant - the docs tell you to refresh the canvas (F5 / Ctrl+R) instead if the node gets into a bad state. It's a minor operational quirk, but it's the kind of thing that makes people think the node is broken when it isn't.

Install.

cd ComfyUI/custom_nodes
git clone https://github.com/tetsuoo-online/Comfyui-TOO-Pack

or ComfyUI Manager → "Comfyui-TOO-Pack" → restart. Needs piexif (in the pack's requirements.txt) for the JPG/WebP EXIF metadata path.

Honest verdict. Two registrations of one saver is a slightly awkward way to ship a UI preference, and it can confuse people searching for the node - you'll see both "TOO Smart Image Saver (Advanced)" and "…(Advanced)(DOM)" in the node list. Functionally you can't go wrong with either; the (DOM) name just marks the version with the nicer panel. Whichever you use, the payoff is the same: filenames and metadata built from live graph values, and a Civitai upload that auto-links your model and LoRAs by hash - the thing the default save node can't do.