ViewComfy - Save Text
Write a String to Disk and Actually See What You Saved
ComfyUI saves images all day without thinking about it, but try to persist a string - a caption, an LLM's output, a log line - and you'll find the core toolbox is oddly empty. Save Text from ViewComfy-Utils fills that gap: it takes any string, writes it to your output folder as a .txt file, and then shows you the result right on the node. Simple on its face, quietly handy once you've needed it.
The inputs are what you'd expect: text (a string, marked force-input so you can wire it from any text source rather than typing it in), file_name (default text_file), and overwrite (a boolean, default True). There are no outputs - it's an output node. The behavior worth understanding is the overwrite toggle: with it on, the file is rewritten fresh each run; with it off, it appends, so consecutive runs stack lines into one growing file. That append mode is genuinely useful for logging and history, and it's the kind of detail the README glosses over but you'll want.
The part that makes it feel finished: the node has a small frontend extension that reads the saved file back and displays its contents in a read-only widget on the canvas. So you don't have to go hunting through output/ to check what an LLM workflow just produced - the text is right there, on the node, after every run. That's a much nicer debugging loop than the stock "write to disk and trust it" pattern, and it's the reason this node beats a hand-rolled python node for most people.
Where it fits: the obvious home is LLM-in-ComfyUI workflows, where a text-generation node produces something you want to keep alongside the images. The pack's own framing is "display text in a ViewComfy app" - in that context it's how a workflow hands a text result back to the app UI, which is exactly the output-channel problem the ViewComfy platform needed solved. Locally, it's also the easiest way to export prompts, metadata, or any string from a workflow without pulling in a heavier utility suite.
Two small caveats, both straight from the source. The file always gets a .txt appended, so don't include an extension in file_name or you'll end up with notes.txt.txt. And because it writes relative to your ComfyUI output directory, two workflows saving to the same file_name will collide - give each one a distinct prefix, or enable overwrite if you only care about the latest run. If overwrite is off and the file grows, it grows forever; there's no size cap.
Installation is shared with the whole pack: ComfyUI Manager → search "ViewComfy-Utils" → install, or clone by hand:
cd ComfyUI/custom_nodes
git clone https://github.com/ViewComfy/ViewComfy-Utils
Restart ComfyUI after. No extra dependencies beyond stock ComfyUI, no model downloads, MIT licensed. It's not the most glamorous node in the pack, but "save the thing the model said" is a problem you will eventually have, and this is the cleanest answer for it.
Inputs (3)
| Name | Type | Default | Description |
|---|---|---|---|
| text | STRING | — | |
| file_name | STRING | text_file | — |
| overwrite | BOOLEAN | true | — |
Outputs (0)
No outputs